# Email Verify API – MX Record Lookup

> Email Verify API – MX Record Lookup 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).

Fetches raw MX (Mail Exchange) DNS records for a given domain, enabling email deliverability validation and mail server discovery.

## Facts

- Endpoint: POST https://email.payapi.market/mx-lookup?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-mx-record-lookup-cd2b493d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Y1zyudeJIYVz7pJ0Rlum8

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-mx-record-lookup-cd2b493d -d '<json body>'
```

Example prompt: Can you look up the MX records for stripe.com so I can verify it has valid mail servers set up?

## When to prefer this

Use this endpoint when you need raw MX record data for a specific domain, particularly for email validation workflows, deliverability pre-checks, or DNS auditing. It is ideal for lightweight, per-domain lookups with micropayment billing via x402/USDC on Base, making it suitable for high-volume automated pipelines where pay-per-use is preferred over subscription plans.

## Known failure modes

- Domain has no MX records — returns empty mx_records array
- Invalid or malformed domain input — may return an error or empty result
- Domain does not exist (NXDOMAIN) — lookup fails or returns empty
- DNS timeout or upstream resolver failure — service may return error
- Malformed request body missing the domain field — request rejected

## How this service works

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

## Output

Returns a JSON object containing the queried domain and an array of MX record objects, each with an 'exchange' field (the mail server hostname) and a 'preference' field (priority integer). Lower preference values indicate higher priority mail servers.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Domain to fetch raw MX records for, e.g. 'acme.com'."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "domain": "acme.com",
  "mx_records": [
   {
    "exchange": "aspmx.l.google.com",
    "preference": 1
   },
   {
    "exchange": "alt1.aspmx.l.google.com",
    "preference": 5
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/email-verify-api-mx-record-lookup-cd2b493d/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)