What it measures
Every number comes from a live probe of your URL, never from a stored guess:
- The URL answers at all, and how long it takes
- Whether the unpaid call returns 402 — and on every probe, not just one
- Whether a
PAYMENT-REQUIREDheader is present - The
payToaddress the challenge declares, decoded from the header - Whether that
payToshows up in the public discovery catalog
Latency is reported as p50 / p95 over the probes that answered 402, with the sample count shown — so you know how much of a promise it is.
Call it
An unpaid request returns the x402 terms. A paid request returns the report.
curl -i -X POST https://verify-service.node01.org/api/verify-service \
-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.001) 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.
The verdict you get back
- ALIVE_AND_INDEXED — every probe answered 402 and the payTo is in the public catalog
- ALIVE_PAYABLE_NOT_INDEXED — every probe answered 402, but the payTo is not listed yet
- INTERMITTENT — some probes answered 402, some did not
- BROKEN — reachable, but not a 402 (the wrong status code is reported)
- UNREACHABLE — no probe got an answer
Complementary to listing-doctor
Same family, different question. listing-doctor ($0.05) diagnoses why an endpoint is not indexed; verify-service ($0.001) tells you whether the service is alive and consistent right now, with latency you can quote. Check the doctor when a listing is missing, the verifier when you need a number to put in your docs.
Machine-readable
OpenAPI 3.1 · x402 manifest · agents.json · agents.txt · llms.txt · trust-measured catalog