Coverage
What you get
| Item | Detail |
|---|---|
| Product code | CR-REFERENCE-RATES |
| Coverage | Major coins against USD, and multi-coin indices with constituents |
| Granularity | From per-second publication up to a daily fixing, by rate |
| History | From each rate's first publication |
| Delivery | REST and WebSocket |
| Update speed | At each publication time |
Bitcoin trades on dozens of venues at once, and at any moment their prices differ. A reference rate picks the venues, cleans out bad prints, and combines the rest over a short window into one number. The window is interval_start to interval_end; the method behind it lives at methodology_url. A reference rate is only as good as that method, so we'd publish it before the first value.
Schema
Schema
| Field | Type | Required | Description |
|---|---|---|---|
index_code |
string | yes | e.g. MD-BTC-USD-RR |
timestamp |
string | yes | Publication time, ISO 8601 UTC |
interval_start |
string | optional | Calculation window start |
interval_end |
string | optional | Calculation window end |
value |
number | yes | Rate or index level |
open |
number | optional | Bar open, for candle output |
high |
number | optional | Bar high |
low |
number | optional | Bar low |
close |
number | optional | Bar close |
constituents |
array | optional | asset, weight for multi-coin indices |
methodology_url |
string | optional | Link to method document |
Example record:
{
"index_code": "MD-BTC-USD-RR",
"timestamp": "2026-11-19T16:00:00Z",
"interval_start": "2026-11-19T15:59:00Z",
"interval_end": "2026-11-19T16:00:00Z",
"value": 77634.18,
"constituents": null,
"methodology_url": "https://marketdata.co/methodology/reference-rates"
}
The value is an example, not a bitcoin price. constituents is null because a single-coin rate has none.
Sample data
Sample data
There's no reference rate sample, since we haven't published a rate. If you need daily bitcoin prices today, the free Bitcoin daily OHLCV file covers January to October 2026. Note that it's BTC/USDT from a single exchange, which is exactly the kind of price a reference rate improves on. For a reference rate sample later, leave your coins and fixing times on the form.
Use cases
Use cases
Fund and portfolio valuation. If you mark crypto holdings once a day, use one documented value at a fixed timestamp, the same every day. That gives a valuation you can defend to an auditor or a client.
Settling derivatives and contracts. Payouts tied to a crypto price need a source both sides accept. A reference rate with a public methodology_url is that source.
Tracking a basket. For a multi-coin index, constituents lists each asset and weight. Rebuild the index yourself from our coin prices to check how a rebalance changed your exposure.
Clean backtest prices. Prices from a single exchange carry that exchange's outages and flash crashes. A rate built from several venues smooths those out, which matters for end-of-day strategies.
Code
Code examples
Example: daily BTC reference rate history with curl.
curl "https://api.marketdata.co/v1/crypto/reference-rates?index_code=MD-BTC-USD-RR&start=2026-01-01&end=2026-11-19" \
-H "Authorization: Bearer $MARKETDATA_API_KEY"
Example: Python, compare the reference rate with one exchange's close.
import os
import requests
import pandas as pd
headers = {"Authorization": f"Bearer {os.environ['MARKETDATA_API_KEY']}"}
rr = requests.get(
"https://api.marketdata.co/v1/crypto/reference-rates",
params={"index_code": "MD-BTC-USD-RR", "start": "2026-10-01", "end": "2026-11-19"},
headers=headers,
)
rr.raise_for_status()
ref = pd.DataFrame(rr.json()["results"])
ref["date"] = pd.to_datetime(ref["timestamp"]).dt.date
bars = requests.get(
"https://api.marketdata.co/v1/crypto/bars",
params={"symbol": "BTC-USD", "timeframe": "1d", "start": "2026-10-01", "end": "2026-11-19"},
headers=headers,
)
bars.raise_for_status()
px = pd.DataFrame(bars.json()["results"])
px["date"] = pd.to_datetime(px["timestamp"]).dt.date
both = ref.merge(px, on="date")
both["gap_bps"] = (both["close"] / both["value"] - 1) * 10000
print(both[["date", "value", "close", "gap_bps"]].tail())
Pricing
Pricing
Crypto reference rates are not offered at launch and have no price yet. They won't be sold as a dataset. For most trading uses, the cross-exchange price in our crypto prices API will do the job. It's planned free at 60-second updates and real-time from Starter at $29/mo.
One vendor we studied gives its crypto indices away free. Paid plans from others run $64 to $1,500 a month, based on 2 prices.
Side by side
How we compare
5 of the 50 providers we studied sell crypto reference rates or indices, and the serious ones are regulated benchmark administrators. We aren't one, and we won't sell a rate as fund-grade until we are. If we publish rates, every value will link to its method, show its calculation window, and download in the same shape as our crypto bars.
FAQ
Frequently asked questions
What is a crypto reference rate?
A single price for a coin, calculated from trades on several exchanges over a set window using a published method. Funds and contracts use it so everyone agrees on one number.
Why isn't it available now?
Rates that funds settle against fall under benchmark regulation, including the EU Benchmarks Regulation. We'll only publish once we can do that properly.
What time zone are timestamps in?
UTC. Common fixing times like 4 p.m. London are stored as their UTC equivalent, which shifts by an hour with UK summer time.
Is it real-time?
Some rates would publish every second over WebSocket, others once a day. Each rate's methodology_url will state its schedule.
How is this different from your crypto price API?
The crypto price API gives a cross-exchange price for trading and charts. A reference rate adds a fixed calculation window and a published, stable method for settlement and valuation.
What format does it come in?
JSON from REST and WebSocket, with optional open, high, low and close for candle output.
Keep reading
Related
- Asset hub: Crypto
- Crypto: BTC-USD, ETH-USD, SOL-USD, XRP-USD, BNB-USD, DOGE-USD
- Docs: API reference: crypto
- Learn: What is OHLCV data, Choosing a market data provider