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.
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.
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.
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.
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)
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.
new HTTPFacilitatorClient({ url: "https://x402-doctor.fizzl.eu/facilitator" }) in your x402 resource server. Your Solana option then names our fee payer; the buyer's USDC goes straight to you.x-credit-key. A failed settle costs nothing.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.
ExactNearScheme from @x402/near/exact/server for near:mainnet and point HTTPFacilitatorClient at https://x402-doctor.fizzl.eu/facilitator. Your account must be registered on the USDC contract once (storage_deposit, about 0.00125 NEAR).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:
upto), your origin reports the actual amount in PAYMENT-SETTLEMENT on a successful response, and sets nothing on an error.PAYMENT-CONTEXT at your origin (an Ed25519 JWT, keys at https://payments.cloudflare.com/certs) and refuse requests without it, or anyone who reaches your origin directly gets the content for free.transaction_verification mode with the transaction hash.accepts.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:
gateway_only). Add a plain exact option next to Gateway if every x402 agent should be able to pay.testnet_only) until your mainnet options are live.resource.url: the middleware sends a path (/summarize); registries and some clients expect the full URL./plugin marketplace add Fizzl13/x402-doctor, then /plugin install x402-doctor@fizzl.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 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:
Cache-Control of the paid answer. Fix: send Cache-Control: no-store, private on every paid answer, so CDNs and proxies don't keep it.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.
serviceName, tags and an icon in your route config, and a /.well-known/x402.npx github:Fizzl13/x402-doctor <url> exits 1 on failures).declareBuilderCodeExtension from @x402/extensions/builder-code. Step 1 tells you whether the facilitator will find it.