Two questions, answered on every response
How fresh is this? Each response reports when the data was computed, how old it is, how often it refreshes, and a plain status:
Is it fit to act on? Each response also carries a quality verdict derived from the platform’s confidence in the answer and whether any inputs were degraded:
When a verdict is
warn or fail, the response names exactly which fields were degraded, so there’s no guessing about what to trust.
Why this matters
- No silent staleness. A number that’s an hour old looks identical to a fresh one unless the response tells you — so it does. This is the single most common failure mode in DeFi risk data, and it’s designed out here.
- Auditable. The freshness timestamp and quality verdict are part of the response payload, so they can be logged and reviewed after the fact alongside the decision they informed.
- Machine- and human-readable. Automated systems branch on the verdict; people read the same signal in plain language.
How staleness is detected, per source
Freshness is not one global timer — it is measured against the expected update cadence of whichever source backed the answer. That source is named on the response itself (meta._agentic.sources), so the freshness status is always tied to its origin. How each source is detected:
The quality verdict then layers on top: it reflects the platform’s confidence and whether any input was degraded — so a response can be
fresh but warn if one of its inputs was incomplete.