meta._agentic.freshness) and is it fit for automated use? (meta._agentic.quality_gate). Both are first-class fields, so a client can branch on them instead of guessing.
Freshness
Status values
status is derived from age_seconds relative to update_cadence_seconds:
Quality gate
verdict summarizes whether the response is fit for unsupervised automated use, from confidence (0.0–1.0) and whether any fields are degraded:
degraded_fields lists which fields drove a warn/fail; reason is a human-readable explanation. Per-field confidence and provenance are available in meta._agentic.field_confidence. The verdict is also returned in the X-Quality-Gate header.
Not the same as oracle staleness
The envelopefreshness.status above describes the response data. It is distinct from the oracle-feed staleness vocabulary (fresh, approaching_stale, stale, unverifiable, not_applicable) returned by the oracle classification endpoints, which describes how stale a specific price feed is. See Oracle classification for that model.
See also
- Response envelope — the full
{ data, meta }contract. - Agentic envelope — consuming these signals as an automated agent.
- Errors — retry guidance for failed requests.