Status

Every consumer endpoint is probed automatically after each deploy and classified as ok, gap (responded, but empty or missing expected fields), slippage (data older than that endpoint's freshness budget), drift (response shape changed — a breaking change for typed clients), or breakage (did not respond). Reads /api/v1/status/api-health live — free, no key required. Shape-stability policy is on the changelog.

This section reads /api/v1/sources/status live. Data through is the newest reference period inside the source — for monthly releases it legitimately trails today (the BLS CPI report released mid-July carries June observation dates). Ingested is when the pipeline last pulled the source — that is the freshness signal.

BLS appears as three rows, on purpose. All ten BLS series arrive in one call, but they are published on different calendars: the Employment Situation lands on the first Friday of the following month, CPI around the 10th–14th, and PPI and import prices later still. One combined “data through” date would state the truth about the fastest series while implying it of the slowest, so bls_cpi, bls_ppi_import and bls_employment are reported separately. Between roughly the 5th and the 18th of a month they legitimately show different reference months — that is the release calendar, not drift. They share one ingest timestamp because one fetch either succeeded or it did not.