The data layer behind this terminal — open
Every chart on Depth Radar is drawn from the JSON API documented here, and the same API is open to you and to your agents: no key, no signup, open CORS. Live multi-venue CVD, footprint cells, order-book walls, confirmed divergences, liquidations and long-horizon Bitcoin models — the exact data we trade-watch ourselves, served raw.
Base URL: https://app.depthradar.com · Rate limit: 10 req/s per IP (burst 30, then HTTP 429) · Symbols: BTCUSDT, ETHUSDT · All GET, all JSON · OpenAPI spec · llms.txt
For AI agents: MCP server
Point any MCP-capable agent (Claude, or anything speaking Streamable HTTP) at:
https://app.depthradar.com/mcp
Stateless JSON-RPC, no auth. The server exposes eight tools: get_ticker, get_live, get_history, get_divergences, get_liquidity_zones, get_footprint, get_btc_models, get_markets. Heavy series are trimmed to agent-friendly portions by default (a context window is not a time-series database), with parameters to pull more.
curl -s https://app.depthradar.com/mcp -H 'content-type: application/json' -d '{
"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"get_live","arguments":{"symbol":"BTCUSDT"}}}'
REST endpoints
| endpoint | what you get | window |
|---|---|---|
| /api/ticker | BTC+ETH snapshot, funding, F&G, dominance, OI, 24h liquidations | now |
| /api/live?sym= | current 1m bar: OHLC, volume, 5-venue CVD, OI | now |
| /api/history?sym= | 1m bars with per-venue CVD + OI series | ~3 days |
| /api/divergences | confirmed price↔CVD divergences, non-repainting | recent |
| /api/liqzones?sym=&mins=&top= | largest resting order-book walls, tested or not | ≤7 days |
| /api/heatmap?sym=&mins=&cols= | order-book depth matrix + liquidations + day levels | ≤7 days |
| /api/footprint?sym=&tf=&tick= | sell×buy volume by price level inside candles, OHLC, delta | ~3 days |
| /api/markets | top-100 coins by 24h Binance spot volume | now |
| /api/model/btc | daily closes, drawdown, risk 0–1, cycles, power-law fit | since 2011 |
Example: live multi-venue CVD
curl -s 'https://app.depthradar.com/api/live?sym=BTCUSDT'
{ "sym": "BTCUSDT",
"bar": { "t": 1786308240000, "o": 65205.0, "h": 65214.9, "l": 65198.3, "c": 65208.1,
"vol": 142.7, "cvdBinance": 1847.99, "cvdBybit": 369.37,
"cvdBnC": 41.75, "cvdByC": 25.76, "cvdCb": 37.06 },
"oi": 107894.39, "t": 1786308267123 }CVD fields are cumulative taker deltas in coin units per venue: cvdBinance / cvdBybit — USDT perpetuals, cvdBnC — Binance coin-margined, cvdByC — Bybit inverse, cvdCb — Coinbase spot. Coin units make the venues directly comparable — and the disagreement between them is the signal.
Example: Bitcoin models for a daily briefing
curl -s 'https://app.depthradar.com/api/model/btc' | jq .summary
{ "price": 65205.03, "ath": 124658.54, "athDate": "2025-10-06", "dd": -47.69,
"daysSinceATH": 307, "risk": 0.17, "riskZone": "Deep Value",
"cycleDays": 1357, "cycleMult": 4.13, "plFair": 132393, "plDev": -50.7 }Honest limits
This API is built for what is happening now: order-flow endpoints retain roughly 3 days of minute bars and about a week of order-book history; liquidation feed covers Bybit only and resets on server restarts. The Bitcoin models endpoint is the exception — full daily history since 2011. If your agent needs deeper archives, that tier doesn't exist yet; tell us in Telegram what you'd pay for and we'll build in that order.
FAQ
Do I need an API key?
No. Every endpoint is public, CORS is open, and the rate limit (10 requests/second per IP, burst 30) is enforced by the server. If you need more, talk to us on Telegram.
Is there an MCP server?
Yes — https://app.depthradar.com/mcp speaks MCP over Streamable HTTP (stateless JSON-RPC). Point any MCP-capable agent at it and it gets eight tools covering ticker, live and historical CVD, footprint, liquidity zones, divergences, markets and Bitcoin models.
How much history is available?
Order-flow endpoints keep roughly 3 days of 1-minute bars and about a week of order-book minutes — this API is built for what is happening now. The Bitcoin models endpoint carries full daily history since 2011.
Where does the data come from?
Directly from exchange feeds: Binance futures (USDT-perp and coin-margined), Bybit (USDT-perp and inverse), Coinbase spot, plus Bitstamp for pre-2017 daily history. The aggressor side comes from each exchange's own taker flag — nothing inferred.
Can I use this in production or commercially?
Yes, within the rate limit and with attribution appreciated. No SLA is offered on the free tier; schemas are versioned informally and breaking changes are announced in the Telegram channel.