How many x402 and MPP routes are listed?
The short answer
Tens of thousands of routes across the two public catalogues, on the day we read them. The total moved between two complete reads taken less than two hours apart, so any count needs its timestamp.
As published in the issue
The x402 and MPP route catalogues (Bazaar and mpp.dev) list 16,197 routes across 1,768 hosts as of 1 September.
(1) The CATALOGUE population: every route listed on the two public route catalogues, combined and de-duplicated, at one stamped read on 2026-09-01 — the read the issue's route, host and service counts are quoted against, with a second complete read 93 minutes later kept as the cross-check.
The listed universe moved 16,170 → 16,197 routes between two complete reads 93 minutes apart on 1 September. Because the catalogue denominator moves, market-size claims need a timestamp.
(1) The CATALOGUE population: every route listed on the two public route catalogues, combined and de-duplicated, at one stamped read on 2026-09-01 — the read the issue's route, host and service counts are quoted against, with a second complete read 93 minutes later kept as the cross-check.
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 denominator that moves within an afternoon makes an undated share meaningless.
What we measured
We walked both public route catalogues in full, combined and de-duplicated the routes and their hosts, and repeated the complete read later the same day to measure how far the catalogue population had moved.
What the evidence shows
- Sealed days behind the archive figures
- 11
- Observations in that window
- 29,022
- Issue
- Machine Commerce Reality Index: #001 — August 2026
- Published
11 days
2026-08-21 · 2026-08-22 · 2026-08-23 · 2026-08-24 · 2026-08-25 · 2026-08-26 · 2026-08-27 · 2026-08-28 · 2026-08-29 · 2026-08-30 · 2026-08-31
All 11 days behind these figures (21–31 Aug 2026) are sealed, each with its published hash on the Integrity page; each date opens that day's manifest.
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 hash |
|---|---|---|
| One fresh full read of both public route catalogues, combined and de-duplicated: route shares by operator, settlement routing attributed from published payment challenges against a re-fetched public registry, and the count of listed routes that publish no usable request example. | b34ac16e2eba36d319f1423b2b2c348d8b4d2ad022c12e2eae6e9a41e3ce53c5 | |
| The dated, stamped union read every catalogue denominator in this issue is quoted against, and its cross-check against a second complete read taken 93 minutes later — which is where the moving-denominator signal comes from. | 60fe0415ac7e79c53c5e76f3a930acfbc87dc2b241ca4d8ca0ab61243f890fb9 |
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.