Keep the next intake check comparable

Save the exact address and any DKIM selectors used for an import. Run that same request again before the next outreach batch or CRM cleanup. The response keeps the fields that explain a changed result: can_receive_mail, is_disposable, is_role_account, and the SPF, DMARC, and DKIM records.

email-deliverability-check costs $0.005 USDC per x402 call on Base. It checks address syntax, mail-domain DNS posture, disposable-domain risk, and role mailboxes. The route does not contact the mailbox, so can_receive_mail means the domain publishes MX records rather than that a person controls the address. 

{
  "email": "[email protected]",
  "dkim_selectors": ["selector1", "selector2"]
}

Use the selector list only when the sender publishes it. Otherwise omit it and the route checks its documented common selectors.

Save the response beside the import

Keep the request body, deliverability_score, risk, and findings with the import record. A later run can compare the same domain posture without turning a new list of addresses into an unexplained score change. Treat an address as a new paid check when its local part or domain changes.

For an agent that pays through HTTP 402, the canonical endpoint is: 

POST https://x402.agentutility.ai/email-deliverability-check

The web-probe MCP package exposes the same tool as email-deliverability-check with the same JSON fields. Save the returned verification_level too. It records the DNS-only boundary used by the check.