Email Verification API
GET /api/email/verify $0.005 per call
USDC on Base · x402
Email verification for outreach and CRM agents: syntax validation, MX lookup with implicit-MX fallback, disposable-domain detection, role-account and free-provider flags, plus-tag normalization, and a deliverability verdict. No signup, no external services.
Parameters
| Name | In | Description | |
|---|---|---|---|
email | query | required | Email address to verify |
Example request
curl "https://api.webbersites.com/api/email/verify?email=jane.doe%2Bnews%40gmail.com"
# first call returns 402 + payment requirements; an x402 client pays and retries automaticallyExample response
{
"email": "jane.doe+news@gmail.com",
"normalized": "janedoe@gmail.com",
"syntax": {
"valid": true
},
"domain_check": {
"mx_found": true
},
"flags": {
"disposable": false,
"role_account": false,
"free_provider": true,
"plus_tag": true
},
"verdict": "deliverable_domain"
}MCP tool: get_email_verify — via npx -y webbersites-x402-mcp (local, key stays on your machine) or the remote endpoint https://api.webbersites.com/mcp.
How payment works
There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.