by Test
Validate email addresses for deliverability, format, MX records, and disposable domain detection. Powered by Abstract API.
/?email={email}| Name | Type | Required | Description | Example |
|---|---|---|---|---|
email | string | required | Email address to validate | test@example.com |
{
"email": "test@example.com",
"is_mx_found": true,
"is_smtp_valid": true,
"quality_score": 0.95,
"is_valid_format": true,
"is_disposable_email": false
}Bad Request
Missing or invalid parameters
Unauthorized
Invalid or missing API credentials
Too Many Requests
Rate limit exceeded
Internal Server Error
Upstream API error — payment hash released for retry
All calls use the x402 payment protocol: send a request, receive a 402 with payment instructions, send USDC on Base L2, then re-call with the transaction hash.
GET https://gateflow-proxy.7crypto-jo.workers.dev/v1/a072c723/email-validator — receive a 402 with payment instructions
Send USDC on Base L2 to the address in X-Payment-Address
Wait for 1+ block confirmation (≈ 2 seconds on Base)
Re-send your original request with the tx hash in X-Payment-Hash
Obolo verifies on-chain and proxies the request to the upstream API
AP2 Support
This endpoint also accepts AP2 Cart Mandates. Include a signed Cart Mandate in the X-AP2-Mandate header with an x402 tx hash embedded in payment.txHash.
curl "https://gateflow-proxy.7crypto-jo.workers.dev/v1/a072c723/email-validator" \
-H "X-Payment-Hash: 0x<your_tx_hash>" \
-H "X-Payment-Chain: 8453"curl "https://gateflow-proxy.7crypto-jo.workers.dev/v1/a072c723/email-validator" \
-H "X-Payment-Hash: 0x<your_tx_hash>" \
-H "X-Payment-Chain: 42161"https://gateflow-proxy.7crypto-jo.workers.dev/v1/a072c723/email-validatorUSDC
Base L2 (Chain 8453)
Protocols