Data & Analytics
The same intelligence, with full history.
Point-in-time history of everything we publish, on the same schema as the live feed, so a backtest reads exactly what was published at the time.
- Full history back to 2020
- Point-in-time, as published
- Identical schema to the live feed
- Range queries and bulk export
Bitcoin 30-day BSIV, 13 daily fixes from 30 Jul 2026 to 12 Aug 2026: from 35.67% to 38.91%, ending at 38.31% — the same value published on the live indices. The published archive runs back to 2020; this shows the most recent 13 fixes we hold at this granularity, each on the date it was actually published.
What you get
What the market read on the day.
Every value is the one we published at that moment, on the same schema the live endpoints serve today. A strategy tested against it sees exactly what was available at the time, point-in-time with no lookahead, and the backtest reconciles directly with your production feed.
Coverage
- History since
- 2020
- Spot & perpetual indices
- 150+
- Data points / day
- 250M+
- Instrument listings catalogued
- 1.8M+
Depth & resolution
Query at the resolution your research requires.
Point-in-time history for the reference indices, derivatives and volatility surfaces this site publishes live — the same intelligence, running backwards to 2020. Daily fixes are the default across the site; hourly and minutely resolution are available through Data Plans.
Tick-level data and custom aggregations finer than a minute are available on request.
Survivorship
1.8M+
Instrument listings catalogued, ever
Delisted instruments remain in the record.
An instrument that has expired or been delisted stays in the record exactly as it was, and remains in the catalogue after it stops trading. A study built only on current listings sees only the survivors; one built on this record sees the whole population, failures included.
Why that matters for a backtestREST API
One endpoint, a JSON body, your history back.
Some integrations need a defined range once, without a persistent connection: a nightly batch job, a one-off backtest, or a script pulling last quarter’s prints. REST fits that shape: a POST request with an API key, a JSON body naming the asset and window, and the same data the live endpoints serve back as JSON.
Read the full API referenceHeaders
Content-Type: application/json
X-API-Key: ••••••••••••
Body
{
"exchange": "composite",
"base_asset": "BTC",
"asset_type": "option",
"expiry": "30d",
"start": "LATEST",
"end": "LATEST",
"frequency": "1h",
"options": {
"format": {
"timestamp": "ms",
"hexify": false,
"decimals": 10
}
}
}Endpoints
How far back you can query is set by billing period — a weekly window monthly, a one-year rolling window quarterly, three years annually, extendable to the 2020 floor. See Data Plans for the current tiers.
Delivered over
RESTMCPPull OraclePush Oracle
Use cases
What teams build on Historical Data
- Prop TradingBacktesting Systematic Options Strategies with Historical Vol DataBacktesting systematic options strategies — delta-hedged straddles, calendar spreads, vol targeting — across years of calibrated historical volatility data. Test strategy performance across multiple market regimes before deploying capital.Read the story
- AI-Driven Strategy Backtesting via MCPAI agents design, execute, and iterate on cross-asset derivatives backtests through MCP — mixing options, futures, perpetuals, and spot in a single conversation. Theoretical and listed pricing modes reveal the gap between model edge and executable edge.Read the story
- Hedge FundSystematic Strategies: Identifying Vol Regime Shifts in Crypto DerivativesSystematic strategies that identify volatility regime shifts through term structure spreads and skew metrics across crypto derivatives markets. Evaluating the spread between 30-day and 7-day implied vol alongside 25-delta risk reversals to generate alpha.Read the story
Get started
Integrate Historical Data into your own systems.