Skip to main content
Provenance describes how a stored fact entered Meridian and which source or materialization run produced it.

​
Provenance segment

{
  "source": "binance_vision_aggtrades",
  "family": "custom_bars",
  "exchange": "binance-futures",
  "product": "BTCUSDT",
  "begin": "2026-01-01T00:00:00.000Z",
  "end": "2026-01-02T00:00:00.000Z",
  "status": "available",
  "source_run_id": "custom_bars_...",
  "provenance_type": "native_backfilled",
  "imputed": false
}

​
Source classes

Meridian can distinguish native live collection, native exchange archives, historical backfill, replay, and explicitly approved repairs. Exact labels are returned with the response and may evolve without changing the underlying stored-facts rule.

​
Imputation

imputed: false means the fact was not created by interpolation or synthetic filling. If Meridian ever exposes imputed data, the value must be marked explicitly and remain distinguishable from native facts.

​
Operational lineage

Depending on the surface, provenance can include source_id, job_id, provenance_id, collection_mode, original_source, source_completeness, and source-run identifiers.