# x402 Email Verification API

> x402 Email Verification API is a paid API for AI agents from call402.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-19).

Validates an email address by checking syntax, disposable domain lists, and MX DNS records, returning a deliverability verdict

## Facts

- Endpoint: POST https://call402.com/api/email-verify?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-email-verification-api-1c62e3ea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NQOD_xMYAudsmcT1YWQch

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-email-verification-api-1c62e3ea -d '<json body>'
```

Example prompt: Can you check whether someone@example.com is a valid, deliverable email address — make sure it's not a disposable address and that the domain actually has mail servers set up?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-use email validation that covers syntax, disposable domain detection, and MX record lookup without SMTP probing. It is ideal for agents that need occasional or low-volume email checks without committing to a subscription-based validation SaaS. The x402 USDC micropayment model makes it cost-effective at $0.005 per call for sporadic validation needs.

## Known failure modes

- Missing or malformed email field returns a 400-level error
- Invalid JSON body causes request rejection
- Payment not included or invalid causes HTTP 402 response with payment requirements before processing
- Domain with no MX records returns mx_found: false and a conservative verdict
- Disposable domains are flagged but not blocked — verdict interpretation is left to the caller

## How this service works

USDC pay-per-call APIs for AI agents via the x402 protocol (v2, exact, Base mainnet). Send a request, receive HTTP 402 with payment requirements, pay with @x402/fetch or any x402 client, retry with the PAYMENT-SIGNATURE header.

## Output

Returns a JSON object with the original email and domain, a verdict field (e.g. 'likely_deliverable'), booleans for format_valid, mx_found, and disposable, a list of discovered MX hosts, and metadata describing which checks were performed (syntax, disposable list, MX lookup). No SMTP mailbox probing is performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "email": {
   "type": "string",
   "description": "Email address to validate"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "meta": {
   "note": "No SMTP mailbox probing.",
   "checks": [
    "syntax",
    "disposable_list",
    "mx_lookup"
   ]
  },
  "email": "someone@example.com",
  "domain": "example.com",
  "verdict": "likely_deliverable",
  "mx_found": true,
  "mx_hosts": [
   "mail.example.com"
  ],
  "disposable": false,
  "format_valid": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-email-verification-api-1c62e3ea/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from call402.com](https://www.zero.xyz/host/call402.com/llms.txt)