For x402 sellers

AI agents decide in milliseconds whether to pay you. These free tools show you what they see, and let you prove you're worth paying.

1. Check your endpoint free

Every check a paying agent would run, without paying: the 402 challenge, every payment option, Solana readiness, which wallets can pay, Bazaar and OpenAPI discovery. Each problem comes with a fix.

2. Your track record and badge free

x402 Doctor scans every resource in the CDP Bazaar, Circle's Agent Marketplace, GoPlausible's discovery list and the MPP directory once a day. Agents get this record before they pay you. Look yours up, then put the badge in your README or on your site: it updates daily and links to your record. Not listed anywhere yet? Look it up anyway and add it there: Doctor checks that it answers 402, and the next scan starts its record.

x402 payable badge, example

3. Prove a payment free

A buyer says they paid? Paste the PAYMENT-RESPONSE header (or a transaction and network) and see whether it's on-chain, succeeded, and how much USDC went from whom to whom.

Open the payment proof check →

4. Get told the moment it breaks 1 free · up to unlimited

The Fizzl endpoint monitor calls your endpoint every hour the way a paying agent does, without paying. If it stops asking for payment correctly (a 5xx, a 200 without payment, a broken challenge), you get a notification in the Fizzl wallet app on your phone, or a message on Telegram, Discord, Slack or your own webhook, and another when it works again. One endpoint is free. Pro watches 10 for $5 per 30 days, Pro 20 watches 20 for $9, and Pro Unlimited as many as you need for $20, all in USDC.

Watch my endpoint → (sign in with your wallet, no e-mail)

A facilitator for Solana that takes Phantom, and for NEAR

Sell on Solana? Phantom adds Lighthouse safety instructions to every payment it signs, and some facilitators refuse that layout, so those buyers can't pay you. Doctor's facilitator settles them: it simulates the transaction and checks the USDC really reaches your payTo. Before every settle it also screens the payer and your payTo against the OFAC SDN list, so no sanctioned money reaches you through it.

Sell for USDC on NEAR? The same URL settles near:mainnet payments. The buyer signs one USDC transfer to your account with the official @x402/near client, and our relayer sends it and pays the NEAR gas, so neither of you needs NEAR. Same OFAC screen before every settle, and each signed payment settles once.

Selling through AWS, Cloudflare or Stripe

Cloudflare's Monetization Gateway (closed beta, US sellers and buyers) and Stripe's x402 machine payments (US businesses; elsewhere on request) both send a standard x402 v2 challenge and settle through the Coinbase CDP facilitator, so the free check above works on them as is. AWS WAF's Monetize action on CloudFront answers in the x402 format too, and settles through the same Coinbase facilitator. What to watch:

AWS WAF on CloudFront

Cloudflare Monetization Gateway

Stripe x402

Selling through Circle Gateway

Built with @circle-fin/x402-batching, for example with Circle's accept-agent-payments skill for Claude Code? The check above knows Gateway's options on every network it serves, testnets included. What to watch:

What agents check before paying you

Agents using x402 Doctor's pre-payment check (GET /api/v1/preflight, also in x402-safe-fetch) get go, caution or no_go. You get caution or no_go when:

The five x402 attacks: what Doctor checks

The paper Five Attacks on x402 (May 2026) found five ways a paid endpoint can answer without being paid, or take a payment without answering. What x402 Doctor checks from outside, and what you fix in your own server:

Also checked: HEAD for free. Up to @x402/core 2.28.0 the payment middleware let a HEAD request on a paid GET route through, and Express, Hono and Next then run your handler for it unpaid: no answer goes back, but the work and its costs do. The web check sends one HEAD request and warns when it gets a 2xx. Fix: update the @x402 packages once the fix (x402#3796) is released; until then key the route without a method, or refuse HEAD before the payment middleware.

Get found in the Bazaar

  1. Settle through the CDP facilitator (set your CDP API keys): resources that settle there (and declare discovery metadata) can be listed in the CDP Bazaar.
  2. Describe your resource: a clear description, input and output schema, serviceName, tags and an icon in your route config, and a /.well-known/x402.
  3. Stay payable: check yourself with step 1 after every deploy (or in CI: npx github:Fizzl13/x402-doctor <url> exits 1 on failures).
  4. Get attributed on Base: declare your Base Builder Code (minted at base.dev) with declareBuilderCodeExtension from @x402/extensions/builder-code. Step 1 tells you whether the facilitator will find it.
  5. Show it: the badge from step 2 on your README and site.
  6. Watch it: let the endpoint monitor (step 4) tell you on your phone, Telegram, Discord or Slack when it breaks, before your buyers notice.

by · all tools and live demos at fizzl.eu