Data quality is public system state.
Per venue and per layer: how many of the values the platform collects are present, stale or missing right now — decided by the same rule the API applies to every answer it gives.
There is no single "all systems operational" badge. A venue whose connector went silent is shown as exactly that, next to the venues that are collecting normally.
One row per venue. Open it for one row per layer.
A venue is read through seven layers — ticker, mark, funding, open interest, book, stats, venue depth — and each goes out of date on its own clock. The venue row sums them; the rows inside keep them apart, with the five answers the API gives: present, stale, missing, not_published, off.
| Venue · layer | State | Present | Stale | Missing | Oldest present | Open breaks · stale reasons |
|---|---|---|---|---|---|---|
| Requesting | ||||||
Values that are stale or missing, with the reason.
A stale value is not returned as a value: the API answers with its status, its reason and its age — never with a number that looks live. A stale one also says whose standstill it is: by venue when the platform kept receiving and the venue's own timestamp, which the horizon counts from, is old (its feed stands), by us when the platform stopped hearing, a connection broke or no cadence fact covers it; awaiting first trade when our own connector restarted and the venue's market has not traded since — its ticker is made of its trades, so nothing new can arrive before the first one (we lost nothing, the venue is silent; the value is still stale, and counted as such); the reason stays the API's. A missing one was expected and has not been observed. Up to 50 per venue are listed, the longest out of date first.
What the five answers mean.
Present, stale, missing, not published and off — every reason a value is null, and why none of them is folded into another.
How long a value is good for.
The horizon of every layer on every venue, and what it rests on.