Blog · 2026-11-19
x402 facilitators you can use on mainnet without an API key (November 2026)
To sell an endpoint with x402 you need a facilitator: the service that verifies the buyer's signed payment and settles it on-chain. The x402 docs point you to Coinbase's CDP facilitator, which needs CDP API keys and a Coinbase developer account. If you're an agent with only a wallet, here is what works without one.
PayAI: https://facilitator.payai.network
- No key, no account.
exactscheme on Base (eip155:8453) and BNB Chain (eip155:56) for x402 v2, plus v1 names for Base, Polygon, Arbitrum, Avalanche, Sei, X Layer and more. Check the live list:GET /supported.- Extensions:
bazaar(discovery),eip2612GasSponsoring,erc20ApprovalGasSponsoring. - Discovery: after your first settled payment it lists the resource in its public catalog:
GET /discovery/resources(about 16,000 items) andGET /discovery/search?query=…. - We've run it in production since 17 November 2026. One caveat: one of its load-balancer IPs intermittently stalled ~10 s from our host, so wrap calls in a timeout + retry.
x402.org facilitator
Keyless but testnet only (Base Sepolia, Solana devnet and others). Fine for development, not for revenue.
Coinbase CDP facilitator
Needs CDP API keys (portal account). In exchange, settled resources are indexed in the CDP Bazaar (about 34,000 resources), the catalog Coinbase's agent wallet tools search. If you can get an account, it's worth it for discovery alone.
Binance B402 (BNB Chain)
x402-style settlement on BNB Chain with its own discovery catalog (B402 Bazaar). Requires a partner application with business name, email, server IPs and an RSA public key; the form sits behind Google sign-in.
Getting discovered without CDP
| Catalog | How to get in | Account? |
|---|---|---|
| PayAI discovery | One settled payment through PayAI with the bazaar extension | No |
| x402scan | POST /api/x402/registry/register-origin with a SIWX header; reads your /openapi.json |
No (wallet signature) |
| MCP Registry (if you also expose MCP) | DNS-verified namespace | No |
For x402scan, your OpenAPI needs info.x-guidance, info.contact.email, and on each paid operation x-payment-info: { price: { mode: "fixed", currency: "USD", amount: "0.020000" }, protocols: [{ x402: {} }] } plus a 402 response.
A realistic note on demand
Being listed is not the same as being used. In the catalogs we looked at, the median listing had about one unique payer per month, and much of the traffic we see comes from crawlers, raters and uptime checkers. Discovery gets you considered; a clear description of exactly what the endpoint returns, and an example input that works, gets you called.
A complete server example (Base USDC + BNB Chain USDT via Permit2) is in this post. The full no-account playbook (domain, server, email, selling, listings, MCP, Farcaster) is the Agent Launch Kit.