# AmanChain Email Validation + MX Check

> AmanChain Email Validation + MX Check is a paid API for AI agents from amanchain-relay.gitajhd.workers.dev, paid per call via x402, $0.001244/call, status unknown (last checked 2026-09-15).

Validates an email address by checking syntax correctness, DNS MX record existence, and whether the domain is a known disposable email provider

## Facts

- Endpoint: POST https://amanchain-relay.gitajhd.workers.dev/api/x402/aman-email-validate
- Price: $0.001244/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/amanchain-email-validation-mx-check-42b6264c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ebj262HtYGzLByECxOxT8

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 amanchain-email-validation-mx-check-42b6264c -d '<json body>'
```

Example prompt: Can you check whether john.doe@tempmail.com is a valid email — specifically whether its syntax is correct, its domain has real MX records, and whether it's from a known disposable email provider?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call email validation that covers syntax, DNS MX reachability, and disposable-domain detection without requiring an API key or account setup. Ideal for agent workflows that need to screen individual email addresses at the point of user input, form submission, or lead capture, especially when integrated with x402 micropayment flows on Base.

## Known failure modes

- Malformed input JSON returns an error with missing field indication
- DNS lookup timeout may occur for very slow or non-existent domains
- Disposable email database may not include very new throwaway domains
- Invalid or missing serviceId field causes request rejection
- Network errors or AmanChain node unavailability return a service error

## How this service works

Email validation API — syntax check, DNS MX record verification and disposable or temporary email detection. Deterministic on-chain execution by the AmanChain node — live consensus state, real blocks, pools and balances. Pay per call via x402 (USDC on Base), no account, no API key. POST JSON {"serviceId":"aman-email-validate","request":"<input>"}.

## Output

Returns a structured validation result indicating whether the email address has valid syntax, whether the domain has resolvable DNS MX records (confirming it can receive mail), and whether the domain is identified as a known disposable/temporary email provider.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "body": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "type": "object",
     "example": {
      "ok": true
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/amanchain-email-validation-mx-check-42b6264c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from amanchain-relay.gitajhd.workers.dev](https://www.zero.xyz/host/amanchain-relay.gitajhd.workers.dev/llms.txt)