Submit a new service or facilitator for review

Submit a new x402-compatible service, or an x402 facilitator (settlement operator), to be reviewed and listed in the directory. The optional body field "type" selects the branch: omit it (or use any value other than "facilitator") for a service submission; set "type": "facilitator" for a facilitator submission. Service submissions are automatically probed for valid HTTP 402 responses on the provided endpoints. Facilitator submissions are checked for on-chain presence instead: the enabled EVM chains among the declared networks are scanned for recent USDC settlement activity originated by the submitted settler addresses (30-day window, 15 seconds total budget); Solana and chains outside the measured registry are recorded as declared claims and resolved at manual review. A failed or idle probe never blocks the submission. Every submission of either type is manually reviewed before appearing in the directory. A service URL on a free compute host (vercel.app, workers.dev, pages.dev, netlify.app, onrender.com, railway.app, fly.dev, herokuapp.com, replit.app, glitch.me, deno.dev, pythonanywhere.com, firebaseapp.com, web.app and similar), on a free subdomain or dynamic-DNS service (eu.org, is-a.dev, duckdns.org and similar), on wildcard DNS that maps a name onto an IP (nip.io, sslip.io and similar) or on a hosted sandbox (hf.space, koyeb.app, codesandbox.io and similar) is answered with HTTP 402: submitting it costs a one-off $1 USDC on Base, non-refundable, which buys a place in the human review queue and nothing more. A service URL on static-only hosting (github.io, gitlab.io, surge.sh, neocities.org, r2.dev and similar) or on a dev-tunnel domain (ngrok, trycloudflare.com, localhost.run, serveo.net and similar) is rejected with HTTP 400 at any price. Website URLs are rejected only when they are dev-tunnel domains. Facilitator submissions are rejected with HTTP 400 for any free-hosting website URL, with no paid option. Each email address may submit once every 7 days per submission type (service and facilitator cooldowns are tracked separately): a second submission of the same type within the cooldown returns HTTP 429 with a Retry-After header (seconds until the cooldown ends). Submissions still pending after the 7-day review window are automatically rejected and the submitter is notified by email.