DexPaprika
DEX pool, token and swap data on 36 chains over REST and SSE, keyless to start.
by CoinPaprika
Last updated
What it is
A DEX data API from CoinPaprika, the Polish company behind the coin-ranking site of the same name. Where the CoinPaprika API sells one aggregated price per coin, this sells the pool layer underneath it: liquidity pools and the DEXes they sit on, token prices computed from those pools, individual swaps, pool reserves and OHLCV candles, keyed by chain and contract address.
The coverage page, regenerated from the live API, listed 36 chains and 244 DEXes on 4 October 2026, with more than 42 million pools and 38 million tokens indexed. Solana, Base, Ethereum and BNB Smart Chain led on 24-hour volume; the list also runs to Robinhood Chain, HyperEVM, Monad, Sui, Tron, Aptos and TON.
The buyer is a developer building a token-price feed, a pool screener, a trading bot's data layer
or an agent that needs on-chain prices without running indexers. The website at dexpaprika.com is
a DEX tracker on the same data; this card is about the API.
The endpoints. Networks; DEXes on a network; pools on a network, on a DEX or filtered across networks by liquidity, volume, age and similar; a single pool; pool OHLCV; pool transactions, paged up to 100 pages; token details, the pools a token trades in, top tokens and token filtering; batch prices for up to ten tokens per call; token OHLCV; search across tokens, pools and DEXes; global stats; and a call that reports your own plan and credit usage.
Pricing
Four self-serve levels and a contract. Keyless and Free cost nothing and differ by allowance: 10,000 credits per IP against 100,000 per key, both over a rolling 30-day window that returns credits 30 days after they were spent rather than resetting on the first of the month. Dev is 30 dollars a month and Pro 99, or 86 a month billed annually; Dev showed the same 30 on both billing tabs. Prices exclude VAT.
The unit is a plain credit — one request, one credit, no compute units — with two multipliers that
are not obvious: a batch price call costs one credit per token in it, and every update a stream
delivers costs one credit. Running out returns HTTP 402, not 429; a 429 means the per-minute
cap and carries a Retry-After. On Free access stops at the limit; Dev and Pro auto-recharge at 20
dollars per extra million credits, and Pro's monthly spend is hard-capped at 2,000 dollars.
What the ladder buys, beyond credits and rate: freshness — up to 60 seconds old on Free, no added delay from Dev up; pool OHLCV depth — 24 hours of hourly-and-longer candles keyless, 7 days of 10-minute-and-longer on a free key, 30 days of 1-minute on Dev, unlimited on Pro; the transactions endpoint and transaction streams, from Dev; and token OHLCV, whose plan the pricing page states two ways — the Dev card and the comparison table say Pro, the FAQ says Dev and above.
The free tiers are non-commercial. The API terms grant commercial use only on paid plans, and every plan carries a mandatory "Powered by DexPaprika" attribution.
Data & coverage
Prices are derived from DEX pools, not from centralised exchanges. A pool is re-indexed when a swap moves it, so an idle pool simply has nothing new — a stale-looking price may be an accurate one.
Freshness is stated two ways by the vendor. The pricing page and its FAQ say the free tier is capped at 60 seconds and give the reason — CPU under scraping load. The homepage FAQ says "at most 15 seconds old". The documentation defers to the pricing page, and that is the figure on this card.
Streaming runs over Server-Sent Events, not WebSockets, at streaming.dexpaprika.com for keyless
and free-key use and streaming-pro.dexpaprika.com for paid plans. The documentation names four
feeds: token prices, pool reserves, swap transactions and sealed token candles at 1, 5 or 60
seconds. Keyless, prices stream on 35 showcase tokens only — one per chain, except Arc. A free key
opens prices and reserves on any token, ten streams at a time. Transactions need Dev; candles are
paid-plan only. The vendor measured price streams at between about 1 and 52 updates a minute per
token, which at one credit an update is what decides the bill.
Integrations
MCP, hosted and keyless, at mcp.dexpaprika.com over SSE, streamable HTTP and JSON-RPC. On 4
October 2026 an initialize request answered as "DexPaprika MCP Server" version 2.9.1, and an
unauthenticated tools/list returned 18 tools, from getNetworks and getPoolOHLCV to
getTokenMultiPrices and search. Keyless MCP use draws on the same 10,000 credits per IP. A local
server is published on npm as dexpaprika-mcp, MIT-licensed, at version 2.7.2.
SDKs, first-party and MIT-licensed under the coinpaprika GitHub organisation: TypeScript,
Python, Go and PHP, plus a Rust client whose last commit was on 1 July 2026. The TypeScript and Python clients
had a run of versioned releases on 28 and 29 September 2026, the latest adding token OHLCV; the
Python package on PyPI is dexpaprika-sdk at 0.12.2. Also first-party: dexpaprika-cli, a
LangChain integration and n8n nodes.
The vendor also publishes an OpenAPI specification and an llms.txt index, and its documentation
pages are served as Markdown on request.
Limitations
Keyless is shared, and it was already spent. The 10,000 keyless credits are counted per IP, so from a cloud host, an office NAT or a VPN they belong to everyone on that address. Our first keyless call on 4 October 2026 came back 402. Get the free key before judging the product.
DEX-only. No centralised-exchange order books, trades or funding; for an asset-level price across exchanges the same company sells the CoinPaprika API. A token with thin or manipulated pools gets a price from those pools.
Streaming is metered by the market, not by you. By the vendor's own arithmetic a token averaging one update a minute costs about 43,000 credits a month and one averaging ten about 432,000 — so a free key's 100,000 covers two quiet tokens, and not one busy one. Enterprise is the only unmetered tier.
History is the paid part. Free keys get a week of 10-minute candles; unlimited history needs Pro.
The attribution clause binds every plan. "Powered by DexPaprika", prominently, in your product. If your interface cannot carry it, ask before building on the API.
Alternatives
Birdeye Data and Mobula sell the same shape — DEX-derived token prices and pools by API — with wallet and portfolio endpoints this API does not have. Bitquery is the choice when you need to query raw on-chain events rather than a curated pool model. GeckoTerminal and DEX Screener are screeners first, with APIs behind them. For one aggregated price per coin instead of per pool, CoinPaprika's own API and the CoinGecko API are the other shelf.
Specs
- Interfaces
- API, MCP server
- Export
- JSON, API
- Asset classes
- Spot, DEFI
- Chains
- Ethereum, Solana, Base, Arbitrum, Polygon, BNB, Multi
- Venues
- DEX
- KYC required
- No
- Platforms
- CLI, Library
- AI features
- None
- Capabilities
- Onchain data
- Pricing verified
- Coverage verified
- Capabilities verified
Also from CoinPaprika
Also worth comparing
- Birdeye Data API — Solana-first DEX prices, trades, holders and wallet PnL, metered in compute units.
- CoinAPI Market Data API — One symbol scheme over 400+ venues, metered in REST credits and WebSocket gigabytes.
- CoinGecko API — Prices, market data and onchain DEX data for 18,000+ coins, via REST, websocket or MCP.
- CoinMarketCap API — Prices, rankings, DEX and derivatives data, metered by rows returned rather than by call.
- Mobula API — Pool-weighted token prices, trades and wallet portfolios across 90+ chains, by credit.
- Amberdata Market Data API — Spot, futures and options data — and one exchange's feed you can buy with a card.
On these shelves
Background
How this part of the industry works, rather than which product to pick.
- Why two sites report different volume for the same exchange — Exchange volume is a calculation, not a reading. The six choices that make two honest sites disagree, and how to pick a figure for a dashboard or a backtest.
- How a crypto index is built — What decides which coins get into a crypto index, which exchanges price them, how weights are capped and rebalanced, and why the name needs a licence.
- Credit, request, weight, symbol: why API quotas don't compare — Crypto data APIs meter weight, calls, data points, assets, compute or instruments, so one job costs a different number on each. How to convert it.
- What a tokenized stock is, and where its weekend price comes from — A token named after a stock can be a share, a note, a certificate, a broker's derivative or a perp. What each is, and who prices it when New York is shut.
- What exchange API terms actually let you do — Public crypto endpoints answer without a key. The terms behind them still restrict redistribution, benchmarks and model training, and name an unpriced licence.
- Where the bitcoin price actually comes from — There is no single bitcoin price — only trade prints on individual venues and the methods that combine them. What those methods decide, and which to use when.
FAQ
Does DexPaprika need an API key?
Not to start. Keyless calls to api.dexpaprika.com get 10,000 credits per IP address over a rolling 30 days at 15 requests a minute. The allowance is shared with everyone on the same address — on 4 October 2026 our first keyless request returned HTTP 402 with "Monthly limit reached for unauthenticated use". A free key raises it to 100,000 credits and needs no card.
Can I use DexPaprika's free tier in a commercial product?
No. The API terms, in effect from 14 July 2026, permit commercial use only on plans other than Free, so a business needs Dev at 30 dollars a month or higher. Every plan also requires a visible "Powered by DexPaprika" attribution, in a legible font no smaller than size 10.
How fresh is DexPaprika data on the free tier?
The pricing page says up to 60 seconds old on Free and real time from Dev up. The DexPaprika homepage FAQ says at most 15 seconds on the free tier, so the vendor's own pages disagree; the docs point to the pricing page as the current statement. Streaming pushes a price update when a swap moves it rather than on a fixed tick.
What does a DexPaprika credit cost?
One request is one credit, with no per-endpoint weights. Batch price calls cost one credit per token, so ten tokens in one call is ten credits. Every streamed update costs one credit on Free, Dev and Pro, which makes a busy token's stream the expensive part — the vendor's own example puts ten tokens at one update a second, eight hours a day, at 8.6 million credits a month.
Is DexPaprika the same as the CoinPaprika API?
No. Same company, separate product. DexPaprika covers DEX pools, swaps and on-chain token prices, on its own hosts, keys, documentation and SDKs. The CoinPaprika API is the aggregated, asset-level view — one price and market cap per coin across exchanges.