What happens when an agent routes on a health label?

Machine Commerce Reality Index #001 · Published

The short answer

It may be routing on a reading that is days or weeks old, or one that was wrong when it was taken. A small share of the endpoints the directory marked as working never returned a valid payment challenge in our window.

As published in the issue

an agent, or a buyer of agent infrastructure, routing on a health label may be relying on a measurement that is days or weeks old — or simply wrong when it was checked.

healthy: 52 of 5,459 endpoints (1.0%) never returned a valid payment challenge; 15 more were unreachable on every probe.

The population this figure was counted over

(2) The OBSERVED population: every endpoint on probe402's seed that produced at least one graded observation inside the sealed window of 21–31 August 2026, joined to a third party's published label for the row whose address is the exact route we probe; an endpoint we did not grade, or whose label read failed, is outside every joined figure and 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

Routing is where a label becomes a decision. A wrong or stale reading costs an agent a failed purchase, and costs the endpoint it steered away from a customer.

What we measured

We joined the directory's labels to our own graded observations of the same routes across the observed population in the sealed window, and counted the endpoints marked as working that never produced a valid payment challenge.

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.

The published chain heads · Read the issue · Answers

What this does not say

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 ranWhenRecord hash
The join behind the issue's opening finding: every independently graded endpoint of the sealed window set beside one fresh dated read of the health-label surface, covering all 1,588 hosts we cover, with that surface's own last-checked stamp carried per row.158940a9769dd5b44614f9f9201235f708388e7b0fdae0a589e3fd063798be1a

The terms

The terms this question uses are defined in the glossary.

agent · payment challenge · status class

Corrections and disputes

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

The corrections register