How many x402 payment endpoints answer a payment request?
Of the paid x402 URLs we probe, how many return a real 402.
- As of2026-10-27
Paid resources
12
URLs a project names as paid in its own /.well-known/x402 manifest
Reached
12
0 gave us nothing — unknown, not failed
Answered a real 402
10
parseable payment payload, within 7 days
Share of reached that answer
withheld
12 reached is below the publishable floor
Answering, facilitator reachable
0
the declared facilitator answered /supported on its own host
Every URL probed, by what it is
| Kind of URL | Probed | Reached | Answered a 402 |
|---|---|---|---|
| Paid resource (named in its own /.well-known/x402) | 12 | 12 | 10 |
| MCP endpoint (payment, if any, rides inside JSON-RPC) | 8 | 8 | 0 |
| Listing page (homepage, docs, repo or article) | 110 | 101 | 0 |
Only a paid resource is a place an HTTP 402 is expected. The listing pages come from directory listings whose standards field carries x402 — Sato Hub's classification, not the project's declaration — and for a wallet or an SDK it often means the tool can pay with x402 rather than sell over it. A missing 402 on a homepage measures nothing, so those rows are shown and never counted against anyone.
What the gap between these numbers is
Declaring x402 costs nothing: a tag, a line in a manifest, a mention in a README. Answering one means a server is running, priced, and returns HTTP 402 with a payload a client can act on. Neither number is a safety or solvency claim, and we never send a payment — so delivery is never observed. A blank is unknown, never a failure, and a check older than 7 days stops counting as standing rather than flipping to a negative.
Settlement networks the answering payloads declared
| Network | Endpoints |
|---|---|
| eip155:8453 | 10 |
A declared network is what the seller says it accepts. We did not pay, so no settlement was observed. These rows count endpoints, not payments, and are never added to any other population.
- Method
- One GET per URL (POST retried on a 405), redirects followed, a 10-second deadline. A payment payload counts when it parses as x402 v2 (base64 JSON in the
PAYMENT-REQUIREDheader) or v1 (JSONaccepts[]in the body). A 403 or 429 is a wall, not an answer, and counts as unknown. The facilitator named in that payload is asked for/supportedon its own host only. - Population
- Paid resources declared by any
/.well-known/x402manifest found on the hosts of directory listings whosestandardsfield contains x402, one per host and listing; those listings' own website, docs and MCP URLs are probed too and shown apart. The Coinbase Bazaar catalogue is a different population, measured separately; the two overlap and must never be added. - Per endpoint
- Every host and what it did is on x402 verified. This page is the counts only, so the two cannot drift into two different tables of the same endpoints.
- Reproduce
- GET /api/export/x402-verified.json → endpoints[] (declared_as, url, outcome, http_status, protocol) and funnel.by_kind; then fetch any url with curl -i and base64-decode its PAYMENT-REQUIRED header
Data CC-BY-4.0 — attribution: data by satohub.ai. A standing 402 is a statement about a protocol response on a date, nothing else.
Reference
QuestionsWhat people ask about this pageShowHide
Questions this page answers
- How many x402 payment endpoints actually answer a payment request?
- 10 of the 12 paid resources we reached (last checked 2026-10-27), inside a 7-day window. A paid resource here is a URL a project names as paid in its own /.well-known/x402 manifest; 0 of the 12 gave us nothing and are unknown, not failures.
- What share of x402 payment endpoints answer?
- No share is published: 12 reached paid resources is below the 20-observation floor this site publishes a rate on. The count stands; a small sample is never turned into a percentage of the ecosystem.
- What are the other URLs Sato Hub probes, and why do they not count?
- 110 are homepages, docs pages, repositories or articles from directory listings whose standards field carries x402, and 8 are MCP endpoints. That field is Sato Hub's classification, not the project's declaration, and for a wallet or an SDK it often means the tool can pay with x402 rather than sell over it. Nobody said those URLs take payment, so a missing 402 there measures nothing; 0 of them answered one.
- Which networks do the answering endpoints settle on?
- eip155:8453 (10) — as declared in each 402 payload. A declared network is what the seller says it accepts; we did not pay, so we did not observe a settlement.
- Does an answering endpoint mean paying it works?
- No. It means that on the date shown, that URL returned HTTP 402 with a payment payload a client could parse. No payment is ever sent, so delivery, solvency and honesty are never observed and are never claimed. A check older than the window stops counting rather than flipping to a negative.
SourcesWhere the data comes fromShowHide
Sources — the x402 specification and the HTTP status it uses
Cite this pagePlain text, APA or BibTeXShowHide
Cite this
10 of the 12 x402 payment endpoints we reached replied with valid payment terms; nothing was paid, as of 2026-10-27.
Sato Hub, "How many x402 payment endpoints answer a payment request?", https://satohub.ai/numbers/x402-endpoints-that-answer, as of 2026-10-27. Data CC-BY.
How this was measured
- Method
- Once a day, one unpaid request to each URL that declares x402 (GET, or POST when the server answers 405), counted as answering when it returns HTTP 402 with a payment payload a client can parse; no payment is ever sent.
- Window
- Verifications from the last 7 days; an endpoint last verified before that is not counted as answering.
- Data date
- MCP call
- none — No MCP tool returns this funnel: the banked answers_402_rate row mixes listing pages with payment resources, so it is a different number.
- URL
- https://satohub.ai/api/export/x402-verified.json
endpoints[] holds one row per URL; funnel.by_kind holds the three counts per kind of URL.
Machine source
- JSON export: https://satohub.ai/api/export/x402-verified.json → endpoints[] and funnel.by_kind