Skip to main content
Catalog presence, settlement interpretation and analytical coverage are separate facts. A discovered market can exist without a supported payout model. The API does not claim full-universe coverage.

Inspect coverage

GET /coverage accepts at most one selector type: listing IDs, market IDs or a family ID. A venue can refine the scope. No selector returns venue/family capability summaries. Coverage identifies supported interpretation, calculation and market-data capabilities, including known limits and historical windows. Every supplied analytical input is accounted for. require_complete_coverage defaults to true. Explicit partial analysis returns supported inputs and a scoped conclusion. Missing prices are a distinct condition from missing payout coverage.

Reproduce a calculation

Keep the returned market/mapping versions, family scenario pins, issued scenario references and snapshot context with your result. Published versions preserve their settlement meaning after later amendments. Version references are opaque text. Collection cursors pin the original snapshot. Reuse the same filters and order between pages. Calculations resolve omitted current versions once rather than changing versions halfway through a response.

Follow reference changes

GET /changes covers markets, mappings, families, scenario versions and coverage. Without a cursor, it establishes a current watermark without backfill. Save next_cursor and retain resource/family filters. Expired cursors require an explicit resnapshot. Reference updates are separate from price ticks and private customer estimates. The reference stream uses the same recovery model.