Coverage - Meridian

Coverage answers a different question from freshness: does Meridian have the requested stored fact for this identity, column, and interval?

Coverage segment

Futures and spot responses may include:

{
  "exchange": "hyperliquid",
  "product": "BTCUSDT",
  "columns": ["liquidations_dollar_volume"],
  "begin": "2026-07-13T00:00:00.000Z",
  "end": "2026-07-13T01:00:00.000Z",
  "resolution": "1m",
  "status": "source_limited",
  "source": "native_live",
  "imputed": false
}

Common states

State	Meaning
`covered` or `available`	Stored facts exist for the represented request
`source_limited`	The source does not provide the requested fact densely for that scope
`partial`	Some, but not all, requested coverage exists
`missing` or `no_matching_stored_rows`	No stored fact matched the exact scope

Rules

A source-limited null is not zero.
An unsupported venue/product pair does not count as a missing row.
A complete response can still contain explicit source-limited cells.
Coverage must be evaluated per venue, product, column, resolution, and interval.
Meridian does not synthesize facts to improve apparent density.

Keep coverage and warnings with exported data. Removing them can turn an honest partial dataset into a misleading complete-looking dataset.