Do routes that leave the Bazaar catalogue stop quoting?
The short answer
Mostly not. Most of the daily-read routes that left the Bazaar during September, and were read again after they left, still returned a valid payment challenge on their latest reading.
As published in the issue
Of the 3,153 daily-read x402 routes in our list that the Bazaar listed on 5 September and not on 30 September (on 864 hosts), 2,732 were read after they left. 2,383 of those (87%) still returned a valid payment challenge on their latest reading, and 2,176 did so on every reading after leaving (a median of ten).
(2) The OBSERVED population: every route on probe402's September route list — 16,118 routes on 1,950 hosts, fixed on 3 September — and every graded reading of it inside the sealed window of 4–30 September 2026, less the rows of endpoints a published correction of ours scopes; a gateway, movers or address figure is a count over those readings, a comparison with a third party's label joins the exact route we read to the label its surface returned for it, and an endpoint we did not read is counted rather than dropped.
The sentence above is quoted from a published issue and is not re-written here. Its date, its population and the record behind it are below.
Why it matters
A catalogue removal reads like a death notice, and a buyer or a directory that treats it as one drops endpoints that still answer. Without a dated reason for each removal, a listing change says nothing about the endpoint.
What we measured
The daily-read x402 routes on the September route list that the Bazaar listed at the start of the month and not at its end, joined to every graded reading of each route after it left. The exact population rule is quoted beside the figure below.
What the evidence shows
- Sealed days behind the archive figures
- 27
- Observations in that window
- 315,315
- Issue
- Machine Commerce Reality Index: #002 — September 2026
- Published
2026-09-04 · 2026-09-05 · 2026-09-06 · 2026-09-07 · 2026-09-08 · 2026-09-09 · 2026-09-10 · 2026-09-11 · 2026-09-12 · 2026-09-13 · 2026-09-14 · 2026-09-15 · 2026-09-16 · 2026-09-17 · 2026-09-18 · 2026-09-19 · 2026-09-20 · 2026-09-21 · 2026-09-22 · 2026-09-23 · 2026-09-24 · 2026-09-25 · 2026-09-26 · 2026-09-27 · 2026-09-28 · 2026-09-29 · 2026-09-30
27 of the 27 sealed days behind these figures are on the head table at /chain (9 re-derived from an off-vendor replica and 18 anchored from the archive as stored). Each day's manifest is served at /chain/<date>.
What this does not say
- Neither catalogue read says why any route left.
Method and reproduction
The runs behind the figures, the record each one produced, and the terms this question uses.
What ran, when, and the record it produced.
| What ran | When | Record |
|---|---|---|
| The join behind the departed routes: every x402 route on the September list that the catalogue carried on 5 September and not on 30 September, set beside every graded reading of it after it left, by cadence, operator and gateway, with the routes listed on both dates as the comparison. | 7393b5ecc51743f96d050a76019583bfdac5b456bd62dd7f27c8145c258516ca |
The terms
The terms this question uses are defined in the glossary.
Corrections and disputes
Corrections to this issue are on the corrections register, and this answer reads from the record rather than from a copy.