How much of the MPP catalogue is mounted through a gateway?

Answered from the issue named below, as published on its date. A later issue is a later answer, at its own address.

The answer

109 of 142 listed services (76.8%) are third-party gateway mounts by the catalogue's own integration field, and 978 of 1,456 endpoint rows (67.2%) are mounted through the gateway domains of Orthogonal, Locus and Tempo — a statement about how the catalogue is integrated, not about economic control.

The population this figure was counted over

(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.

What this does not say

The evidence

What ran, when, and the record it produced.

What ranWhenRecord
One fresh read of the second catalogue's service listing, split by that catalogue's own integration field: which services are mounted through a third party's gateway domain, and which are listed by the service itself.4c56c19a6605088f8cfdc3fca30095fe25ed46321f92b49d99e8c5e466133e71
Sealed days behind the archive figures
11
Observations in that window
29,022
Issue
Machine Commerce Reality Index: #001 — August 2026
Published

The published chain heads · Read the issue · Answers

The terms

The terms this question uses are defined in the glossary.

MPP · catalogue · discovery

Corrections and disputes

This answer names a party we measure. The route to dispute a reading is on the corrections page.

Corrections to this issue are on the corrections register, and this answer reads from the record rather than from a copy.

The corrections register