Why Is Exchange Netflow Always Behind a Paywall?
Searching for a cryptoquant alternative exchange netflow api usually ends the same way: the free tier shows a chart, the API needs a paid plan, and the on-chain endpoints sit one tier higher again. CryptoQuant's own API documentation files exchange flows under its on-chain categories, and the third-party pricing trackers we checked in October 2026 put on-chain API access at its Professional plan, around $99-109 a month. We could not confirm plan contents from CryptoQuant's pricing page itself, so check it before quoting anyone.
The reason it costs money is honest: watching exchange wallets means running nodes, maintaining an address registry and decoding transfers on every chain. We do that work and serve the result at GET /api/v1/on-chain/exchange-flows/{symbol} on the free tier, with hourly history since 2026-05-28 and a live feed of transfers above $1M.
What this post does is say plainly what is covered. Exchange-flow data is only useful if you know which wallets are watched, which chains, and what a zero means. Ours answers that in the response itself.
Token Flows on 7 Chains vs Native BTC: What Is Actually Measured
There are two different measurements under one endpoint, and you should know which one you are reading.
- Token flows on 7 chains. ERC-20 style transfers to and from known exchange wallets on Ethereum (50 tokens incl. USDT, USDC, WBTC, WETH, LINK, PEPE, ONDO, ENA), BSC (9), Base (7), Arbitrum (5), Optimism (4), Tron (USDT, USDC) and Solana (13 symbols incl. SOL native, JUP, BONK, WIF). Transfer events are decoded directly from nodes, so both directions are captured on the EVM chains.
- Native BTC. Balance deltas on a short list of exchange wallets via mempool.space. Since 2026-10-18 that list is Binance, Bybit and OKX, each taken from the exchange's own proof-of-reserves address list. Coinbase and Kraken publish no BTC addresses, so their BTC flow is
null. WBTC, BTCB and CBBTC are separate symbols with their own token flows.
Two caveats are stated in the docs and worth repeating. Solana inflows are systematically low: deposits land in per-user token accounts the hot-wallet scan does not see, so SPL net flow is biased toward outflow while withdrawals are accurate. Native ETH is live-only, polled by balance delta from collector start, so for backtests before that use WETH.
Everything here is token-native units: USDT flows in USDT, BTC flows in BTC. The windows do not convert to USD for you except on the spike-alert feed, which carries amount_usd at live price.
How Do I Get Exchange Netflow for a Symbol via API?
One call per symbol. The top-level windows are summed across every chain the symbol exists on; by_chain breaks the same windows down per chain.
curl "https://cryptodataapi.com/api/v1/on-chain/exchange-flows/BTC" \
-H "X-API-Key: cdk_live_your_key"Illustrative response (shape exact, numbers invented):
{
"symbol": "BTC",
"exchange_filter": null,
"as_of": 1792828800,
"windows": {
"1h": {"inflow": 212.4, "outflow": 180.1, "net": 32.3},
"6h": {"inflow": 1410.9, "outflow": 1602.7, "net": -191.8},
"24h": {"inflow": 5120.2, "outflow": 5890.0, "net": -769.8},
"7d": {"inflow": 33810.5, "outflow": 35102.9, "net": -1292.4}
},
"per_exchange_24h": {
"binance": {"inflow": 3100.0, "outflow": 3550.2, "net": -450.2},
"coinbase": null,
"kraken": null,
"bybit": {"inflow": 1020.2, "outflow": 1200.8, "net": -180.6},
"okx": {"inflow": 1000.0, "outflow": 1139.0, "net": -139.0}
},
"exchanges_covered": ["binance", "bybit", "okx"],
"by_chain": {"btc": {"1h": {}, "6h": {}, "24h": {}, "7d": {}}},
"chains_covered": ["btc"],
"spike_zscore_1h": 0.4,
"spike_zscore_24h": -1.1
}Read the sign the way the docs state it: positive net = deposits (often bearish, sell-side liquidity arriving), negative net = withdrawals (often bullish). spike_zscore_1h compares the latest hour with its baseline; above 2 is statistically unusual for that symbol.
The field that protects you is exchanges_covered. An exchange with no watched wallet for the symbol is null in per_exchange_24h, not 0.0, and ?exchange=coinbase on BTC makes every window null. Before 2026-10-17 those read zero, which a bot cannot tell apart from a quiet day. Now null means unknown, and 0 means measured zero.
History Since 2026-05-28 and the $1M Transfer Feed
Hourly history. GET /api/v1/on-chain/exchange-flows/{symbol}/history returns archived flow sampled about every 30 minutes since 2026-05-28. Each point carries ts, trailing inflow_1h / outflow_1h / net_1h, the same for 24h, the chains present and a per_exchange_1h map. Default is the last 7 days at interval=1h (the last sample per UTC hour); interval=raw gives every sample; start / end accept ISO 8601 or unix, end exclusive, up to 93 days per call.
curl "https://cryptodataapi.com/api/v1/on-chain/exchange-flows/USDT/history?start=2026-10-01&end=2026-10-08&interval=1h" \
-H "X-API-Key: cdk_live_your_key"Large transfers. GET /api/v1/on-chain/exchange-flows/spike-alerts is the live feed of the last 500 transfers (roughly 10 hours) to or from tracked exchange wallets at or above min_amount on the live-price-converted amount_usd, default $1M. Each alert has ts, chain, symbol, exchange, direction, amount with unit, amount_usd, counterparty and source.
source is the field to filter on. transfer is a decoded Transfer event with a real counterparty. balance_delta is inferred from a change in a watched wallet's balance, which can be the exchange moving coins between its own hot and cold wallets. For a deposit signal, use ?source=transfer; for native BTC, ETH and SOL, balance deltas are all there is, so weight them accordingly. Full history since 2026-10-08 lives in the exchange_flow_spikes snapshot type on /backtesting/snapshots (Pro Plus); each 5-minute snapshot holds only rows first seen that tick, so a range lists each transfer once.
Exchange Reserves: /market-intelligence/exchange-balance
Netflow is the derivative; reserves are the level. GET /api/v1/market-intelligence/exchange-balance returns one row per exchange with exchange_name, total_balance_usd, clean_balance_usd and balance_change_usd_1d / _7d / _30d, built from DefiLlama's proof-of-reserve data since 2026-07-22 with our own on-chain BTC sweep for the exchanges we source directly.
Two things to know before charting it. The USD figures cover all assets, not just BTC; the BTC-denominated balance is populated only where btc_covered is true, with btc_source saying whether it came from our chain sweep or DefiLlama. And only exchanges that publish reserve wallets appear: Coinbase and Kraken do not, so a sum over the rows is not "all exchanges". The source field marks the series era so a consumer never splices it onto the older CoinGlass numbers archived as coinglass_exchange_balance.
CryptoQuant-Style Netflow vs This API
| Typical on-chain vendor | cryptodataapi.com | |
|---|---|---|
| API on free tier | Usually market data only; flows on a paid plan | Live flows, history and spike alerts on Free |
| Native BTC exchanges | Broad entity clustering across many exchanges | Binance, Bybit, OKX from proof-of-reserves lists; Coinbase and Kraken null |
| Token flows | Varies by vendor | 7 chains, 70+ symbols, per-chain by_chain |
| History depth | Years | Hourly from 2026-05-28; 90 days of daily snapshots in the archive |
| Unknown vs zero | Often indistinguishable | null + exchanges_covered |
| Transfer-level feed | Alerts product, often separate | /spike-alerts, $1M default, source tagged |
The trade is explicit: less history and a narrower BTC entity list in exchange for a free, forward-honest feed you can wire into an agent today. If your edge is a multi-year BTC netflow backtest across twenty exchanges, this is not it yet.
How to Use This in a Bot (and When Not To)
A netflow read works as a context flag, rarely as a trigger. A minimal loop:
import httpx
BASE = "https://cryptodataapi.com/api/v1"
H = {"X-API-Key": "cdk_live_your_key"}
f = httpx.get(f"{BASE}/on-chain/exchange-flows/BTC", headers=H, timeout=30).json()
net_24h = f["windows"]["24h"]["net"]
z = f["spike_zscore_1h"]
covered = f["exchanges_covered"] # ["binance","bybit","okx"] for BTC
flag = "deposit_pressure" if (net_24h > 0 and z > 2) else "neutral"
print(flag, "based on", covered)- Log
exchanges_coveredwith every decision. A BTC read is three exchanges, not the market. - Do not treat Solana inflows as complete; use outflows or the EVM chains for the deposit side.
- Filter alerts by
source=transferunless you want internal rebalancing in your signal. - Cross-check with
/on-chain/dormancy/btc, whoseexchange_net_flow_usd_24hcomes from Coin Metrics and is independent of our wallet registry. - Poll every 5 minutes at most; the collector refreshes on that cadence.
For how an agent should read a spike z-score, see Exchange Inflow Spikes; for the stablecoin side of the same picture, Stablecoin Flows as a Market Indicator.
Frequently asked questions
Is there a free exchange netflow API alternative to CryptoQuant?
Yes. GET /api/v1/on-chain/exchange-flows/{symbol} returns 1h/6h/24h/7d inflow, outflow and net for 70+ symbols across Ethereum, BSC, Base, Arbitrum, Optimism, Tron and Solana plus native BTC, on the free tier, with hourly history from 2026-05-28.
Which exchanges are covered for native BTC flows?
Binance, Bybit and OKX, each from the exchange's own proof-of-reserves address list. Coinbase and Kraken publish no BTC addresses, so they are null in per_exchange_24h and exchanges_covered lists only the three.
What does null mean in per_exchange_24h?
That exchange has no watched wallet for the symbol, so its flow is unknown. A measured zero is 0. Before 2026-10-17 both read 0.0.
What is the difference between source transfer and balance_delta on spike alerts?
transfer is a decoded on-chain Transfer event with a real counterparty. balance_delta is inferred from a watched wallet's balance change and can be the exchange moving coins between its own wallets.



