> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent context: freshness checks

> Rules for when agents should add 0xArchive data-quality checks before market-data jobs, backtests, exports, or downstream analysis.

Add a data-quality preflight for:

* backtests
* alerts
* exports
* model or research inputs
* order-book reconstruction
* incident reviews

Use coverage, freshness, and incident routes before a job depends on a venue, symbol, data family, and time window.

Do not silently interpolate or fabricate missing market data.

## Quality Checklist

Store the quality checklist with downstream output when a job feeds a backtest, alert, export, dashboard, warehouse table, or model input.

| Field            | What to store                                                                                  |
| ---------------- | ---------------------------------------------------------------------------------------------- |
| Route            | Coverage, freshness, incident, latency, SLA, or venue freshness path                           |
| Venue and symbol | The exact family and symbol used for the downstream request                                    |
| Data family      | Order book, L3, L4, trades, candles, funding, OI, liquidations, orders, replay, or export      |
| Window           | `start`, `end`, cursor chain, and any requested limit                                          |
| Quality body     | Coverage payload, freshness timestamp, incident state, latency result, or SLA result           |
| Request handle   | `meta.request_id` when exposed, or the downstream data request ID from the client or transport |
| Decision         | Continue, narrow window, retry later, or stop                                                  |

Do not require the market-data envelope on coverage bodies that expose a resource-specific payload.

## Agent Stop Rules

Stop before widening the request when freshness is missing, stale, or contradicted by an incident. Stop when coverage does not include the requested venue family, symbol, data family, or time window. Stop when the quality route and market-data route disagree about the symbol or family. In those cases, return the quality checklist and ask whether to narrow the window, choose a different symbol, or wait for updated coverage.

For one-off inspection, it is acceptable to report the quality result beside the market-data response. For backtests, alerts, exports, dashboards, warehouse tables, and model inputs, store the quality checklist as part of the output contract so the result can be audited later.