Validate an email address and return structured signals: RFC syntax validity (isSyntaxValid + reason if not), the normalized address with split local/domain, and boolean flags for…
Validate an email address and return structured signals: RFC syntax validity (isSyntaxValid + reason if not), the normalized address with split local/domain, and boolean flags for isDisposable (throwaway/temp-mail domain), isRoleAccount (info@, support@, admin@, …), and isFreeProvider (gmail/outlook/yahoo/icloud/…). With checkMx (default true) it also reports hasMxRecords — whether the domain publishes MX records, looked up live via DNS-over-HTTPS — plus the MX hosts. IMPORTANT: this is NOT a deliverability or mailbox-existence guarantee (catch-all domains, greylisting, and privacy relays make that impossible to assert from a single lookup); hasMxRecords reflects DNS MX presence only. Useful for signup-flow hygiene, lead scrubbing, and flagging disposable/role addresses before sending.
| Method | Endpoint | Price | Description |
|---|---|---|---|
GET | /v1/marketplace/api/email-validate-3754 | $0.00115 | Invoke Email Validate (Search) and return the upstream response. |
Requests are paid per call over the x402 protocol. Call the endpoint, receive a 402 Payment Required quote, then repeat the request with the signed payment header. The SDKs do both steps for you.
# 1. Ask for a quote
curl -i https://api.jarvisclaw.ai/v1/marketplace/api/email-validate-3754
# 2. Pay it (the SDK signs and retries for you)
curl -H "X-PAYMENT: <signed-payload>" https://api.jarvisclaw.ai/v1/marketplace/api/email-validate-3754
Open in the marketplace
Docs: Getting started · x402 payments · x402 discovery · All APIs