Raw markets. Canonical facts.
Meridian provides normalized crypto futures, spot, and custom trade-bar data through a stable, DataFrame-ready contract. Developers connect through Context Protocol using its TypeScript SDK, Python SDK, or official remote MCP endpoint.Run your first query
Query BTC futures data through Context Protocol in a few minutes.
Inspect the tool contract
Use Meridian’s stable marketplace tool ID and method names.
Explore custom bars
Work with dollar, volume, tick, and imbalance bars built from individual trades.
Understand data quality
Read coverage, provenance, source-limited, and no-results semantics.
Current surfaces
| Surface | Exchanges | Main data |
|---|---|---|
| Futures | Binance, Bybit, OKX, Hyperliquid | OHLCV, trade flow, open interest, funding, premium, liquidations |
| Spot | Binance, Bybit, OKX, Coinbase | OHLCV and buy/sell trade flow |
| Custom bars | Binance Futures | BTCUSDT dollar, volume, tick, and imbalance bars |
Meridian returns stored facts. Missing or venue-limited values remain explicit through coverage metadata, provenance, warnings, and nulls. They are never silently converted to zero.
Integration boundary
The public integration layer is Context Protocol. The underlying Meridian HTTP routes define the data contract, while the marketplace tools provide authenticated discovery, billing, execution, and MCP access. Meridian provides market data only. It does not place orders, approve trades, manage capital, or expose trading-bot behavior.Continue to Quickstart
Create a Context API key and run a pinned Meridian query.