Why can a listed endpoint not be called?
The short answer
Usually because the listing does not say how to call it. The endpoint exists and its payment wall answers; what is missing is enough public request information to construct the call safely.
As published in the issue
Of those, 975 publish no example at all, 481 publish an empty
{}, and 65 substitute a schema, an unsupported encoding or an unusable type.
(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.
These are not dead listings. Knocked at the payment wall — a minimal call sending nothing, claiming liveness and the quote and nothing more — 598 of the 831 contract-less routes graded (72.0%, 31 August–1 September) returned a valid payment challenge containing a payable quote: price, asset, pay-to address. The endpoint exists. The payment wall exists. What is missing is enough public request information to safely construct the call.
(3) The KNOCKED population: routes selected because they publish no usable request contract, graded at the payment wall and nowhere past it — every share over it describes those routes and never the sector.
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
These are not dead listings, and treating them as dead would be as wrong as treating them as usable. The gap is a publishing gap on the operator's side.
What we measured
We took the routes that publish no usable request contract and classified what each one publishes instead; then we knocked at the payment wall of a graded subset with a minimal request, sending nothing and claiming nothing past the quote, and counted how many returned a payable quote.
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.
What this does not say
- The contract-less share describes the routes selected for missing request contracts. It is not a share of the sector, and it is not a statement that those routes cannot be bought.
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 walk at the payment wall: what each route without a published request contract returned when knocked, partitioned by what a knock is permitted to grade, together with the outcome mix over the mirrored window. | 2c9f3d110901fa775a2ab6584ba5eff25cd1ebd325e92c1bf47cb493dee9155f |
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.