Verified endpoints

Questions this page answers

Which x402 endpoints actually answer a payment request?

As of 2026-10-26, 10 of the 12 paid resources we reached, named in projects' own x402 manifests, answered with HTTP 402 and a readable payment payload in the last 7 days; across all 130 URLs that declare x402, 10 did. Most of those URLs are listing pages where no 402 is expected, and nothing is paid, so this records a reply, not what paying delivers.

What does a verified 402 mean here?

That on the date shown, that URL answered HTTP 402 with a payment payload a client could parse. It is a protocol check. It is not a solvency claim, not a security claim, and not a promise that paying returns anything — we never send a payment, so we never observe delivery.

What share of declared x402 endpoints answer?

8.5% of the 118 endpoints we reached (last checked 2026-10-26). Endpoints we could not reach are excluded from the rate rather than counted as failures.

How is the check run?

One GET per declared endpoint, POST retried on a 405, redirects not followed, a 10-second deadline. A payload counts when it parses as x402 v2 in the body (accepts[] or paymentDetails) or as v1 in the headers; which one is recorded. The facilitator named in that payload is asked for /supported on its own host only.

Why is a cell blank?

A timeout, a bot-block or an undeclared facilitator is stored as null and shown as unknown. Unknown is a value here and never means failed or zero, and a check older than the window stops counting as standing rather than flipping to a negative.

What counts as working for an x402 endpoint here?

A URL is declared first, which is a claim. Then four readings, each dated and none implied by another: it answers HTTP 402 with a payment payload a client can parse, that payload names a network and asset, the host serves a /.well-known/x402 manifest, and the facilitator it names answers /supported. The last step, paying and getting what was sold, is not measured: no payment is sent by the daily check, so it is shown as not measured and never as zero.

Which count is for the paid resources, and which is for all URLs?

10 of the 12 paid resources we reached answered HTTP 402 inside the last 7 days (last checked 2026-10-26). A paid resource is a URL a project names as paid in its own /.well-known/x402 manifest, so a 402 is expected there. The count for all 130 URLs includes listing pages where no 402 is expected, so the two are never mixed. The paid-resource funnel is at /numbers/x402-endpoints-that-answer.

Sources — the x402 specification and the HTTP status it uses

• x402 — protocol specification and reference implementation ↗
• x402.org — the standard's own site ↗
• RFC 9110 §15.5.3 — HTTP 402 Payment Required ↗

Sato Hub. "x402 verified — declared endpoints probed for a real 402." Sato Hub, updated 2026-10-26, accessed 2026-10-26. https://satohub.ai/x402/verified

Data last refreshed 2026-10-26; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.