Why BytNode

#Fourteen families, one API

121 REST routes, a real-time WebSocket stream and an MCP server, all on the same contract. What usually takes several subscriptions — a market-data feed, a derivatives provider, an on-chain service, a macro source — is one key here:

• Market and order flow: OHLCV candles from 1 minute to 1 week, individual trades and ticks, large trades, aggregated order book, trade candles (spot, futures, combined), CVD, VWAP, buy/sell ratio, inter-venue spread.
• Derivatives and liquidations: settled, next and cumulative funding, basis, open interest, long/short account ratio, individual and cumulative liquidations, big versus small liquidations, and the liquidation heatmap clusters the price is drawn to.
• Options on BTC and ETH: open interest and volume by calls and puts, put/call ratio, ATM implied volatility and its candles, max pain per expiry, OI per strike, and greeks recomputed under one convention.
• Fundamentals: tokenomics and market cap, total market and dominance, Fear & Greed, spot ETF holdings anchored on SEC filings, Bitcoin network (fees, mempool, mining, difficulty), Ethereum (gas, supply and burn, staking, DeFi), on-chain valuation (MVRV, NVT, active addresses, miner stress).
• Macro: daily FRED series, intraday macro candles (dollar index, FX, gold, oil, US yields, VIX), net liquidity, BTC-macro correlations, macro momentum and a risk-on / risk-off score — and 20 technical indicators computed server-side.

Every family speaks the same language: same envelope, same timestamps, same units, same error codes. What you learn on one route holds on all of them.

#Aggregated, not one exchange

Every number is built from the major spot and perpetual futures venues, not read from one exchange. Volumes are summed, funding and basis are weighted by open interest, prices by volume — and the method is written down for each metric on the Conventions page.

Every multi-venue row says how many venues contributed (venue_count, exchange_count), and the snapshot adds a coverage key. A single-exchange feed shows one venue’s view of the market; an aggregated one shows the market.

#Depth on the assets that matter

22 pairs: BTC, ETH, SOL, XRP, DOGE, BNB, TRX, SUI, HYPE, XLM, XMR, LINK, ADA, LTC, UNI, GRAM, AVAX, HBAR, NEAR and TAO on spot and perpetual futures, plus the USDC and USDT stablecoin pairs. Together they are about 93 % of the total crypto market capitalisation (measured on 2026-09-30: 2.69 of 2.88 trillion USD).

This is a deliberate choice, not a gap: rather than thin coverage of thousands of tickers, each of these assets gets every family of data from every venue that lists it — order flow, derivatives, liquidations, options where they exist, fundamentals. Quality and depth on the assets people actually trade; new assets are added when they reach that level.

#Numbers you can trust

• is_closed on every bucketed value: true means final and never rewritten, so a backtest never trains on a number that will change.
• unavailable on every empty answer says why — not_applicable, no_api_key or no_data — so “no measure” is never mistaken for “nothing happened”.
• Every numeric field has a documented unit (percent, fraction, basis points, USD, base asset), carried in the OpenAPI contract next to each field.
• Going beyond your plan is an explicit refusal with a stable error.code, never a silently truncated answer.
• Every example in this documentation is a real response, and the documentation is checked automatically against the API.

#Built for AI agents

An agent that reads this API can use it without a bespoke integration:

• A native MCP server with three tools and 73 fields, used with your own key.
• Machine-readable references: /openapi.json with schemas, units and real examples, llms.txt and llms-full.txt, a Postman collection.
• One-request context: the snapshot returns up to 61 fields for a symbol in a single call.
• Errors an agent can act on: a stable error.code, the parameter at fault in error.param, and the fix in the message (“did you mean limit?”).

#Priced for builders

The cheapest paid plan, per month (billed yearly · billed monthly), and what two million requests a month cost (billed yearly):

And a free plan to start: 10,000 requests a month, four families, no card. The plans, their families and their history depth are on the pricing page.

#Start in three minutes

Create a free key, make your first call, then go deeper.