Email DNS Preflight

$0.001 USDCBase mainnetx402 v2

Low-cost infrastructure intelligence for autonomous agents, CRM hygiene, sender vetting, DNS diagnostics and anti-phishing preflight. Direct Base x402 needs no signup or API key.

Direct payment asset: native USDC on Base, contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Do not use bridged USDbC.

Pay from other networks, settle on Base

Buyers can prepay API credits with native USDC from Ethereum, Arbitrum, Optimism, Polygon or Avalanche. Relay routes the payment to native USDC on Base at the configured seller wallet. Credits are issued only after the Worker verifies a successful Base fill to the exact payout recipient and USDC contract.

The cross-chain path never accepts an arbitrary destination: Base chain ID 8453, native USDC and the seller payout address are fixed server-side. Credits equal floor(actual verified Base USDC / $0.001), so Relay fees and routing costs cannot create unbacked credits. Settlement transaction references are replay-protected, and each completed deposit address must not be reused. The $0.001 direct Base x402 path remains unchanged.

MCP Streamable HTTP

https://email-dns-preflight-x402.copper-crate.workers.dev/mcp exposes four read-only MCP tools over Streamable HTTP: email_preflight, domain_preflight, domain_email_security and domain_rdap. MCP negotiation and tools/list are free; every successful tool call costs $0.001 native USDC on Base through x402. Payment travels in MCP _meta["x402/payment"] and settlement receipts return in _meta["x402/payment-response"].

Paid HTTP endpoints

Why agents use it

Useful for email validation, lead-list hygiene, signup checks, domain research, DNS/domain-security posture, certificate-issuance policy, MX/TXT inspection, SPF diagnostics, DMARC policy analysis, DKIM/BIMI checks, registrar-lock/expiry signals and infrastructure verification.

Important limits

Mailbox existence and inbox delivery are not tested. DKIM selectors are publisher-defined, so the DKIM signal is explicitly heuristic and checks common selectors only. BIMI checks only the default selector and does not fetch or validate referenced SVG/evidence documents, so record presence is not a logo-display guarantee. RDAP 404 responses are not treated as ownership proof.

Machine-readable discovery