x402 doctor
Paste the URL of an endpoint you sell over x402 and see what a paying client would meet: does it answer 402, is the payload readable, does the resource URL match, is it on a mainnet in USDC, is it catalogued. One unpaid request, nothing paid.
What a result is, and is not
Each check describes what one unpaid request met at that moment. Nothing here says whether paying works or whether you deliver, because we never pay. “unknown” means we did not observe it, for example because your server refused our request or did not answer in time. It does not mean something failed.
What it checks
Uses https
The URL is served over TLS.
Answers 402
An unpaid GET (or POST, if GET gets a 405) is answered with HTTP 402.
Readable payload
The 402 carries payment options with scheme, network, payTo, asset and amount.
Resource URL
The URL named in the payload is the URL we requested. A mismatch is what a proxy that ends TLS usually causes.
Mainnet and USDC
The network is a mainnet and the asset is a known USDC contract.
Catalogued
The URL is in the x402 Bazaar catalogue we collect from.
Solana token account
Only for Solana options: the payTo holds a USDC token account.
Discovery metadata
A description and input and output schema, so agents can find and call it.
The check runs against public hosts only, on standard web ports, with a short time limit. It is also available as POST /api/x402/doctor with a JSON body of { "url": "https://…" }.