# Email Verify API

> Email Verify API is a paid API for AI agents from email.payapi.market, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-17).

Validates an email address by checking syntax, MX records, SMTP, disposability, and catch-all status, returning a scored verdict

## Facts

- Endpoint: POST https://email.payapi.market/verify?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/email-verify-api-aac2b1d8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JYjhBR4_at93H8ZVWehHg

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 email-verify-api-aac2b1d8 -d '<json body>'
```

Example prompt: Can you verify whether jane.doe@acme.com is a real, deliverable email address — check if it's valid, not disposable, and has working mail servers?

## When to prefer this

Choose this endpoint when you need a comprehensive, scored email verification that covers syntax, MX records, SMTP reachability, disposable detection, and role-based flagging in a single call. It is well-suited for agents that need to validate individual email addresses on demand with micropayment billing ($0.001 USDC per call via x402 on Base), avoiding subscription overhead. Prefer it over simpler regex-only validators when deliverability accuracy matters, and over heavier identity platforms when you only need email-level checks without full KYC.

## Known failure modes

- Missing or malformed email input returns a validation error
- Unreachable or non-existent domain may result in low score or 'invalid' verdict
- Catch-all domains may return indeterminate SMTP results
- Transient SMTP timeouts could affect smtp_check accuracy
- Payment failure via x402 will block the request from processing

## How this service works

Email verification with x402 payments. $0.001 per request in USDC on Base.

## Output

A JSON object containing the verified email address, a numeric score (0–100) reflecting deliverability confidence, the domain, an overall verdict (e.g. 'valid' or 'invalid'), boolean flags for catch-all, disposable, role-based, and free-provider status, a list of MX records, SMTP check result, syntax validity flag, and a typo suggestion if one was detected.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "email": {
   "type": "string",
   "description": "Email address to verify, e.g. 'jane.doe@acme.com'."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "email": "jane.doe@acme.com",
  "score": 100,
  "domain": "acme.com",
  "verdict": "valid",
  "catch_all": false,
  "disposable": false,
  "mx_records": [
   "aspmx.l.google.com",
   "alt1.aspmx.l.google.com"
  ],
  "role_based": false,
  "smtp_check": true,
  "syntax_valid": true,
  "free_provider": null,
  "typo_suggestion": null
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/email-verify-api-aac2b1d8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from email.payapi.market](https://www.zero.xyz/host/email.payapi.market/llms.txt)