CoinAPI Market Data API

What it is

One HTTP and WebSocket interface over trades, quotes, order books, OHLCV, options chains and derivatives metrics from the venues CoinAPI has integrated, with a single symbol scheme — BINANCE_SPOT_BTC_USDT — instead of each exchange's own. The thing being sold is normalisation and the archive behind it, not the prices: the exchanges publish most of these ticks themselves.

It is one of six products under the same brand. Exchange Rates (aggregated VWAP reference rates), Indexes, Flat Files, EMS Trading and Exchange Link are separately bought and separately priced, and the pricing below covers only the Market Data API. If what you want is one conversion rate per asset rather than a tape, the Exchange Rates API is the cheaper product and this is the wrong card.

The company behind it renamed: the footer on every page reads "API BRICKS LTD F/K/A COINAPI LTD", and API Bricks also publishes FinFeedAPI. The product, the docs and the support address are still CoinAPI.

Pricing

There is no free plan. The vendor says so in its own FAQ, and the entry point is a metered Pay As You Go account with $25 of credits that requires a verified payment method before a key is issued. That is a trial balance, not a free tier, and it is the single biggest change from the product most readers will remember.

Monthly rates, from the pricing page's monthly toggle — Startup $79, Streamer $249, Pro $599, with annual billing at $69, $199 and $499 per month respectively. Enterprise is quoted.

Two meters run at once and they are not interchangeable:

• REST credits, one per call, except that a call using the limit parameter is billed one credit per 100 data points returned. Startup 1,000/day, Streamer 10,000/day, Pro 100,000/day. Metered overage starts at $5.26 per 1,000 credits for the first thousand used in a day and falls to $0.03 per 1,000 above 25 million a day.
• WebSocket bytes, split into Tier 1 (trades, quotes, order books) and Tier 2 (metadata, OHLCV, exchange rates). Startup includes 32 GiB of Tier 1 a day and no Tier 2 at all — Tier 2 is billed at $0.0625 per MiB on that plan, which is $64 per GiB. Streamer includes 128 GiB Tier 1 and 1 GiB Tier 2; Pro, 512 GiB and 64 GiB.

FIX is included on Pro and an add-on at $99 a month below it. LMAX Digital data is a $500 a month unlock, and a FIX session into a oneZero Hub is $499 a month. Cards, crypto and bank wire are all accepted.

Data & coverage

The headline numbers on the product page are 400+ integrated exchanges, 916k+ symbols, 18k+ assets and 678 TB+ of history. The Flat Files pages on the same site say 632 TB and 380+ exchanges, so take the order of magnitude and not the digits.

The exchange count is worth pulling apart, because CoinAPI publishes the underlying table. Its A–Z supported-exchanges metadata tables carry 405 exchange IDs, of which 137 have any trade-data range at all and 114 run to the table's own cut-off. The other 268 — Satang Pro, STEX, SeedCX, SurBitcoin and the rest — are integrations against venues that no longer trade. That is how a coverage count reaches 400.

History goes back further than the marketing does. The spot page says "since 2014"; the earliest data_trade_start in the published tables is 2011-09-13. Which venues go that deep is answerable from the same tables before you pay for anything.

DEX coverage is narrow and recent. The supported venues are Uniswap V2 and V3, SushiSwap V2, Curve and Balancer V2 on Ethereum; Uniswap V3, SushiSwap V2 and DODO V2 on Arbitrum; plus dYdX V3 and Hyperliquid. DEX trade history starts 2023-11-22 (Hyperliquid, 2024-09-27). CoinAPI is explicit that this is pool-derived prices and swap transactions rather than chain indexing, so there are no holder counts, flows or labels here — that is a different category of product.

Derivatives are the strongest part of the catalogue: funding rates, settled funding rates, open interest, mark price, liquidations and implied-volatility metrics, plus options grouped by underlying, expiry and strike, and Hyperliquid L4 order-lifecycle events over the WebSocket DS endpoint.

Real-time latency is not published as a number. What is published is the routing — a GeoDNS default at rest.coinapi.io and explicit EMEA, APAC and NCSA endpoints you can fail over between yourself.

Integrations

Six protocols, listed per plan on the pricing page: MCP, REST, JSON-RPC, WebSocket V1, WebSocket DS and FIX. REST answers in JSON or, with output_format=csv, in CSV — which is why the same endpoint works from a spreadsheet's IMPORTDATA as from a client library.

The MCP row is ticked on every plan including the metered one, and the servers are real rather than announced: an unauthenticated POST to mcp.md.coinapi.io/mcp answers 401 with a message naming the four headers, the query-string parameter and the URL form it will accept a key in. Separate endpoints exist for the Indexes and Flat Files products.

Helper libraries are listed for Python, JavaScript, TypeScript, Node.js, Go, Java, .NET, C#, C++, PHP, Ruby, R, Matlab and Haskell. Flat Files, the bulk-history product, is reached over an S3-compatible API and is also available through Snowflake.

Limitations

No free tier, and a card on file before the first call. Anyone prototyping against a dozen providers will find this the expensive one to evaluate.

Displaying the data to your users is redistribution. The usage policy puts customer-facing dashboards, public APIs, trading terminals, white-label platforms, market-data widgets and reselling on the not-permitted side, and says a redistribution agreement may be required if your customers can access the data at all. Internal trading, research, risk and ML are allowed. This is a licence question and it is not on the pricing page.

One concurrent WebSocket session per subscription. The FAQ says subscriptions typically allow only one, and that concurrent connections on shared credentials can trigger hard limits and dropped connections. A dev environment and a production environment therefore want two accounts, not two keys.

The published reference tables are stale. Every live venue in the supported-exchanges tables has a data_trade_end of 2026-01-23, which is when the tables were last generated, not when the data stopped. Read inside that: Uniswap V2 and V3 on Ethereum end 2025-04-14, Uniswap V3 on Arbitrum ends 2025-02-24, and Balancer V2 ends 2024-07-06, while every CEX row runs to the cut-off. Confirm the DEX range you need against a live call before committing to it.

Rate-limit headers are not guaranteed. X-RateLimit-Request-Cost is always returned, but the docs say X-RateLimit-Remaining and X-RateLimit-Reset are deliberately omitted from some responses for latency reasons and that there is no way to force them on. A client that budgets requests from those two headers has to tolerate their absence.

No published per-second or per-minute REST limit. The quotas are daily. The vendor's own FAQ has a heading asking what the current rate limits and latency expectations are, and no answer underneath it.

No uptime SLA on the metered plan. Pay As You Go shows a dash in the SLA row. The 99.9% uptime SLA covers Startup, Streamer and Pro alike, and Enterprise is custom — so the SLA is not what the two upper subscription tiers buy you. No plan below Enterprise carries a latency SLA at all.

Alternatives

Within the same vendor, the Exchange Rates API is the right product if you want one VWAP number per asset rather than a venue-by-venue tape, and Flat Files is the right one if you are filling a backtest rather than running a service — paying REST credits to page through years of history is the expensive way to do that.

Outside it, the comparison a reader usually wants is against CoinDesk Data, which has a longer aggregate history and news and on-chain endpoints in the same API, but no published prices at all. CoinAPI's advantage in that pair is that you can read the whole price list, work out what your query costs and start without talking to anyone. See the rest of Crypto Market Data APIs for the wider field.