What it checks
Five checks, in the order they fail. Each answer comes from a live probe, never from a stored guess:
- The URL is reachable and answers within the timeout
- The unpaid call returns 402, not 200/403/500
PAYMENT-REQUIREDheader present and decodable- A
payToaddress is declared in the challenge - That
payToappears in the public discovery catalog
Output: verdict (INDEXED, PAYABLE-NOT-INDEXED, NOT-402, BAD-HEADER, MISCONFIGURED, UNREACHABLE, UNKNOWN) with the checks that produced it.
Call it
An unpaid request returns the x402 terms. A paid request returns the diagnosis.
curl -i -X POST https://listing-doctor.node01.org/api/listing-doctor \
-H 'content-type: application/json' \
-d '{"url":"https://your-host/api/your-route"}'
Expect HTTP 402 with the payment terms. Pay with any x402 client on Base (USDC, $0.05) and repeat the same request with the payment header; you get JSON back.
A browser request to the API path gets the 402 challenge, not a form: this page is the human entry point.
Before you pay: the free half
Most “not indexed” cases start with missing discovery files. Generate all six for free at discover.node01.org: OpenAPI, .well-known/x402, agents.json, agents.txt, llms.txt and robots.txt, in the browser, no account. If the files are right and the endpoint still fails, the doctor is the next step.
Machine-readable
OpenAPI 3.1 · x402 manifest · agents.json · agents.txt · llms.txt · trust-measured catalog