Email Verification API
4 endpoints for real-time email verification: single verify, bulk verify (up to 100), domain check, MX lookup. Each call runs syntax validation, MX resolution, SMTP RCPT probe, catch-all detection, disposable check against 3500+ domains, role-based pattern detection (45+ patterns), free provider classification, typo suggestion, and a 0–100 quality score. Verdict: valid / invalid / risky / unknown.
x402 verified · $0.001 USDC/request · 4 endpoints / 4 tools · Verification · base network · x402 protocol
Validate email addresses: syntax, MX records, disposable-domain and catch-all detection. Single, bulk and domain checks.
Endpoints
POST /verify: Verify a single email: syntax, MX, disposable and role-account checks. ($0.001)POST /bulk-verify: Verify a list of emails in one call. ($0.001)POST /domain-check: Check whether a domain can receive email. ($0.001)POST /mx-lookup: Return the MX records for a domain. ($0.001)
Example request
curl -X POST https://email-verify-api-production-d262.up.railway.app/verify \
-H 'content-type: application/json' \
-d '{"email":"jane.doe@gmail.com"}'
Example response
{
"email": "jane.doe@gmail.com",
"valid": true,
"syntax_valid": true,
"mx_found": true,
"disposable": false,
"role_account": false,
"free_provider": true
}
How an agent calls this
Is jane.doe@gmail.com a valid, non-disposable email address?
An MCP-connected agent discovers this API, picks it for the task, and pays per call in USDC. No keys, no account.
How to call this API
Every protected route returns HTTP 402 with x402 payment requirements. An agent pays the stated USDC amount on Base and retries with the payment header. No API keys, no accounts. Browse the marketplace or list your own API.