Email Validate API

Validates an email address: syntax, MX records for its domain, and whether it is a disposable or role account.

Updated

Agents read this page asGET /v1/email-validate/schemafree: schema, examples, errors, price

Endpoint
POST /v1/email-validate
Price
$0.002 per call
Timeout
5 s
max_timeout_seconds
26 (the whole call as the 402 envelope sells it: the timeout, plus payment verification and settlement around it)
Response cap
2 MB (2,097,152 bytes)

When to use it

The MX check needs a resolver an agent may not have, and the disposable/role assessment is a curated dataset and rule set it would otherwise have to build and keep current.

When not to use it

  • The destination needs more than 5 s to answer: the call ends with upstream_timeout (424).

Parameters

One JSON body. The schema is free at GET /v1/email-validate/schema.

FieldTypeRequiredDescription
emailstringyesThe address to assess, up to 320 characters; it is trimmed, and a malformed address is answered with syntax_valid false rather than rejected.
check_mxbooleannoWhether to resolve MX records for the domain; when true, a domain with no MX makes valid false, and false skips every network lookup. Default: true.
check_disposablebooleannoWhether to match the domain against the bundled disposable-provider list; when true, a disposable domain makes valid false. Default: true.

Limits

LimitValue
Size cap2 MB (2,097,152 bytes)
Timeout5 s
Show the JSON Schema the handler validates against
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "minLength": 1,
      "maxLength": 320,
      "description": "The address to assess, up to 320 characters; it is trimmed, and a malformed address is answered with syntax_valid false rather than rejected."
    },
    "check_mx": {
      "default": true,
      "description": "Whether to resolve MX records for the domain; when true, a domain with no MX makes valid false, and false skips every network lookup.",
      "type": "boolean"
    },
    "check_disposable": {
      "default": true,
      "description": "Whether to match the domain against the bundled disposable-provider list; when true, a disposable domain makes valid false.",
      "type": "boolean"
    }
  },
  "required": [
    "email"
  ],
  "additionalProperties": false
}

Example

The published example, verbatim: the request and the response it returns.

Request
POST /v1/email-validate
content-type: application/json
payment-signature: <base64 x402 payload>

{
  "email": "[email protected]",
  "check_mx": false
}

Without the payment-signature header the call answers 402 with the payment requirements, including this endpoint's price and its max_timeout_seconds, so the deadline is known before anything is paid. The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case we cannot state for you is a settlement call that fails without answering: the error message says so when that is what happened.

Response200 OK
200 OK
payment-response: <base64 settlement receipt>

{
  "email": "[email protected]",
  "valid": true,
  "syntax_valid": true,
  "mx_found": false,
  "mx_records": [],
  "is_disposable": false,
  "is_role_account": true
}

Response fields

FieldTypeIn the example
emailstring"[email protected]"
validbooleantrue
syntax_validbooleantrue
mx_foundbooleanfalse
mx_recordsarray0 items
is_disposablebooleanfalse
is_role_accountbooleantrue

Deterministic: the same input returns the same output. Clock-derived fields, when present, are declared in the response.

Call it from code

The client reads the 402, signs the payment and retries on its own.

// email-validate: $0.002 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'

const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)

const body = {
  "email": "[email protected]",
  "check_mx": false
}

const res = await fetchWithPayment('https://grist.tools/v1/email-validate', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)

Errors

Every error is typed JSON. Only a successful call is settled.

CodeHTTPWhen
invalid_input400The body does not match the schema on this page. Nothing is charged. The body does not match the schema; its fields are email, check_mx and check_disposable.
unreachable_target424The destination you named did not resolve or refused the connection.
upstream_timeout424The destination you named did not answer before the declared timeout for this endpoint expired.
internal500Our fault, and in almost every case nothing is charged. The exceptions come after the call has run and the settlement call was made: the message "The work was done but settlement could not be completed", and the messages starting with "Payment settlement returned". There, whether the payment moved is unknown to us as well. The payment moves at most once: its nonce is single-use and settlement is idempotent, so a retry with it is never charged twice. A retry is normally refused with a 402: replay_consumed, an expiry reason, or a reason saying the nonce was already used once the transfer is on-chain. Only if our server restarted before the transfer was final can a retry run the call again. Even then, the payment moves at most once. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain; to call again, sign a new payment.
rate_limited429Too many calls from the same payer, or too many calls towards the same destination domain. Nothing is charged.
concurrency_limit,
registry_at_capacity,
upstream_unavailable
503We could not serve the call right now. Retryable: wait the number of seconds in the retry-after header, then repeat the call. concurrency_limit and registry_at_capacity mean we were at capacity: the call did not run. You can send the same payment again if its validBefore is still far enough away to cover another call. If it is not, the retry gets a 402 authorization_validity_too_short: sign a new payment. upstream_unavailable means our internal service failed or did not answer in time: the call may already have run and the payment may have been settled. A retry with the same payment can get a 402 whose error field says why. authorization_validity_too_short: too little time is left before validBefore to cover another call. This check comes before the replay check, so it does not tell whether the first payment was settled. replay_consumed (the payment was used and may have been settled) or replay_exhausted (too many attempts): sign a new payment. replay_in_flight: the first call is still running, so wait and do not pay again. invalid_exact_evm_nonce_already_used: the transfer is already on-chain, so this payment cannot move again. Sign a new payment. An authorization can be settled only once, since its nonce is single-use. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain.
misconfigured503The service is not configured to serve calls. The call did not run and nothing is charged. It needs a fix on our side, so there is no retry delay to wait for.

Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.

Questions

How much does a call to the Email Validate API cost?

$0.002 per call, paid in USD Coin on Base via x402. There is no account and no API key: the price is in the 402 answer, before anything is paid.

What is the timeout of email-validate?

The endpoint itself runs for at most 5 s. max_timeout_seconds in the 402 answer is 26: that covers the whole call, including payment verification and settlement around it.

How large can a response from email-validate be?

The response-size cap is 2 MB (2,097,152 bytes).

Is the email-validate input schema free to read?

Yes. GET https://grist.tools/v1/email-validate/schema returns the input schema for free, paid endpoints included.

What happens if a call to email-validate fails?

The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case that cannot be stated in advance is a settlement call that fails without answering: the error message says so when that is what happened.

What does email-validate return?

A JSON object with 7 top-level fields: email, valid, syntax_valid, mx_found, mx_records, is_disposable and is_role_account. The example on this page is a real call.