Email Syntax and MX Verification
Validate email syntax and check live DNS MX records. MX presence does not prove an individual mailbox exists.
Preview request
The preview path is rate-limited and does not charge. Production requests use the same parameters and return a standard x402 challenge when no payment signature is present.
curl --request POST \
"https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/verify_emails?preview=true" \
--header "content-type: application/json" \
--data '{"emails":["test@example.com","fake123xyz@yopmail.com"]}'Input contract
| Parameter | Type | Required | Description |
|---|---|---|---|
emails | array | Yes | Array of email addresses to verify. |
Guaranteed response metadata
Every successful product response identifies how the result was produced. Product-specific output fields are documented in the paid OpenAPI contract and can be inspected through the preview request where available.
{
"marketplace_metadata": {
"data_mode": "live_source",
"billable": true,
"availability": "operational",
"source": "syntax validation and live DNS MX lookup"
}
}Agent payment flow
Request the product, read the base64 PAYMENT-REQUIRED challenge, sign the exact Base-USDC authorization with an x402 buyer client, and retry using PAYMENT-SIGNATURE. A successful response includes PAYMENT-RESPONSE.