The market looks deeper than it really is.
Live order books and trades for 14,000+ crypto pairs, 150+ columns each, in real time. One API for your dashboard or your agents.
Bid depth to −5% fell on three pairs in the last four hours. ARB on Bybit lost 62% of it, and its median level lifetime is down to 210 ms.
Every exchange, one set of numbers
Every exchange publishes its order book differently. Four steps turn them all into the same row.
An open stream to the full order book and trade feed on every venue. Every pair, nothing filtered out, nothing sampled on the way in.
Venues stamp their events differently. Every update is snapped to one shared clock so a row means the same thing everywhere.
150+ columns per pair, live: depth bands, order ladders, book churn, trade flow, outsized trades, enrichment and context. Measurements only, never scores.
A dashboard for people; REST, MCP and a CLI for code. The same row behind every one of them.
·
ask
What each number actually tells you
Depth bands
How much money is resting on the book within a given distance of the current price. In plain terms: how much you could sell into before the price starts moving against you.
Bands are percentage moves, not basis points: bid depth to −5%, −10%, −15%, −20%, ask depth to +30% and out to +400%, plus the full book on both sides.
Order ladders
A depth band gives you one total. The ladder gives you the shape of it: how much money is stacked right against the price, and how much sits far enough out that it will never be touched.
Two pairs can carry the same depth and behave nothing alike. Depth on its own will not tell you which of them you can actually sell into.
Book churn
Liquidity added and removed on each side during the window, how many price levels changed, and how long a level survives before it is pulled.
This is how a book can look deep and still behave thin. Median level lifetime and the flicker count separate resting size from size that leaves when you reach for it.
Trade flow
What actually traded: taker buy versus sell volume, trade counts, average trade size and average price on each side, and the single largest print of the window.
Resting size is intent; this is execution. Read it against the depth bands to see whether the book absorbed the flow or moved out of its way.
Outsized trades
Trades that came in far above the pair's own recent average size, counted and totalled at four thresholds (1.5×, 2×, 3× and 6×), split by side.
Each threshold is relative to that pair on that venue, so a big print on a thin altcoin and a big print on BTC are both caught. Counts, not conclusions.
73 columns in these five families. The rest carry candles, trade timing, near-touch depth, market-order cost, trade sizes, enrichment, market context and row quality.
Your agent can read the same numbers
Connect BlackForge to Claude, Cursor or anything that speaks the Model Context Protocol, and ask about the market there instead. Same rows, same entitlements, one API key.
Every tool returns the same JSON the REST API returns.
Software can pay for one request
Normal API access works the way you expect: make an account, get a key, call the endpoint. There is also a second way in, for programs nobody gave an account to.
Call with no key and the answer is HTTP 402, the status code for “payment required”, carrying a price and an address. Settle $0.005 in USDC, repeat the request, get the rows. That exchange is the x402 standard.
USDC on Base. Up to 100 rows a call, all 150+ columns, a 90-day window. No account, no API key, no minimum.
Every plan reads the same numbers
What changes is how far back you can look, how fine the windows are, how many columns you can query, how much you can pull at once, and how much you can ask the agent.
- Binance, MEXC and Gate
- Daily granularity, 2-week window
- 41 columns per pair
- Dashboard access
- A taste of the agent
- Every venue
- Hourly granularity, 3-month window
- 75 columns per pair
- REST API and MCP connector
- Agent included
- 5-minute granularity
- 1-year window
- All 150+ columns
- 50M rows a month, 3 seats
- 5× Pro's agent usage
- Everything in Max
- Minute-level granularity
- Full archive, 500M rows a month
- 10 seats
- Scheduled delivery
- Live formulas with notifications
- 20× Pro's agent usage
- No account, no API key
- Paid in USDC on Base over HTTP 402
- All 150+ columns, up to 100 rows a call
- Minute-level granularity
- 90-day window
History windows are entitlements, not retention. The archive is kept forever. CSV export, the CLI and the agent skill are on every plan, Free included. Every plan starts on Free, and paid plans are self-serve.
Straight answers
What is BlackForge?
BlackForge is raw market data for crypto. It streams live order-book and trade data from the major spot exchanges, every pair (14,000+ of them), and publishes 150+ measurement columns per pair: volume, trade flow, order-book depth bands and ladders, book churn, new listings and more. Humans read it through a dashboard and API; autonomous agents read the same data through a single pay-per-call endpoint over x402. These are raw measurements, not trade calls.
What is the x402 protocol, and how does pay-per-call work?
x402 is HTTP 402 Payment Required, put to work. An agent requests data, gets a price back over HTTP instead of a paywall, settles a stablecoin micropayment on-chain (USDC on Base), and receives the data in the same round trip. No account, no API key, no subscription. Roughly $0.005 per call.
Which exchanges does BlackForge cover?
The major spot exchanges, streamed in real time: Binance, Bybit, OKX, Coinbase, Kraken, KuCoin, Bitget, Gate and MEXC. Every pair on those venues is covered, nothing filtered out, long tail included, and every new pair is tracked from its first trade.
Do you cover perpetuals and derivatives?
Spot markets across the major exchanges today. Derivatives are not covered yet.
How fast is the data?
Data is streamed live from the venues as events happen and measured in real time: the finest bars (Ultra and pay-per-call) are at most a minute old, and smaller plans read coarser rollups of the same data. Agents paying over x402 get their response in the same request, typically well under a second including on-chain settlement.
Do I need an account or API key?
It depends who you are. For humans, you make an account and the dashboard opens on the free plan straight away, with no card and no waiting; paid plans are self-serve from the console. Agents need neither: they point at one endpoint and pay per call over x402, with no account, no API key and no onboarding.
How much does BlackForge cost?
There are four plans plus pay-per-call. Free covers Binance, MEXC and Gate at daily granularity, with a 2-week history window and 41 columns per pair. Pro ($29/month, $290/year) opens every venue at hourly granularity, with a 3-month window and 75 columns. Max ($99/month, $990/year) is the full product: 5-minute granularity, a 1-year window and all 150+ columns. Ultra ($399/month, $3,990/year) adds 1-minute granularity and scales Max to the full archive, 500M rows a month, 10 seats and scheduled delivery. Agents can skip plans entirely: $0.005 per call over x402, up to 100 rows per call at 1-minute granularity, all 150+ columns and a 90-day window, paid in USDC on Base with no account or API key. History windows are entitlements, not retention. The archive is kept forever. Every plan starts on Free, and paid plans are self-serve.
Is this financial advice?
No. BlackForge provides raw market data, not investment advice or a recommendation to trade. Crypto markets are volatile and you trade at your own risk. We give you the raw numbers; the decision is yours.
See it on the pairs you actually trade
Pick the exchanges and pairs you watch and the dashboard opens with their history already loaded.
The major exchanges · 14,000+ pairs · 150+ columns per pair · live
