State of x402
Purchase counts by chain are listed at x402 and MPP payments by chain. The L0 rows behind section 1 are in /api/v1/observatory/l0/export.csv (CC BY 4.0). Dated snapshot report: State of x402: November 2026.
KIZUNA Creation. vet402 observatory. Dataset, retrieved 2026-11-17T10:10:53.768Z. https://vet402.com/api/v1/observatory/state
This citation names the state aggregate, read at 2026-11-17T10:10:53.768Z. It covers the headline totals, the L1 purchase counts, and the listing-change counts. Those three come from that read. It does not cover the chain table in section 2, the history graph, or the coverage share. The history graph uses lastRollupAt from the history response (2026-11-16T10:30:26Z). The coverage share states its own read time in section 5. The shared read behind the state aggregate is reused for up to 300 seconds, so a later API response can carry a different retrievedAt and different counts.
Abstract
Reports of dead endpoints and silent catalog delisting in the x402 ecosystem have so far been anecdotes from individual operators. The figures below are the same phenomena measured across the entire public discovery catalog, with denominators attached. unverified is its own bucket — an entry that cannot be machine-checked is not counted as dead.
1.Headline measurements
| Measurement | Count | Share |
|---|---|---|
| Endpoints on record (denominator) | 162,832 | — |
| Active records (not closed; a Bazaar record stays active after it leaves the catalog) | 137,065 | 84.2% |
| Seen in the latest full read of the Bazaar (2026-11-17) | 33,286 | 98.5% of the catalog's own total |
| Delisted (absent on a complete fetch) | 25,767 | 15.8% |
| Payment wall answers a valid 402 (published pass) | 97,988 | 60.2% |
| of which active (the rest are delisted endpoints whose latest probe passed) | 83,219 | 60.7% of active |
| of those active, latest probe more than 7 days old | 44,161 | 53.1% |
| Payment wall failing on ≥2 consecutive probes, and still active (published fail) | 16,979 | 10.4% |
| Withdrawn from the catalog (delisted, and the newest probes would publish as fail). Left out of the public L0 fail count. | 3,703 | 2.3% |
| Unverified (gate unmet, or not yet probed) | 44,162 | 27.1% |
| No HTTP method, or a method other than GET, POST, HEAD, or DELETE (the probe uses GET) | 93 | 0.1% |
2.By chain
L0 observation has always been chain-agnostic and costs nothing to run, so this table covers every chain the public catalog lists an endpoint on — a wider set than the chains L1 purchasing has reached, which are the rows of the by-chain table in §3. Mainnets only: a row appears only for a network id vet402 knows to be a mainnet. Testnet listings (Base Sepolia, Solana devnet, Arc testnet, Celo Sepolia and the other testnets vet402 names) are excluded below, and so is a network id vet402 cannot name as either (as this page was rendered: unknown × 63, eip155:8217 × 7, eip155:143 × 1, eip155:46630 × 1) rather than assumed to be a mainnet. That makes this table's denominator narrower than the one in §1, which counts every listing on record including testnets: the rows here sum to 161,802, against 162,832 in §1, and the testnet (927) and unnamed listings this table drops are the difference. The two figures come from separate reads, up to a few minutes apart, so read that difference as of those reads rather than as a fixed count. The two denominators are otherwise the same set: both apply the same exclusion of endpoints paying vet402's own addresses. As this page was rendered that exclusion was taking out 0 of them — the count is printed rather than the rule, so a day when it removes nothing reads as nothing removed.
This chain table was read at 2026-11-17T08:57:47.374Z.
Fail in this table leaves out routes withdrawn from the catalog. Wdn is that share of n.
| Chain | n | Listed | Pass | Fail | Wdn | Unverified |
|---|---|---|---|---|---|---|
| Base | 157,087 | 84.2% | 60.1% | 10.6% | 2.2% | 27.1% |
| Arc | 2,005 | 92.0% | 85.3% | 0.3% | 0.0% | 14.4% |
| Solana | 1,363 | 81.4% | 72.2% | 4.5% | 1.2% | 22.2% |
| Tempo | 1,202 | 88.2% | 28.0% | 6.0% | 8.0% | 58.1% |
| XRPL | 54 | 98.1% | 77.8% | 22.2% | 0.0% | 0.0% |
| Arbitrum One | 41 | 100.0% | 87.8% | 0.0% | 0.0% | 12.2% |
| Robinhood Chain | 18 | 88.9% | 66.7% | 27.8% | 0.0% | 5.6% |
| X Layer | 18 | 22.2% | 55.6% | 0.0% |
3.L1 — real purchases
| Measurement | Count | Share of its own denominator |
|---|---|---|
| Paid purchase attempts (money signed and sent): the denominator of the next row | 22,178 | — (denominator) |
| Settled: transfer confirmed on-chain | 15,341 | 69.2% of attempts |
| settled (nonce-bound): the re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset | 13,347 | 87.0% of settled |
| settled (amount + payee): the re-read matched payer, payee, amount and asset and did not bind a one-time value. This tier holds rows settled before 2026-09-04 12:00 UTC, and Stellar rows | 1,994 | 13.0% of settled |
| settled whose settlement block time falls within -5/+15 minutes of the attempt | 15,210 | 99.1% of settled |
| settled with no settlement block time on record (neither inside nor outside that window) | 131 | 0.9% of settled |
| settled where the seller returned no receipt and our own settlements index found the transfer afterwards (same on-chain re-read as the rest) | 1,267 | 8.3% of settled |
Delivered: settled and the paid request answered 2xx other than 202 Accepted with a non-empty body | 14,064 | 63.4% of attempts · 87.7% of attempts not held (vet402's hold) · 87.7% of attempts counted in the delivery rate (16,029: attempts, less held and awaiting on-chain verification) |
Awaiting on-chain verification (settle_claimed): the seller asserted a settlement and vet402 has not yet read it on-chain — in attempts, in neither delivered nor held (vet402's hold below); its ledger held_reason is empty | 0 | 0.0% of attempts · 0 waiting more than 1 day, 0 more than 7 days |
Inconclusive: held, not counted against the seller on this page's delivery rates. The paid request answered 4xx, or it ran while vet402's payer wallet was unfunded. “Held” here means rows with a ledger held_reason; attempts awaiting on-chain verification are the row above. The decision API counts on the seller side while the ledger stays . Reason code counts held rows except seller_fixable_input, plus rows awaiting on-chain verification |
| Chain | Paid attempts | Settled | Delivered | Inconclusive | settled (nonce-bound) | settled (amount + payee) |
|---|---|---|---|---|---|---|
| Base | 17,881 | 11,947 | 11,061 | 5,532 | 10,343 | 1,604 |
| Solana | 1,465 | 1,192 | 1,128 | 184 | 1,166 | 26 |
| Celo | 553 | 493 | 487 | 20 | 493 | 0 |
| Arc | 452 | 348 | 338 | 36 | 348 | 0 |
| Arbitrum One | 421 | 310 | 306 | 83 | 310 | 0 |
| Tempo | 406 | 375 | 121 | 216 | 375 | 0 |
| Stellar | 392 | 364 | 364 | 1 | 0 | 364 |
| XRPL | 326 | 197 | 162 | 24 | 197 | 0 |
| BNB Chain |
The two settled rows above split the same 15,341 receipts by how strong the evidence behind each is, and they sum back to it. The split labels strength. It does not change the count. Signature-nonce binding shipped at 2026-09-04 12:00 UTC. Receipts confirmed before then were matched on payer, payee, amount and asset. A seller holding several listings at the same price and payee could satisfy that check with a transfer received earlier. Stellar rows are in the amount and payee count. The Stellar re-read checks payer, payee, amount and asset and does not bind a one-time value. Those rows keep the settled label. Demoting one would assert that the transfer was not the one bought, and the record does not show that. The machine-readable form is l1.settledNonceBound and l1.settledAmountPayeeOnly, per chain in l1.byChain (this L1 breakdown is not mainnet-filtered, so it sums to the L1 totals; the §2 table above is L0 and mainnets-only). Methodology states what each strength does and does not establish.
Attempt and settled counts above are as reported by /api/v1/observatory/state (l1.attempts, l1.settled): an attempt is a paid request whose payment was signed and sent, whatever the seller answered. The per-endpoint cells on the register use the same denominator, and so does history — its rows are the same attempts, cut by UTC day and chain, recomputed for the trailing 14 days on each rollup, so its totals trail this table by whatever settled after the last rollup (the response says through which day it is rolled up, and when). Other machine-readable surfaces (decisions, export.csv) apply their own definition of an attempt and can differ; when a number is quoted from this site, the state API is the one to cite.
4.Listing-change events observed
| Event | Count |
|---|---|
| delisted — vanished from a complete fetch | 47,726 |
| relisted — returned after a delisting | 38,027 |
| settle_drop — catalog-reported 30-day calls fell ≥70% from a ≥100 base | 285 |
5.Coverage and ledger integrity
Coverage (7-day window): 52,838 of 137,065 active records (38.5% of active records) carry an L0 measurement from the last 7 days. This is the machine definition behind "endpoints under regular verification". Numerator and denominator as stated, nothing else. This page read that share at 2026-11-17T10:10:27.963Z. The response at https://vet402.com/api/v1/observatory/state carries its own retrievedAt. This page reuses the shared read for up to 300 seconds.
Ledger integrity: daily hash chain over the full purchase ledger, latest root (2026-11-15): 5d374b99f6392642… over that day's 106 ledger entries (an anchor counts the rows it hashed, not the L1 attempts above). A root covers that day's rows as they stood when it was computed; rows are still updated afterwards by design (a settlement verified on-chain, a correction), so an older root describes the ledger as it was then, not as it is. The chain is kept by vet402 and not yet fixed anywhere outside it, so it shows whether a root you saved was later changed — it does not by itself stop vet402 from editing rows. Check the links yourself from /api/v1/observatory/anchors alone: each day's prevRoot is the previous day's root (cli/verify-anchors.ts checks that and that no day is missing). Recomputing a root needs the raw purchase rows, which are not published in full — the open-source projection hashes fields export.csv leaves out (row id, payer, asset, sub-second time, and the statuses the export omits), so a root cannot be rebuilt from the published files.
6.Daily history
L0 probes per UTC day (upper line) and how many of them measured pass (lower line), all chains combined, 60 days with data (2026-09-18 to 2026-11-16). Machine-readable, per chain: /api/v1/observatory/history?days=60.
7.Caveats
Figures are computed from days whose catalog fetch was complete; incomplete days withhold delisting judgements entirely. Probes cycle through the catalog on a rolling schedule, so unverified includes endpoints simply not yet reached. vet402's own listings, when present, pass through the identical pipeline (fairness commitments). None of these figures is an assessment of any individual operator.