Blockchain Data · x402
Validate an email address: syntax, live MX record check, and disposable-domain detection
Validate an email address: syntax, live MX record check, and disposable-domain detection.
by email-validator.pdfextractapi.workers.dev · discovered, not yet claimed by its owner · updated 2026-09-14
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Validate an email address: syntax, live MX record check, and disposable-domain detection.
Tags: bazaar
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/8923.jsonfor the price and payment options. - Pay. Call
GET https://email-validator.pdfextractapi.workers.dev/validate. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.005 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Uptime
- 1 of the last 1 checks answered
- Calls (30d)
- 3 · 3 unique payers (third-party data from the public x402 Bazaar)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.005 | 0xA0AC44BECC6302298f01ed255B175ca1060C189E | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xA0AC44BECC6302298f01ed255B175ca1060C189E",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "5000",
"amountUsd": 0.005,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"bazaar": {
"info": {
"input": {
"body": {
"email": "[email protected]"
},
"bodyType": "json",
"method": "POST",
"type": "http"
},
"output": {
"example": {
"email": "[email protected]",
"has_mx_record": true,
"is_disposable": false,
"reason": null,
"syntax_valid": true,
"valid": true
},
"type": "json"
}
},
"schema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"body": {
"properties": {
"email": {
"description": "The email address to validate.",
"type": "string"
}
},
"required": [
"email"
]
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method",
"bodyType",
"body"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}
}
}Example shape — generated from the schema, not a captured live response
nullExamples
curl
curl "https://email-validator.pdfextractapi.workers.dev/validate"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidJavaScript
const res = await fetch("https://email-validator.pdfextractapi.workers.dev/validate");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}Python
import httpx
res = httpx.get("https://email-validator.pdfextractapi.workers.dev/validate")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- email-validator.pdfextractapi.workers.dev
- Endpoint
- https://email-validator.pdfextractapi.workers.dev/validate
- Machine-readable
/resources/8923.json