<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mateusz Sroka on Medium]]></title>
        <description><![CDATA[Stories by Mateusz Sroka on Medium]]></description>
        <link>https://medium.com/@msroka?source=rss-d64356972b83------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ANjEsxMybRt_Noag.jpg</url>
            <title>Stories by Mateusz Sroka on Medium</title>
            <link>https://medium.com/@msroka?source=rss-d64356972b83------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:17:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@msroka/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[October 2026 product update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/october-2026-product-update-coinpaprika-dexpaprika-b628149a54cf?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/b628149a54cf</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 16:24:21 GMT</pubDate>
            <atom:updated>2026-11-10T16:24:21.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8Td-eBrjkqq1NK1y8aR7Q.png" /></figure><p>October added seven DEX integrations to DexPaprika across Tron, Solana, Robinhood and Tempo, and gave Curve’s newer pool types their own DEX ids. Paging through search results past the first page now takes an API key, a free one included. Technical indicators, launched at the start of the month, reached every client we publish. On CoinPaprika, historical tickers and OHLCV gained a circulating_supply field on Business, Ultimate and Enterprise, and several data bugs got fixed.</p><h3>TL;DR</h3><p><strong>DexPaprika:</strong></p><ul><li><strong>Seven DEX integrations:</strong> SunSwap V4 on Tron, ZeroFi and Jupiter Lend AMM on Solana, Aerodrome Slipstream on Robinhood, Uniswap V2, V3 and V4 on Tempo</li><li><strong>Curve StableSwap and TriCrypto pools moved to their own DEX ids</strong> on Ethereum and Base</li><li><strong>Search pages past the first need an API key</strong>. The first page stays keyless</li><li><strong>Technical indicators in every client</strong> the MCP servers, four SDKs, the CLI, LangChain and n8n</li><li><strong>Security releases of every client</strong>: ids are checked before they reach the request path</li><li><strong>OHLCV and the SSE streams accept checksummed EVM addresses</strong></li></ul><p><strong>CoinPaprika:</strong></p><ul><li><strong>circulating_supply on historical tickers and OHLCV</strong> for Business, Ultimate and Enterprise</li><li><strong>/v1/tickers pages past your plan answer </strong><strong>402</strong> instead of returning rows</li><li><strong>Fixed:</strong> percent_change_30d and percent_change_1y stuck at 0, broken logo links, whitepaper and event image links, plan detection for accounts with both a CoinPaprika and a DexPaprika subscription</li><li><strong>NeoxEx</strong> joined the exchange list</li></ul><h3>DexPaprika: more DEXes, and paging that needs a key</h3><h3>Seven DEX integrations</h3><p>Seven DEX integrations went live in October. Each one is a dex_id you can pass to search as dex_name:</p><ul><li><strong>Tron:</strong> SunSwap V4 (sunswap_v4), from 15 October</li><li><strong>Solana:</strong> ZeroFi (zerofi) from 14 October, and Jupiter Lend AMM (jup_lend_amm) from 22 October</li><li><strong>Robinhood:</strong> Aerodrome Slipstream (aerodrome_slipstream), from 29 October</li><li><strong>Tempo:</strong> Uniswap V2, V3 and V4 (uniswap_v2, uniswap_v3, uniswap_v4), from 2 October, next to the Tempo Stablecoin DEX that was already indexed</li></ul><pre>curl -s &quot;https://api.dexpaprika.com/networks/solana/pools/search?dex_name=zerofi&amp;limit=5&quot;</pre><p>Every DEX on a chain is listed at /networks/{network}/dexes, with its 24h volume and pool count.</p><h3>Curve pools moved to their own DEX ids</h3><p>Until 12 October, pools from Curve’s StableSwap factory on Ethereum and Base, and from its TriCrypto factory on Base, were listed under the curve DEX. They now report curve_stableswap and curve_tricrypto. The move covers existing pools as well as new ones (a StableSwap pool created in 2024 now carries the new id), and pool addresses stay the same.</p><p>If you filter Curve pools with dex_name=curve on Ethereum or Base, add the new ids, or those pools drop out of your results:</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/pools/search?dex_name=curve_stableswap&amp;limit=5&quot;</pre><h3>Search pages past the first need an API key</h3><p>Since 26 October, a keyless request that carries cursor on /networks/{network}/pools/search, /pools/search, /networks/{network}/tokens/search or /tokens/search gets 403. The first page still works without a key, up to 100 rows with limit=100, and any API key pages without limit. A free key from <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a> is enough.</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/solana/pools/search?limit=100&amp;cursor=NEXT_CURSOR&quot;</pre><pre>{&quot;error&quot;:&quot;plan_required&quot;,&quot;tier&quot;:&quot;keyless&quot;,&quot;message&quot;:&quot;Search results beyond the first page require an API key (free key: all pages). Create one in under a minute at https://console.dexpaprika.com&quot;,&quot;required_tier&quot;:&quot;free&quot;,&quot;param&quot;:&quot;cursor&quot;,&quot;links&quot;:{...}}</pre><p>The refusal comes before any data is read, so it costs no credits. From 14 October these requests carried an x-api-warning header first; the 403 replaced it on the 26th. To page, send your key in the Authorization header, the key on its own. The rules are in <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits#pagination-rules">pagination rules</a>.</p><h3>Technical indicators in every client</h3><p>Indicators (RSI, EMA, MACD, Bollinger Bands and VWAP, computed by the API from OHLCV candles) launched on 7 October. On 13 October the ten endpoints became two, one per pool and one per token, with the indicator in the indicator query parameter, and all five pool indicators opened on every plan:</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/indicators?indicator=rsi&amp;interval=1h&amp;start=-24h&quot;</pre><pre>{&quot;network&quot;:&quot;ethereum&quot;,&quot;pool_address&quot;:&quot;0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640&quot;,&quot;indicator&quot;:&quot;rsi&quot;,&quot;interval&quot;:&quot;1h&quot;,&quot;parameters&quot;:{&quot;period&quot;:14},&quot;data&quot;:[{&quot;timestamp&quot;:&quot;2026-11-09T15:00:00Z&quot;,&quot;value&quot;:51.8841364338867},{&quot;timestamp&quot;:&quot;2026-11-09T16:00:00Z&quot;,&quot;value&quot;:47.26383225072691}, ...],&quot;has_next_page&quot;:true}</pre><p>Pool indicators follow the same interval and history limits as pool OHLCV for your plan. Token indicators need a Dev, Pro or Enterprise plan on api-pro.dexpaprika.com.</p><p>On 14 October they reached the clients:</p><ul><li><strong>MCP server</strong> <a href="https://github.com/coinpaprika/dexpaprika-mcp/releases/tag/v2.8.0">2.8.0</a>: getPoolIndicator and getTokenIndicator, 20 tools in total. The hosted server at mcp.dexpaprika.com has the same two tools</li><li><strong>TypeScript SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-ts/releases/tag/v1.13.0">1.13.0</a>: pools.getIndicator() and tokens.getIndicator()</li><li><strong>Python SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-python/releases/tag/v0.13.0">0.13.0</a>: pools.get_indicator() and tokens.get_indicator()</li><li><strong>Go SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-go/releases/tag/v1.12.0">v1.12.0</a>: Pools.GetIndicator and Tokens.GetIndicator</li><li><strong>PHP SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-php/releases/tag/v1.12.0">1.12.0</a>: getPoolIndicator() and getTokenIndicator()</li><li><strong>CLI</strong> <a href="https://github.com/coinpaprika/dexpaprika-cli/releases/tag/v0.10.0">0.10.0</a>: pool-indicator and token-indicator</li><li><strong>LangChain</strong> <a href="https://github.com/coinpaprika/langchain-dexpaprika/releases/tag/v0.5.0">0.5.0</a> and <strong>n8n</strong> <a href="https://github.com/coinpaprika/n8n-nodes-dexpaprika/releases/tag/v0.5.0">0.5.0</a>: indicator tools and a Get Indicator operation</li></ul><p>The SDKs and the MCP server send only the parameters you set, because the API refuses a parameter that belongs to another indicator (fast_period with indicator=rsi is a 400). The walkthrough is <a href="https://docs.dexpaprika.com/tutorials/technical-indicators">technical indicators</a>.</p><h3>Client releases worth taking</h3><p>Two more rounds of releases followed.</p><p><strong>16 October.</strong> The TypeScript, Python, Go and PHP SDKs (<a href="https://github.com/coinpaprika/dexpaprika-sdk-ts/releases/tag/v1.14.0">1.14.0</a>, <a href="https://github.com/coinpaprika/dexpaprika-sdk-python/releases/tag/v0.14.0">0.14.0</a>, <a href="https://github.com/coinpaprika/dexpaprika-sdk-go/releases/tag/v1.13.0">v1.13.0</a>, <a href="https://github.com/coinpaprika/dexpaprika-sdk-php/releases/tag/v1.13.0">1.13.0</a>):</p><ul><li>recognise the keyless paging 403 and expose its required_tier and param</li><li>sort and filter pools on price_change_percentage_48h. Until now each SDK silently replaced that sort with its default</li><li>report a key refused on api-pro.dexpaprika.com in plain words, where they used to show a bare 403 or &quot;Unknown error&quot;</li><li>in TypeScript and PHP, wait as long as a 429 asks through Retry-After before retrying</li></ul><p>CLI <a href="https://github.com/coinpaprika/dexpaprika-cli/releases/tag/v0.11.0">0.11.0</a> picked up the 48h window, the paging message and the clearer message for a blocked key.</p><p><strong>21 October.</strong> Every client now checks network ids and addresses before they go into the request path. Before, a value such as ../../../stats was placed in the URL as given, so an application that passed user input to a client could be made to send its API key to a different endpoint. Real ids, including Sui and Aptos type tags with :: and TON addresses, go through unchanged. This shipped in TypeScript 1.14.1, Python 0.14.1, Go v1.13.1, PHP 1.13.1, MCP server 2.9.1 and 2.9.2, CLI 0.12.0, LangChain 0.5.1 and n8n 0.5.1. TypeScript 1.14.2, Python 0.14.2 and PHP 1.13.2 also harden their response caches.</p><p>If your application passes anything a user typed into one of our clients, upgrade. Current versions: TypeScript 1.14.2, Python 0.14.2, Go v1.13.1, PHP 1.13.2, MCP server 2.9.3, CLI 0.12.1, LangChain 0.5.1, n8n 0.5.2.</p><h3>Fixes</h3><ul><li><strong>OHLCV for checksummed addresses (30 October).</strong> A mixed-case EVM pool address, as most wallets and explorers print it, passed the pool lookup and then returned 200 with no candles. It now returns the same candles as the lowercase address</li><li><strong>SSE streams and checksummed addresses (30 October).</strong> Price, reserve and transaction streams now match a checksummed address too; before, such a subscription received no events. A key repeated in one POST no longer delivers each event once per copy</li></ul><h3>Docs</h3><p>On 13 October seven tutorials arrived, one per endpoint, each with a working curl and a Python script for the free tier and for paid keys: <a href="https://docs.dexpaprika.com/tutorials/list-networks">list networks</a>, <a href="https://docs.dexpaprika.com/tutorials/list-dexes">list DEXes</a>, <a href="https://docs.dexpaprika.com/tutorials/search">search</a>, <a href="https://docs.dexpaprika.com/tutorials/token-screener">screen tokens</a>, <a href="https://docs.dexpaprika.com/tutorials/pool-details">pool details</a>, <a href="https://docs.dexpaprika.com/tutorials/pool-transactions">pool transactions</a> and <a href="https://docs.dexpaprika.com/tutorials/check-credit-usage">check your credit usage</a>. Every API reference page now links its tutorial. A longer one, <a href="https://docs.dexpaprika.com/tutorials/agent-trading-signals">feed an AI trading agent with technical indicators</a>, builds a paper-trading agent that runs without a key.</p><h3>CoinPaprika</h3><h3>Historical circulating supply</h3><p>Since 15 October, circulating_supply comes back on /v1/tickers/{coin_id}/historical and on /v1/coins/{coin_id}/ohlcv/historical, /ohlcv/latest and /ohlcv/today, for Business, Ultimate and Enterprise keys:</p><pre>curl -s -H &quot;Authorization: $COINPAPRIKA_API_KEY&quot; \<br>  &quot;https://api-pro.coinpaprika.com/v1/tickers/btc-bitcoin/historical?start=2026-11-01&amp;interval=1d&amp;limit=2&quot;</pre><pre>[{&quot;timestamp&quot;:&quot;2026-11-01T00:00:00Z&quot;,&quot;price&quot;:77827.21,&quot;volume_24h&quot;:10569469791,&quot;market_cap&quot;:1564842388641,&quot;circulating_supply&quot;:20106624},<br> {&quot;timestamp&quot;:&quot;2026-11-02T00:00:00Z&quot;,&quot;price&quot;:77681.92,&quot;volume_24h&quot;:13835195615,&quot;market_cap&quot;:1561952747324,&quot;circulating_supply&quot;:20107029}]</pre><p>The value is market cap divided by price at that point, so treat it as an approximation. On other plans the field is left out of the response.</p><h3>/v1/tickers pages past your plan answer 402</h3><p>Each plan covers a set number of top assets. Until 2 October, a /v1/tickers?page=N request that started past that set still returned rows on the free plan. It now returns 402 with a message naming the limit. Plans and their asset counts are on the <a href="https://coinpaprika.com/api/pricing">pricing page</a>.</p><h3>Fixes</h3><ul><li><strong>percent_change_30d and </strong><strong>percent_change_1y on </strong><strong>/v1/tickers (29 October)</strong> could come back as 0. They now carry the real change. A 0 you still see is genuine: a stablecoin that hasn&#39;t moved, or a coin younger than the window</li><li><strong>logo on </strong><strong>/v1/coins/{coin_id} (29 October)</strong> was built from the coin&#39;s page slug while the files are stored under its id, so for some coins it pointed at a missing file. It now uses the id</li><li><strong>Whitepaper and event image links (22 and 28 October)</strong> now point at static.coinpaprika.com. If you stored the old links, fetch them again</li><li><strong>Accounts with both subscriptions (22 October).</strong> An account holding a CoinPaprika and a DexPaprika subscription could be served the free CoinPaprika plan when the DexPaprika one was listed first. The plan now comes from the CoinPaprika subscription</li></ul><h3>Clients</h3><p>On 21 October the CoinPaprika clients got the same id checks as the DexPaprika ones: the Go client <a href="https://github.com/coinpaprika/coinpaprika-api-go-client/releases/tag/v2.5.1">2.5.1</a> (which also keeps your key on the Pro host), the Swift client <a href="https://github.com/coinpaprika/coinpaprika-api-swift-client/releases/tag/2.4.1">2.4.1</a>, the Kotlin client <a href="https://github.com/coinpaprika/coinpaprika-api-kotlin-client/releases/tag/0.5.4">0.5.4</a> (opt-in), the MCP server <a href="https://github.com/coinpaprika/coinpaprika-mcp/releases/tag/v1.4.1">1.4.1</a> and the CLI <a href="https://github.com/coinpaprika/coinpaprika-cli/releases/tag/v0.2.0">0.2.0</a>. The Swift release also adds paging for tickers and nine endpoints it was missing, maps 402 to its own error, and sends your key in Authorization on its own, the way the API expects it.</p><h3>Exchanges</h3><p>NeoxEx joined the exchange list on 15 October as neoxex.</p><h3>Availability and rollout</h3><p><strong>DexPaprika:</strong></p><ul><li>Uniswap V2, V3 and V4 on Tempo: 2 October</li><li>Indicators on two endpoints, every pool indicator on every plan, seven tutorials: 13 October</li><li>ZeroFi: 14 October</li><li>Indicators in every client: 14 October</li><li>SunSwap V4: 15 October</li><li>SDK releases with 48h sorting and the paging error: 16 October</li><li>Security releases of every client: 21 October</li><li>Jupiter Lend AMM: 22 October</li><li>Keyless search paging refused: 26 October</li><li>Aerodrome Slipstream on Robinhood: 29 October</li><li>OHLCV and stream fixes for checksummed addresses: 30 October</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>/v1/tickers pages past the plan: 2 October</li><li>circulating_supply on historical endpoints, NeoxEx: 15 October</li><li>Plan detection with two subscriptions, whitepaper links: 22 October</li><li>Event images: 28 October</li><li>percent_change and logo fixes: 29 October</li></ul><p><strong>Breaking changes:</strong> on DexPaprika, keyless search paging and the Curve DEX ids. On CoinPaprika, 402 for tickers pages past your plan. No response shapes changed; circulating_supply is a new field.</p><h3>Measurable impact</h3><ul><li>Seven DEX integrations on DexPaprika in October, on four chains</li><li>35 tagged client releases in October across 13 repositories: SDKs, CLIs, MCP servers, n8n and LangChain for DexPaprika, and the Go, Swift and Kotlin clients, CLI and MCP server for CoinPaprika</li><li>Seven new endpoint tutorials, and every API reference page links one</li></ul><h3>Get started</h3><p><strong>DexPaprika:</strong></p><ul><li>Start without a key, or get a free one at <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a> to page through search. Send it in the Authorization header, on its own</li><li>Filtering Curve on Ethereum or Base? Add curve_stableswap and curve_tricrypto</li><li>Token indicators, token OHLCV and new pools in their first hour come with Dev, Pro and Enterprise on api-pro.dexpaprika.com. Plans: <a href="https://dexpaprika.com/api/pricing">dexpaprika.com/api/pricing</a></li><li>Docs: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li>circulating_supply on historical data needs Business, Ultimate or Enterprise: <a href="https://coinpaprika.com/api/pricing">coinpaprika.com/api/pricing</a></li><li>Docs: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li></ul><p><strong>Example query:</strong> RSI for the USDC/WETH pool on Uniswap V3, hourly over the last day, no key needed</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/indicators?indicator=rsi&amp;interval=1h&amp;start=-24h&quot;</pre><h3>Questions?</h3><p>If you are building on our APIs and have questions about these updates:</p><ul><li>DexPaprika docs: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li><li>DexPaprika changelog: <a href="https://docs.dexpaprika.com/changelog/changelog">https://docs.dexpaprika.com/changelog/changelog</a></li><li>DexPaprika pricing: <a href="https://dexpaprika.com/api/pricing">https://dexpaprika.com/api/pricing</a></li><li>CoinPaprika docs: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li><li>CoinPaprika changelog: <a href="https://docs.coinpaprika.com/changelog">https://docs.coinpaprika.com/changelog</a></li><li>DexPaprika MCP server: <a href="https://github.com/coinpaprika/dexpaprika-mcp">https://github.com/coinpaprika/dexpaprika-mcp</a></li><li>CoinPaprika MCP server: <a href="https://github.com/coinpaprika/coinpaprika-mcp">https://github.com/coinpaprika/coinpaprika-mcp</a></li></ul><p><strong>About the author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b628149a54cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/october-2026-product-update-coinpaprika-dexpaprika-b628149a54cf">October 2026 product update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[September 2026 product update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/september-2026-product-update-coinpaprika-dexpaprika-ad3da213aab0?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad3da213aab0</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 12:27:31 GMT</pubDate>
            <atom:updated>2026-10-16T07:20:24.271Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7YjQtEOlZDIg28XywGkKQ.png" /></figure><p>The big one in September is token OHLCV. DexPaprika now gives any token we index one USD candle series, volume-weighted across every pool it trades in, over REST and as a live stream. Charting a token used to mean picking one of its pools and converting the pair price; now it is one call. Around it, pricing v2.0 added a Dev plan between Free and Pro, OHLCV history and pool transactions were each assigned to a plan, and Arc became our 36th network. On CoinPaprika, the Arc DEX markets went live. Every change reached the docs and every client we publish within a day.</p><h3>TL;DR</h3><p><strong>DexPaprika:</strong></p><ul><li><strong>Token OHLCV, new on REST:</strong> USD candles for a token, volume-weighted across every pool it trades in. Dev, Pro and Enterprise</li><li><strong>Token OHLCV streaming:</strong> sealed candles at 1s, 5s or 60s over SSE, with a 15-minute backfill. Dev, Pro and Enterprise</li><li><strong>Pricing v2.0 and a Dev plan.</strong> Dev sits between Free and Pro, at $30 a month at launch, on the same paid hosts as Pro. Free allowances now count over a rolling 30 days instead of a calendar month. Current figures are on the <a href="https://dexpaprika.com/api/pricing">pricing page</a></li><li><strong>OHLCV depth and candle size depend on your plan,</strong> and start=-24h works on every plan, keyless included</li><li><strong>Pool transactions are paid-only,</strong> on REST and on the transactions stream</li><li><strong>Relative times everywhere:</strong> -1h, -24h or -7d on OHLCV, transactions and the four search endpoints</li><li><strong>Errors carry a machine-readable </strong><strong>error code</strong> next to message</li><li><strong>Arc is network number 36,</strong> with Uniswap V2, V3 and V4</li><li><strong>Every SDK, the CLI, both MCP servers, n8n and LangChain</strong> shipped the above, 39 releases in total</li></ul><p><strong>CoinPaprika:</strong></p><ul><li><strong>Uniswap V2, V3 and V4 on Arc</strong> joined the exchange list</li><li><strong>Delisted coin pages load again</strong> instead of answering 410</li><li>Large market cap and volume figures on the website drop the cents</li><li>No breaking API changes</li></ul><h3>DexPaprika: candles for any token, and the plans around them</h3><h3>Token OHLCV: candles for a token, not a pool</h3><p>Until now, charting a token meant picking one of its pools and converting the pair price to dollars. Since 29 September, GET /networks/{network}/tokens/{token_address}/ohlcv does that for you: each candle is a volume-weighted USD price across every pool the token trades in on that network, and volume is the USD traded across all of them.</p><pre>curl -s -H &quot;Authorization: $DEXPAPRIKA_API_KEY&quot; \<br>  &quot;https://api-pro.dexpaprika.com/networks/ethereum/tokens/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2/ohlcv?start=-24h&amp;interval=1h&amp;limit=24&quot;</pre><pre>{&quot;time_open&quot;:&quot;2026-10-12T09:00:00Z&quot;,&quot;time_close&quot;:&quot;2026-10-12T10:00:00Z&quot;,&quot;open&quot;:2553.40,&quot;high&quot;:2556.32,&quot;low&quot;:2551.38,&quot;close&quot;:2556.32,&quot;volume&quot;:8642910}</pre><p>That is WETH on Ethereum, one candle of 24, priced across every WETH pool we index there. The parameters match pool OHLCV: start (relative offsets work), end, interval from 1m to 24h (there is no inversed, since a USD price has no pair to flip, and history starts on 1 November 2025), and up to 1000 candles per request.</p><p>It is available on Dev, Pro and Enterprise, on api-pro.dexpaprika.com; Dev covers the last 30 days. A keyless or free-key call gets 403 naming the plan it needs. Walkthrough: <a href="https://docs.dexpaprika.com/tutorials/token-ohlcv">token price history across every pool</a>.</p><h3>Token OHLCV streaming</h3><p>The same candles also arrive live. Since 10 September, GET /sse/ohlcv on streaming-pro.dexpaprika.com streams sealed token candles for any token we index, on every chain, at 1s, 5s or 60s:</p><pre>curl -N -H &quot;Authorization: $DEXPAPRIKA_API_KEY&quot; \<br>  &quot;https://streaming-pro.dexpaprika.com/sse/ohlcv?method=token_ohlcv&amp;chain=ethereum&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&amp;interval=1s&amp;limit=3&quot;</pre><pre>id: 1791881608<br>event: token_ohlcv<br>data: {&quot;chain&quot;:&quot;ethereum&quot;,&quot;token_id&quot;:&quot;0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&quot;,&quot;interval&quot;:&quot;1s&quot;,&quot;timestamp&quot;:&quot;2026-10-13T08:53:28Z&quot;,&quot;open&quot;:2523.43,&quot;high&quot;:2523.43,&quot;low&quot;:2523.43,&quot;close&quot;:2523.43,&quot;avg&quot;:2523.43,&quot;volume_usd&quot;:14843.42,&quot;txns&quot;:23}</pre><p>Two details make it practical for production. A dropped connection resumes from Last-Event-ID, and since backfills up to the last 15 minutes, so a reconnect doesn&#39;t leave a hole in your chart. Load history over REST, then continue live on the stream. Each candle, backfilled ones included, is one credit; pings are free. Guide: <a href="https://docs.dexpaprika.com/streaming/ohlcv-streaming">OHLCV streaming</a>.</p><h3>Pricing v2.0 and the Dev plan</h3><p>Pricing v2.0 went live on 15 September. The main change is a new <strong>Dev plan</strong>, built for side projects and small production apps: real-time data, every paid endpoint in this update, and a higher per-minute rate than Free. It launched at $30 a month. Dev uses the same hosts and key format as Pro, so a Dev key goes to api-pro.dexpaprika.com for REST and streaming-pro.dexpaprika.com for SSE, sent as the whole Authorization header value on its own.</p><p>What else changed on 15 September:</p><ul><li><strong>Free allowances count over a rolling 30-day window.</strong> Keyless and free-key usage no longer resets on the 1st of the month; it refills continuously, so a 402 body on those tiers carries no reset date. Dev and Pro still reset with the billing period</li><li><strong>Per-minute rates and credit quotas moved on every tier,</strong> and the keyless credit allowance was lowered again on 23 September. If you were sized against August’s numbers, check the <a href="https://dexpaprika.com/api/pricing">pricing page</a> and the <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits">rate limits guide</a>. We keep the figures there and nowhere else, because they move</li><li><strong>Bulk credit packs are no longer sold.</strong> Packs you already bought keep draining</li><li><strong>In the console,</strong> a free account can now pick Dev or Pro directly on the billing page at <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a>, and the plan comparison shows the new tier ladder</li></ul><p>If a keyless integration runs into the new allowance, the fix is a free key from the console: no card, more credits and a higher per-minute rate.</p><h3>OHLCV limits by plan</h3><p>Since 25 September, how far back you can query pool OHLCV and how fine the candles can be depends on the plan behind the request. Keyless calls get the shortest history and hourly candles and up. A free key opens sub-hour candles and a longer history. Dev opens every interval down to 1m over a month, and Pro and Enterprise have no history limit. The exact windows are in <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits#ohlcv-limits-by-plan">OHLCV limits by plan</a>.</p><p>To make that painless, start and end now accept offsets from now (-24h, -7d, -90m), and start=-24h is valid on every plan. If you hard-coded a date, switch to an offset:</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/ohlcv?start=-24h&amp;interval=1h&amp;limit=24&quot;</pre><p>A request outside your plan’s limits returns 403 with a message naming the plan that lifts it. Treat that as a parameter error: retrying it with backoff won&#39;t change the answer. limit now defaults to 10 candles (it was 1). Candles are counted forward from start, so a request without limit now returns up to 10 candles instead of 1; to keep the single-candle response, pass limit=1. The per-request maximum is 1000.</p><h3>Pool transactions are paid-only</h3><p>Since 30 September, GET /networks/{network}/pools/{pool_address}/transactions answers Dev, Pro and Enterprise keys on api-pro.dexpaprika.com, and the transactions stream (/sse/transactions) answers the same plans on streaming-pro.dexpaprika.com. Keyless and free-key calls get 403 with &quot;error&quot;:&quot;plan_required&quot;, &quot;required_tier&quot;:&quot;dev&quot; and links to the console, docs and pricing (trimmed below):</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/transactions?limit=1&quot;</pre><pre>{&quot;error&quot;:&quot;plan_required&quot;,&quot;tier&quot;:&quot;keyless&quot;,&quot;message&quot;:&quot;this endpoint requires a Dev or Pro plan&quot;,&quot;required_tier&quot;:&quot;dev&quot;}</pre><p>On the free tier, pool details still carry each pool’s buys, sells, swap counts and USD volume over windows from 5 minutes to 24 hours, and pool search filters on them. Price streams stay keyless on the <a href="https://docs.dexpaprika.com/streaming/showcase-streams">showcase assets</a> and open to any key on any token, and reserve streams stay open to free keys.</p><h3>Relative times on transactions and search</h3><p>Since 28 September, the time filters across the API accept the same shapes as OHLCV:</p><ul><li>from and to on pool transactions: from=-1h returns the last hour of swaps</li><li>created_after and created_before on /pools/search, /networks/{network}/pools/search, /tokens/search and /networks/{network}/tokens/search</li></ul><p>Unix seconds, RFC3339 and YYYY-MM-DD keep working, and the query block of a search response shows the resolved timestamp. The busiest Solana pools created in the last day:</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/solana/pools/search?created_after=-24h&amp;order_by=volume_usd_24h&amp;sort=desc&amp;limit=5&quot;</pre><h3>Errors you can branch on</h3><p>REST error bodies now carry an error code next to message, plus a field naming what failed where there is one:</p><pre>{&quot;error&quot;:&quot;invalid_param&quot;,&quot;message&quot;:&quot;invalid query param: limit (must be a number)&quot;,&quot;param&quot;:&quot;limit&quot;}</pre><p>The codes are invalid_param (with param), not_found (with resource), unsupported_network and plan_required (with required_tier). message is still there, so code that reads it keeps working, but branch on error from now on: message text can change. Examples in <a href="https://docs.dexpaprika.com/knowledge-base/error-handling">error handling</a>.</p><p>Also new in responses: a last_updated timestamp on pool details, token details and multi-price rows, so you can tell how fresh a price is without comparing it against your own clock.</p><h3>Arc, our 36th network</h3><p>Arc joined on 16 September with Uniswap V2, V3 and V4. /networks lists 36 chains again, after Botanix left in August.</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/arc/dexes&quot;</pre><p>Arc is also on the site at <a href="https://dexpaprika.com/arc">dexpaprika.com/arc</a>, with an API landing page at <a href="https://dexpaprika.com/api/arc">dexpaprika.com/api/arc</a>.</p><h3>Streaming</h3><ul><li><strong>Token OHLCV stream,</strong> above</li><li><strong>Streams close when a key is revoked or a plan lapses,</strong> instead of running on</li><li><strong>Transactions stream:</strong> Dev, Pro and Enterprise since 30 September, as above</li><li>Price streams and reserve streams: unchanged</li></ul><h3>dexpaprika.com</h3><ul><li><strong>Live charts.</strong> Charts receive new candles over SSE as they seal, open on 1-minute candles over the last hour, and keep loading history as you zoom out. Token charts now read TOKEN/USD</li><li><strong>Live transactions on token pages.</strong> New swaps appear above the loaded rows as they happen</li><li><strong>A Tokens tab on every chain hub,</strong> next to pools and DEXes, for example on <a href="https://dexpaprika.com/ethereum">Ethereum</a></li><li><strong>API landing pages per chain and per DEX.</strong> Every chain has one under /api/{chain} and the most-searched DEXes have their own, such as <a href="https://dexpaprika.com/api/ethereum/uniswap">Uniswap on Ethereum</a> and <a href="https://dexpaprika.com/api/solana/raydium">Raydium on Solana</a>, each with the first call to make and the docs to read next</li><li><strong>Pricing page on v2.0:</strong> the Dev tier, OHLCV history and candle size per tier, and which tiers include transactions and token OHLCV. The free-key buttons across the site now open the console’s key screen directly</li><li><strong>Token pages</strong> explain tokens that have never traded, and risk flags moved into the token drawer</li></ul><h3>Tools: 39 releases</h3><p>Each API change above reached our clients within a day. The highlights:</p><ul><li><strong>Token OHLCV</strong> in the TypeScript SDK <a href="https://github.com/coinpaprika/dexpaprika-sdk-ts/releases/tag/v1.12.0">1.12.0</a> (client.tokens.getOHLCV()), Python SDK <a href="https://github.com/coinpaprika/dexpaprika-sdk-python/releases/tag/v0.12.0">0.12.0</a> (client.tokens.get_ohlcv()), PHP SDK <a href="https://github.com/coinpaprika/dexpaprika-sdk-php/releases/tag/v1.11.0">1.11.0</a>, Go SDK <a href="https://github.com/coinpaprika/dexpaprika-sdk-go/releases/tag/v1.11.0">1.11.0</a>, CLI <a href="https://github.com/coinpaprika/dexpaprika-cli/releases/tag/v0.9.0">0.9.0</a> (token-ohlcv), the npm MCP server <a href="https://github.com/coinpaprika/dexpaprika-mcp/releases/tag/v2.7.0">2.7.0</a> (getTokenOHLCV), n8n node <a href="https://github.com/coinpaprika/n8n-nodes-dexpaprika/releases/tag/v0.4.0">0.4.0</a> and <a href="https://github.com/coinpaprika/langchain-dexpaprika/releases/tag/v0.4.0">langchain-dexpaprika</a> 0.4.0</li><li><strong>Relative times</strong> in every SDK, the CLI (<a href="https://github.com/coinpaprika/dexpaprika-cli/releases/tag/v0.8.0">0.8.0</a>) and the MCP server (<a href="https://github.com/coinpaprika/dexpaprika-mcp/releases/tag/v2.6.0">2.6.0</a>)</li><li><strong>OHLCV plan limits:</strong> client-side limit caps raised to the API&#39;s 1000, examples moved to start=-24h, and a 403 now reaches your code with the API&#39;s message instead of a bare status</li><li><strong>Fixes worth upgrading for:</strong> transaction rows in the Go and Python SDKs keep created_at, the token symbols, volumes and USD prices, which earlier releases dropped, and the TypeScript SDK now types those fields; the PHP SDK now sends from and to on transactions (earlier releases dropped both) and its getNetworkDexes() now works; the Python SDK no longer caches prices and OHLCV for 24 hours</li><li><strong>Hosted MCP at </strong><strong>mcp.dexpaprika.com:</strong> getTokenOHLCV and getPoolTransactions run on your own key, set as the Authorization header on your connection (<a href="https://docs.dexpaprika.com/ai-integration/hosted-mcp-server#your-own-api-key-for-token-ohlcv-and-pool-transactions">setup</a>). Every other tool still works without one</li></ul><p>The <a href="https://docs.dexpaprika.com/changelog/changelog">docs changelog</a> lists every release with what changed in it.</p><h3>CoinPaprika</h3><p>A quieter month on the CoinPaprika side, with no breaking API changes.</p><ul><li><strong>Arc DEX markets.</strong> Uniswap V2, V3 and V4 on Arc joined the exchange list on 17 September, as uniswap-v2-arc, uniswap-v3-arc and uniswap-v4-arc:</li></ul><pre>curl -s &quot;https://api.coinpaprika.com/v1/exchanges/uniswap-v4-arc&quot;</pre><ul><li><strong>Delisted coin pages load again.</strong> In August a page for a coin with is_active: false started answering 410. Since 23 September it loads again with a 200, so existing links keep working. The API is unchanged; key on is_active if you track listings</li><li><strong>Cleaner large numbers.</strong> Market cap and volume above 100,000 drop the cents on the <a href="https://coinpaprika.com/all-coins/">all coins</a> list and on market tables</li></ul><h3>Availability and rollout</h3><p><strong>DexPaprika:</strong></p><ul><li>Token OHLCV stream: 10 September</li><li>Pricing v2.0, Dev plan, rolling 30-day free allowances: 15 September</li><li>Arc: 16 September</li><li>Keyless allowance lowered: 23 September</li><li>OHLCV limits by plan, relative start and end: 25 September</li><li>Relative times on transactions and search: 28 September</li><li>error codes in REST error bodies: 30 September</li><li>Token OHLCV on REST and in every client: 29 September</li><li>Pool transactions and the transactions stream paid-only: 30 September</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Arc DEX markets: 17 September</li><li>Delisted coin pages back to 200: 23 September</li></ul><p><strong>Breaking changes, DexPaprika only:</strong> the new allowances and rates on every tier, OHLCV limits by plan (a request outside them returns 403), pool transactions moving to paid plans, and the OHLCV limit default, now 10 candles instead of 1. Nothing changed in response shapes; the new error field sits next to message. No breaking changes on the CoinPaprika API.</p><h3>Since then, in October</h3><p>Three things shipped in the first week of October that belong with this list: pool search sorts and filters on the 48h price change (2 October), the transactions stream replays the swaps you missed after a reconnect (5 October, paid plans), and technical indicators (RSI, EMA, MACD, Bollinger Bands, VWAP) for pools and tokens (7 October): pool indicators work on every plan within its OHLCV limits, token indicators need Dev, Pro or Enterprise. Details in the <a href="https://docs.dexpaprika.com/changelog/changelog">docs changelog</a>; full coverage in next month’s update.</p><h3>Measurable impact</h3><ul><li>36 networks on DexPaprika, up from 35, with Arc’s three Uniswap versions</li><li>Two new data products: token OHLCV over REST and over SSE</li><li>39 tagged client releases in one month across the SDKs, the CLI, the MCP server, n8n and LangChain</li><li>Three new DEX exchanges on CoinPaprika, all on Arc</li></ul><h3>Get started</h3><p><strong>DexPaprika:</strong></p><ul><li>Start without a key, or register a free one at <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a> and send it in the Authorization header, on its own</li><li>For token OHLCV, the token stream or pool transactions, pick Dev or Pro in the console and call api-pro.dexpaprika.com</li><li>Use start=-24h for OHLCV: it works on every plan</li><li>Branch on error, not on message, and treat 403 from OHLCV as final</li><li>Docs: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Docs: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li></ul><p><strong>Example query:</strong> a token’s hourly USD candles across all its pools, on a Dev or Pro key</p><pre>curl -s -H &quot;Authorization: $DEXPAPRIKA_API_KEY&quot; \<br>  &quot;https://api-pro.dexpaprika.com/networks/ethereum/tokens/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2/ohlcv?start=-24h&amp;interval=1h&amp;limit=24&quot;</pre><h3>Questions?</h3><p>If you are building on our APIs and have questions about these updates:</p><ul><li>DexPaprika docs: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li><li>DexPaprika pricing: <a href="https://dexpaprika.com/api/pricing">https://dexpaprika.com/api/pricing</a></li><li>CoinPaprika docs: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li><li>DexPaprika MCP server: <a href="https://github.com/coinpaprika/dexpaprika-mcp">https://github.com/coinpaprika/dexpaprika-mcp</a></li><li>CoinPaprika MCP server: <a href="https://github.com/coinpaprika/coinpaprika-mcp">https://github.com/coinpaprika/coinpaprika-mcp</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad3da213aab0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/september-2026-product-update-coinpaprika-dexpaprika-ad3da213aab0">September 2026 product update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[August 2026 product update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/august-2026-product-update-coinpaprika-dexpaprika-4a6e77499282?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a6e77499282</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 06:53:10 GMT</pubDate>
            <atom:updated>2026-09-07T06:53:10.299Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Date:</strong> 4 September 2026 <strong>Author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTUxpx4rtfLMv5K7ApJMUg.png" /></figure><p>Paid plans went live on DexPaprika on 7 August. Most of what shipped this month follows from that: the API now enforces plans and hosts, tells you exactly why a call was refused and where to go next, and every SDK, the CLI and the MCP servers can send a key. Around it, two deprecated endpoints were retired, two DEX families joined, pool search learned two shorter price windows, and CoinPaprika’s API started reporting your monthly budget in headers.</p><h3>TL;DR</h3><p><strong>DexPaprika:</strong></p><ul><li><strong>Paid plans are live since 7 August.</strong> Keys are checked against their host, monthly allowances are enforced, and every refusal comes back as a structured body with links. Current allowances and rates are on the <a href="https://dexpaprika.com/api/pricing">pricing page</a></li><li><strong>Two deprecated endpoints retired:</strong> /networks/{network}/dexes/{dex}/pools (5 August) and the legacy /stream path on the streaming host (26 August). Both answer 410 with the replacement in the body</li><li><strong>Botanix retired.</strong> The network shut down; /networks now lists 35 chains</li><li><strong>New DEXes:</strong> Curve on Plasma (three pool types) and Nile V1 on Linea</li><li><strong>1h and 5m price change</strong> join the pool search filters and sort fields</li><li><strong>Token endpoints serve real-time data on paid plans;</strong> response shapes unchanged</li><li><strong>Streaming:</strong> reserve streams open to free keys, refusals use the same 402 body as REST</li><li><strong>Every SDK, the CLI, the MCP server and the n8n node take an optional API key,</strong> and the SDKs moved off the retired DEX pools endpoint</li><li><strong>On dexpaprika.com:</strong> live single-asset streaming showcase pages, risk flags on token pages, a .md mirror of every page, and a self-serve pricing page</li></ul><p><strong>CoinPaprika:</strong></p><ul><li><strong>The API reports your monthly budget</strong> in RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, and 402 and 429 carry Retry-After</li><li><strong>Revolut X</strong> is a new exchange, with 408 markets</li><li><a href="https://coinpaprika.com/methodology/"><strong>Methodology 2.0</strong></a> is published, with the independent data-quality audit, the outlier procedure and the asset identifier mappings documented</li><li><strong>Delisted coins answer </strong><strong>410</strong> on the website. No breaking API changes</li></ul><h3>DexPaprika: the first month of paid plans</h3><h3>Plans and hosts are enforced</h3><p>Since launch day the API checks a key against the host it is valid on. Free keys belong on api.dexpaprika.com and streaming.dexpaprika.com; Pro and Enterprise keys belong on api-pro.dexpaprika.com and streaming-pro.dexpaprika.com. A free key sent to a Pro host gets 403 with &quot;error&quot;:&quot;wrong_host&quot; and the right host named in the body, on REST and on streaming alike. Paid keys belong on the Pro hosts only; /usage, below, tells you which plan the host you are calling sees.</p><p>Monthly allowances are enforced for keyless callers (per IP) and for free keys. Going over the per-minute rate returns 429 with Retry-After; using up the period&#39;s allowance returns 402, which no amount of retrying will fix until the period resets. The keyless per-minute limit is now separate from, and lower than, the limit a free key from <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a> gets. The figures moved during August and may move again, so we no longer print them anywhere; the <a href="https://dexpaprika.com/api/pricing">pricing page</a> is the source of truth, and the <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits">rate limits guide</a> explains how they are counted.</p><p>Every 402, 403 and 429 body now carries a links object with the <a href="https://console.dexpaprika.com/">console</a> (to register a free key), the docs and the pricing page, so a client that logs the body has the next step in front of it. Streaming uses the same body, including on the error event a stream emits when a cap is hit mid-session; tier is one of keyless, free, pro and enterprise.</p><pre>curl -s &quot;https://api.dexpaprika.com/usage&quot;</pre><pre>{&quot;plan&quot;:&quot;keyless&quot;}</pre><p>Two more details for anyone integrating a paid key. Responses on api-pro.dexpaprika.com are generated per caller and sent with cache-control: private, no-cache, so plan-specific data is never served from a shared cache. And GET https://api-pro.dexpaprika.com/ now answers 200 with a short JSON notice explaining that the host is for paid plans and expects your key in the Authorization header, instead of a bare 401.</p><h3>Two endpoints retired</h3><p>Both answer 410 rather than 404, so a client can tell a retired path from a wrong one.</p><ul><li><strong>/networks/{network}/dexes/{dex}/pools</strong> returns 410 since 5 August. The body names the replacement, /networks/{network}/pools/search, and links its documentation; add dex_name={dex} to keep the DEX filter. Rows come back under results with has_next_page and next_cursor. dex_name matches the DEX <strong>id</strong> (uniswap_v3, case-insensitive), not the display name; pass the dex_id field from /networks/{network}/dexes.</li><li><strong>/stream on </strong><strong>streaming.dexpaprika.com</strong> returns 410 since 26 August, pointing at /sse/prices.</li></ul><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/dexes/uniswap_v3/pools&quot;</pre><pre>{&quot;code&quot;:410,&quot;message&quot;:&quot;endpoint removed&quot;,&quot;replacement&quot;:&quot;/networks/{network}/pools/search&quot;,&quot;documentation&quot;:&quot;https://api.dexpaprika.com/docs/#tag/Pools/operation/searchNetworkPools&quot;}</pre><h3>Botanix retired, 35 networks</h3><p>Botanix shut down, so it was removed from the index on 26 August. /networks lists 35 chains and /stats reports the same. If you iterate /networks you have already noticed; if you hard-coded botanix, those calls now answer 404.</p><h3>Curve on Plasma, Nile V1 on Linea</h3><p>Plasma gained Curve with three pool types, each its own DEX id: curve_stableswap, curve_twocrypto and curve_tricrypto. Linea gained Nile V1 as nile_v1, next to the existing nile.</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/plasma/pools/search?dex_name=curve_stableswap&amp;limit=3&quot;</pre><h3>Shorter price windows in pool search</h3><p>Pool search on /networks/{network}/pools/search and the cross-chain /pools/search takes four new filters, price_change_percentage_1h_min, price_change_percentage_1h_max, price_change_percentage_5m_min and price_change_percentage_5m_max, and two new sort fields, price_change_percentage_1h and price_change_percentage_5m. July added 6h; with 1h and 5m the full set is 24h, 6h, 1h and 5m on pools. Token search still sorts on the 24h change only.</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/ethereum/pools/search?order_by=price_change_percentage_1h&amp;sort=desc&amp;liquidity_usd_min=100000&amp;limit=5&quot;</pre><p>The /search endpoint also changed how it lists DEXes: one row per DEX per chain, with pool count, 24h transactions and 24h volume summed across that DEX&#39;s factories, instead of one row per factory contract.</p><h3>Real-time token data on paid plans</h3><p>The token endpoints (/networks/{network}/tokens/{address}, /networks/{network}/tokens/search, /tokens/search, /networks/{network}/multi/prices) and pool search now serve real-time data on paid plans; keyless and free keys get the delayed view the <a href="https://dexpaprika.com/api/pricing">pricing page</a> describes. Response shapes didn&#39;t change.</p><p>Pools that discovery missed can now be added by hand; the first batch was three Fluid pools on Ethereum and Arbitrum and a Manifest pool on Solana.</p><h3>Streaming</h3><ul><li><strong>Reserve streams</strong> (/sse/reserves) are open to free keys; they were paid-only. /sse/prices stays keyless on the showcase list.</li><li>Streaming refusals carry the REST 402 body, also as the error event when a cap is reached mid-stream. The top-level message is kept for older clients.</li><li>A deadlock that could stall subscribers was fixed on 28 August.</li></ul><h3>dexpaprika.com</h3><ul><li><strong>Streaming showcase pages rebuilt.</strong> Each <a href="https://dexpaprika.com/streaming/ethereum">/streaming/{chain}</a> page now streams one flagship asset live over SSE, shows the measured updates per minute, compares polling with streaming, and prints the one keyless curl that produces the same stream. The old multi-token demo is gone; /streaming/preview/{chain} redirects to the canonical path</li><li><strong>Pricing page went self-serve</strong> on launch day: the <a href="https://dexpaprika.com/api/pricing">comparison table</a> has four columns (Keyless, Free, Pro, Enterprise) across REST, Streaming and Infrastructure, the CTAs go to the console, prices are marked excluding VAT, and the FAQ explains 402 versus 429 and how batch endpoints are billed. Bare /api redirects there</li><li><strong>Risk flags on token pages.</strong> A “Risk flags” section evaluates each token against a versioned registry (14 flags at month end: ticker and stablecoin impersonation, new token, missing metadata, pool concentration, all-time-high moves, missing price, missing or implausible liquidity and volume, thin liquidity, activity collapse, pool price divergence)</li><li><strong>A markdown mirror of every page.</strong> Append .md to any page URL (chain, DEX, pool, token, streaming, glossary, the /api/* pages) and you get the page as markdown, no Accept header needed. Built for agents and for pasting into a prompt</li><li><strong>Agent discovery:</strong> /.well-known/mcp serves the MCP manifest as JSON, <a href="https://dexpaprika.com/llms.txt">llms.txt</a> says when to use DexPaprika and when not to</li><li><strong>In the app:</strong> a Console button in the top bar when you are signed in, 5m and 1h price-change columns on the pool tables, charts default to 15-minute candles over 7 days on every screen size, mobile pool and token pages open on the chart, and chart data loads more reliably under rate limiting</li></ul><h3>Tools: every one of them can send a key now</h3><p>On 13 August none of our published tools could send an API key, which meant a paying customer couldn’t use their key with any of them. By the 17th all of them could. The 14 August SDK and CLI releases also moved the DEX pools call to pools/search, and the Go, TypeScript, Python and MCP releases send a versioned User-Agent.</p><ul><li><strong>Go SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-go/releases/tag/v1.8.0">v1.8.0</a>: dexpaprika.WithAPIKey(...), falling back to DEXPAPRIKA_API_KEY; v1.7.0 moved Pools.ListByDex() to pools search with cursor paging</li><li><strong>PHP SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-php/releases/tag/v1.8.0">v1.8.0</a>: Config::setApiKey(); v1.7.0 moved getDexPools() to pools search</li><li><strong>TypeScript SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-ts/releases/tag/v1.10.0">v1.10.0</a>: new DexPaprikaClient(baseUrl, options, { apiKey }); v1.9.0 changed pools.listByDex() to return the cursor-paginated search shape</li><li><strong>Python SDK</strong> <a href="https://github.com/coinpaprika/dexpaprika-sdk-python/releases/tag/v0.9.0">v0.9.0</a>: DexPaprikaClient(api_key=...); v0.8.0 moved pools.list_by_dex() to pools search</li><li><strong>CLI</strong> <a href="https://github.com/coinpaprika/dexpaprika-cli/releases/tag/v0.6.0">0.6.0</a>: config command to store a key, with validation</li><li><strong>n8n node</strong> <a href="https://github.com/coinpaprika/n8n-nodes-dexpaprika/releases/tag/v0.2.0">0.2.0</a>: optional DexPaprika credential</li><li><strong>dexpaprika-mcp</strong> <a href="https://www.npmjs.com/package/dexpaprika-mcp">2.5.0</a>: DEXPAPRIKA_API_KEY and DEXPAPRIKA_API_BASE_URL, a getKeyStatus tool that tells an agent whether its key is being honoured, 429 advice that reads Retry-After instead of guessing a daily reset, and the getDexPools tool on pools search (2.4.0)</li></ul><p>In every one of them the key is the entire Authorization header value, on its own. The host is never inferred from the presence of a key: free keys stay on the default host, and Pro and Enterprise move to api-pro.dexpaprika.com, which you set explicitly.</p><h3>CoinPaprika: budget headers, a new exchange, methodology 2.0</h3><h3>Your monthly budget, in headers</h3><p>Since 28 August every response from api.coinpaprika.com carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset: the plan&#39;s monthly call budget, what is left of it, and the seconds until it resets. 402 and 429 responses also carry Retry-After. If your client reads standard rate-limit headers, it now works against CoinPaprika without special casing.</p><pre>curl -sD - -o /dev/null &quot;https://api.coinpaprika.com/v1/global&quot; | grep -i ratelimit</pre><pre>ratelimit-limit: 20000<br>ratelimit-remaining: 19826<br>ratelimit-reset: 2395259</pre><h3>Revolut X</h3><p><a href="https://coinpaprika.com/exchanges/revolut-x/">Revolut X</a> joined the exchange list on 12 August, with 408 markets across 274 currencies at the time of writing. It is available at /v1/exchanges/revolut-x and its markets at /v1/exchanges/revolut-x/markets.</p><h3>Methodology 2.0</h3><p>The <a href="https://coinpaprika.com/methodology/">methodology page</a> is now versioned (2.0, effective 17 August) and carries a change policy. New in it:</p><ul><li><strong>Independent verification:</strong> the data-quality study submitted to the SEC Crypto Task Force in October 2025, in which CoinPaprika’s aggregation received grade A</li><li><strong>Outlier detection:</strong> the four-stage procedure documented end to end, from excluded markets to exchange-level anomalies. The check that catches groups of markets drifting together, which July’s update mentioned, is stage three</li><li><strong>Asset identifiers:</strong> DTI (ISO 24165), ISIN (ISO 6166) and the CoinMarketCap, CoinGecko and CryptoCompare ids, with a link to the <a href="https://docs.coinpaprika.com/api-reference/coins/api-id-mappings">ID mappings endpoint</a></li><li><strong>Independence:</strong> ownership, and what Fast Track does and doesn’t buy (review priority only; nothing affects price, rank or the confidence score)</li></ul><h3>Website</h3><ul><li><strong>Delisted coins answer </strong><strong>410.</strong> /coin/{id}/ for a coin whose is_active is false returns 410 with a link to the active list; legacy ids 301 to the renamed URL; /all-coins/ lists active coins only. If you scrape or deep-link coin pages, key on the API&#39;s is_active flag. Website only; the API is unchanged</li><li><strong>Education in other languages:</strong> an article not yet translated renders in English under the locale URL instead of 404, with a language chip in listings; articles show a difficulty level and published and updated dates</li><li>The listing request form at <a href="https://coinpaprika.com/add/">/add/</a> no longer truncates submissions or shifts the date by a day</li><li>The all-time-high volume and market cap shown on <a href="https://coinpaprika.com/market-overview/">/market-overview/</a> and <a href="https://coinpaprika.com/exchanges/">/exchanges/</a> were a stale reading; fixed</li></ul><h3>MCP server 1.4.0</h3><p><a href="https://www.npmjs.com/package/@coinpaprika/mcp">@coinpaprika/mcp 1.4.0</a> states the free tier correctly (20,000 calls a month, no daily quota, as the <a href="https://coinpaprika.com/api/pricing/">pricing page</a> lists it) and stops reporting a remaining balance it couldn’t know. The hosted server at mcp.coinpaprika.com serves the same 30 tools plus submitFeedback.</p><h3>Availability and rollout</h3><p><strong>DexPaprika:</strong></p><ul><li>Plan and host enforcement, denial bodies with links: live since 7 August; allowances and rates changed during August</li><li>/networks/{network}/dexes/{dex}/pools retired 5 August; legacy /stream retired 26 August</li><li>Botanix retired 26 August; Curve on Plasma 19 August; Nile V1 on Linea 10 August</li><li>1h and 5m price change filters and sorts: 7 August</li><li>Real-time token data on paid plans: 27 August</li><li>Tool releases: 14 to 17 August</li><li>Site: streaming showcase pages 5 August, pricing page self-serve for the 7 August launch, risk flags and .md mirrors 11 August, /.well-known/mcp 24 August</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Budget headers and Retry-After: 28 August</li><li>Revolut X: 12 August</li><li>Methodology 2.0: effective 17 August, published 21 August</li><li>410 for delisted coin pages: 24 August</li><li>@coinpaprika/mcp 1.4.0: 19 August</li></ul><p><strong>Breaking changes:</strong> plan and host enforcement, which is the one to read if you call us without a key: keyless traffic now hits a monthly cap and a separate per-minute rate, and a key on the wrong host is refused. Then the two retired DexPaprika endpoints, the Botanix removal, and the SDK releases that moved listByDex to the pools search shape (Go 1.7.0, PHP 1.7.0, TypeScript 1.9.0, Python 0.8.0). No breaking changes on the CoinPaprika API; the 410 on delisted coin pages affects the website only.</p><h3>Measurable impact</h3><ul><li>35 networks, 33M+ tokens and 36M+ pools indexed on DexPaprika, as the <a href="https://dexpaprika.com/api/pricing">pricing page</a> counts them</li><li>Four new DEX ids across two chains</li><li>One new exchange with 408 markets on CoinPaprika</li><li>Seven tools that can send a key (four SDKs, the CLI, the MCP server, the n8n node), up from zero on 13 August</li></ul><h3>Get started</h3><p><strong>DexPaprika:</strong></p><ul><li>Register a free key at <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a> and put it in the Authorization header, on its own</li><li>Read the <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits">rate limits guide</a> and the <a href="https://docs.dexpaprika.com/knowledge-base/error-handling">error handling guide</a> before writing a retry loop; treat 402 as final for the period</li><li>Docs: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Watch RateLimit-Remaining if you run close to the monthly budget</li><li>Docs: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li></ul><p><strong>Example query:</strong> the biggest 1h movers on Base right now</p><pre>curl -s &quot;https://api.dexpaprika.com/networks/base/pools/search?order_by=price_change_percentage_1h&amp;sort=desc&amp;liquidity_usd_min=100000&amp;limit=5&quot;</pre><h3>Questions?</h3><p>If you are building on our APIs and have questions about these updates:</p><ul><li>DexPaprika docs: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li><li>CoinPaprika docs: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li><li>DexPaprika MCP server: <a href="https://github.com/coinpaprika/dexpaprika-mcp">https://github.com/coinpaprika/dexpaprika-mcp</a></li><li>CoinPaprika MCP server: <a href="https://github.com/coinpaprika/coinpaprika-mcp">https://github.com/coinpaprika/coinpaprika-mcp</a></li></ul><p><strong>About the author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a6e77499282" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/august-2026-product-update-coinpaprika-dexpaprika-4a6e77499282">August 2026 product update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[July 2026 Product Update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/july-2026-product-update-coinpaprika-dexpaprika-4e0e1f5cead1?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e0e1f5cead1</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 12:39:51 GMT</pubDate>
            <atom:updated>2026-08-10T11:09:14.022Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Date:</strong> August 7, 2026 <strong>Author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uofcYKhyol0R1N67XfImJw.png" /></figure><p>For two years DexPaprika ran as an open API with no accounts and no keys. That was the right way to start, and it is how most of you found us. In July we added the other half: DexPaprika now has user accounts, API keys and a console to manage them. Nothing moved behind a key that was not behind one before. Every endpoint, every chain and the full OHLCV history still answer without one, and the keyless curl you already have in your terminal still works.</p><p>Alongside that, coverage grew by a chain and five DEXes, and pool discovery picked up a new time window.</p><h3>TL;DR</h3><p><strong>DexPaprika:</strong></p><ul><li><strong>Accounts and API keys are live.</strong> Manage them at <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a>, including usage history and an error log of what your failed calls returned</li><li><strong>No key still works.</strong> All endpoints, all 36 chains and full OHLCV history answer keyless</li><li><strong>New </strong><strong>/usage endpoint</strong> reports the plan a request was evaluated against</li><li><strong>New error semantics:</strong> 429 for going too fast, 402 for exhausting the period allowance</li><li><strong>Streaming is split by host:</strong> the keyless host serves 36 showcase assets, a key unlocks any token and the transaction and reserve streams</li><li><strong>Robinhood Chain is our 36th network,</strong> with Uniswap V2, V3 and V4 indexed</li><li><strong>New DEXes:</strong> Ekubo V2 and V3 on Ethereum, Agni Finance V2 and V3 on Mantle, SectorOne V2.2 on MegaETH</li><li><strong>6h price change</strong> joins the pool search sort and filter fields</li><li><strong>API Terms of Use published</strong> at <a href="https://dexpaprika.com/api/terms">dexpaprika.com/api/terms</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li><strong>MiCA compliance filter</strong> on the exchanges list, with a badge on regulated venues</li><li><strong>5 new DEX market sources</strong> across Robinhood Chain, Ethereum, Mantle and MegaETH, plus the Trapix exchange</li><li><strong>Better price accuracy</strong> on thin markets</li><li>No breaking API changes</li></ul><h3>The headline: DexPaprika has accounts and API keys</h3><h4>The console</h4><p>Everything account-shaped now lives at <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a>. Sign in with the same account you already use on coinpaprika.com, or with Google, X or an email and password.</p><p>Inside, each screen answers one question:</p><ul><li><strong>Dashboard:</strong> am I fine? Current plan, what the period has used, when the next cycle starts</li><li><strong>Usage:</strong> where did it go? Per endpoint, day by day</li><li><strong>Error Log:</strong> what did my failed calls actually return?</li><li><strong>API Keys:</strong> reveal, copy, revoke. One active key per account</li><li><strong>MCP &amp; AI Setup:</strong> ready-made config for Claude, Cursor, Cline and anything else that speaks MCP</li><li><strong>Notifications:</strong> where account alerts land</li></ul><p>The Error Log deserves a mention on its own. When something breaks at 2am, the first question is always whether the API is down or your call was wrong. Now you can look it up instead of guessing.</p><h4>Your key is tied to a host</h4><p>A key is valid on a specific pair of hosts, either api.dexpaprika.com and streaming.dexpaprika.com or api-pro.dexpaprika.com and streaming-pro.dexpaprika.com. The API Keys screen in the console tells you which pair applies to yours. Send a key to the wrong host and you get a 403 wrong_host that names the right one, rather than a silent failure.</p><p>The important thing for anyone already integrated: there are no feature gates. Every endpoint, all 36 chains, all DEXes and the complete OHLCV history answer without a key. A key raises your allowance and unlocks any-token streaming. Current per-minute and monthly numbers are on the <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits">rate limits page</a>.</p><h4>Check your plan from the terminal</h4><p>The new /usage endpoint reports the plan a request was evaluated against. With a key on the authenticated host it also returns the account email and what the current period has used and has left.</p><pre>curl &quot;https://api.dexpaprika.com/usage&quot;</pre><pre>{&quot;plan&quot;:&quot;keyless&quot;}</pre><h4>Two error codes, two different meanings</h4><p>Rate limiting and allowance exhaustion used to look similar from the client side. They no longer do:</p><ul><li><strong>429 Too Many Requests</strong> means you went too fast. It carries Retry-After. Back off and continue.</li><li><strong>402 Payment Required</strong> means the allowance for the period is gone. Retrying will not help, and there is deliberately no Retry-After. The body names your tier, when the allowance resets and where to go next.</li></ul><p>If you have a retry wrapper around our client, this is the one change worth making today: treat 402 as terminal for the period, not as a transient error to hammer.</p><h4>Streaming is now split by host</h4><p>Price streaming stays open without a key, on a fixed list of 36 showcase assets, one flagship token per chain. They exist so you can watch real pushed prices before you sign up for anything. The <a href="https://docs.dexpaprika.com/streaming/showcase-streams">full list with live demos</a> is in the docs.</p><pre>curl -N &quot;https://streaming.dexpaprika.com/sse/prices\<br>?method=token_price\<br>&amp;chain=ethereum\<br>&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&quot;</pre><pre>event: token_price<br>data: {&quot;address&quot;:&quot;0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&quot;,<br>       &quot;chain&quot;:&quot;ethereum&quot;,&quot;price&quot;:&quot;1912.6105938833623&quot;,<br>       &quot;timestamp&quot;:1786100665}</pre><p>A key removes the restriction: any token we index, on all three stream types, up to 10 concurrent connections. Transaction and reserve streams need a key outright. Ask for a token outside the showcase list without one and you get a 403 that explains why and links to registration, instead of an empty stream that never emits.</p><p>Nothing about the transport changed. Same SSE, same event shapes, same delivery rate.</p><h4>Terms of use</h4><p>DexPaprika now has its own <a href="https://dexpaprika.com/api/terms">API Terms of Use</a>, linked from the site footer.</p><h3>DexPaprika: coverage and API</h3><h4>Robinhood Chain, our 36th network</h4><p>Robinhood Chain is indexed end to end, with Uniswap V2, V3 and V4 and roughly 20,000 pools. It arrived busy: V4 alone accounts for the bulk of its daily volume.</p><pre>curl &quot;https://api.dexpaprika.com/networks/robinhood/pools/search\<br>?order_by=volume_usd_24h&amp;sort=desc&amp;limit=5&quot;</pre><p>Coverage now stands at 36 chains, 33M+ tokens, 36M+ pools and 230+ DEXes, over 96% of on-chain DEX volume. The live snapshot is always at <a href="https://api.dexpaprika.com/stats">/stats</a> and on the generated <a href="https://docs.dexpaprika.com/coverage">coverage page</a>.</p><h4>Five new DEXes</h4><pre>DEX                Chain       dex_name<br>Ekubo V2           Ethereum    ekubo_v2<br>Ekubo V3           Ethereum    ekubo_v3<br>Agni Finance V2    Mantle      agni_v2<br>Agni Finance V3    Mantle      agni_v3<br>SectorOne V2.2     MegaETH     sectorone_v2_2</pre><pre>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/search\<br>?dex_name=ekubo_v3&amp;limit=5&quot;</pre><p>Curve StableSwap-NG and Fluid pools also got their reserve tracking resynced, so TVL on those venues reflects the chain again.</p><h4>6h price change</h4><p>Pool search gained a 6 hour window alongside the existing 5m, 1h and 24h ones. It works as both a returned field and a sort key, which makes it the sweet spot for spotting moves that are more than noise but have not made the daily table yet.</p><pre>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/search\<br>?order_by=price_change_percentage_6h&amp;sort=desc&amp;limit=5&quot;</pre><p>The same column is now sortable on the pools tables at dexpaprika.com.</p><h4>Pools for a token</h4><p>Finding every pool for a token now goes through pool search with a token_address filter, which means one endpoint and one response shape for all pool discovery:</p><pre>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/search\<br>?token_address=0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48\<br>&amp;limit=5&quot;</pre><p>The legacy /networks/{chain}/tokens/{address}/pools path returns 410 Gone with the replacement named in the body, the same pattern as June&#39;s search migration.</p><h4>Search that resolves addresses directly</h4><p>Paste a complete EVM address, or a Solana or Tron one, and search now treats it as an exact lookup rather than a fuzzy text match. Name and symbol search was reindexed at the same time. In practice: address lookups return faster and stop surfacing near-miss tokens above the one you actually pasted.</p><h4>Web app</h4><ul><li><a href="https://dexpaprika.com/chains"><strong>/chains</strong></a> ranks every network we index by volume, pools and activity</li><li><a href="https://dexpaprika.com/ethereum/dexes"><strong>/{chain}/dexes</strong></a> does the same for exchanges within a chain</li><li><strong>6h column and timeframe</strong> on the pool tables and the homepage trend strip</li><li><strong>Quiet venues get a real empty state</strong> with useful links, instead of a blank table</li><li><strong>The streaming console reconnects properly</strong> after a dropped connection, with a manual retry when the backoff gives up</li><li><strong>Stablecoin-led pairs no longer crowd the trending strip</strong>, so the movers list shows actual movers</li></ul><h4>Docs and tools</h4><p>The docs picked up an <strong>AI Integration</strong> tab covering Codex, MCP clients, agent skills and the Vercel AI SDK, an index of every DexPaprika tool and SDK, a <a href="https://docs.dexpaprika.com/knowledge-base/console">console guide</a> and the showcase stream list.</p><p>Shipped versions in July:</p><ul><li>dexpaprika-mcp 2.3.2 and @coinpaprika/mcp 1.3.3, both with rewritten tool descriptions so an agent can pick the right tool from the description alone (dexpaprika-mcp is on 2.3.3 as of publishing)</li><li>Go SDK v1.6.1</li><li>dexpaprika-cli 0.4.4</li><li><a href="https://pypi.org/project/langchain-dexpaprika/">langchain-dexpaprika</a> 0.1.0 on PyPI, DexPaprika tools for LangChain agents</li></ul><p>The hosted MCP at <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a> tracks the same releases, so there is nothing to update there.</p><h3>CoinPaprika: MiCA filtering and more DEX markets</h3><h4>See only MiCA-compliant exchanges</h4><p>Exchange rows now carry a MiCA badge, and a “Show only MiCA” checkbox on the <a href="https://coinpaprika.com/exchanges/">exchanges list</a> hides everything else, including in the liquidity table. If you are picking venues for an EU-facing product, that filter is the whole job in one click.</p><h4>Five new DEX market sources</h4><p>The DEXes DexPaprika started indexing in July feed CoinPaprika’s market data too:</p><pre>Robinhood Chain   Uniswap V2, Uniswap V3, Uniswap V4<br>Ethereum          Ekubo V2, Ekubo V3<br>Mantle            Agni Finance V3<br>MegaETH           SectorOne V2.2</pre><p>Tokens trading on these venues map to their contract platforms, so prices and market listings attribute correctly on coin pages and through the API. Each one has its own exchange page, for example <a href="https://coinpaprika.com/exchanges/ekubo-v3-ethereum/">Ekubo V3 on Ethereum</a> and <a href="https://coinpaprika.com/exchanges/uniswap-v4-robinhood/">Uniswap V4 on Robinhood Chain</a>.</p><p>On the centralized side, <a href="https://coinpaprika.com/exchanges/trapix-exchange/">Trapix</a> was added as a new exchange and the Kanga integration was pointed at the exchange’s current API.</p><h4>Better price accuracy on thin markets</h4><p>Outlier detection used to catch individual rogue quotes well and correlated ones poorly. It now spots groups of in-range markets drifting the mean together, which is the failure mode that produces a wrong price nobody can point at a single source for.</p><p>No breaking API changes on CoinPaprika this cycle.</p><h3>Availability and rollout</h3><p><strong>DexPaprika:</strong></p><ul><li>Accounts, API keys and the console are live now</li><li>Keyless access is unchanged in scope: all endpoints, all 36 chains, full OHLCV history, no key required to start</li><li>/usage, the structured 402 and 429 bodies, and the streaming host split are live</li><li>Robinhood Chain, the five new DEXes, the 6h field and the token_address filter are live</li><li>/networks/{chain}/tokens/{address}/pools returns 410 with its replacement named</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>MiCA filtering, the new DEX market sources and the price accuracy work are live</li><li>No breaking API changes</li></ul><p><strong>Action needed:</strong> nothing, if you call keyless and stay inside the standard allowance. If you call from many machines behind one IP, or you stream, register a key so your allowance is counted per account rather than per address. If you retry on error, make 402 terminal for the period.</p><p><strong>One August note, since this update publishes in August:</strong> on 5 August /networks/{chain}/dexes/{dex}/pools was retired and now returns 410. Use /networks/{chain}/pools/search?dex_name={dex} instead. Our SDKs, CLI and MCP servers already point at the new path.</p><h3>Measurable impact</h3><ul><li><strong>Coverage:</strong> 36 chains, 33M+ tokens, 36M+ pools, 230+ DEXes, over 96% of on-chain DEX volume</li><li><strong>One new chain and five new DEXes</strong> indexed in a single month</li><li><strong>Streaming:</strong> 36 assets you can stream with no key, any token with one</li><li><strong>Keyless remains complete:</strong> no endpoint, chain or history window is gated behind registration</li></ul><h3>Get started</h3><p><strong>DexPaprika:</strong></p><ul><li>Get a key: <a href="https://console.dexpaprika.com/">console.dexpaprika.com</a></li><li>Limits and errors: <a href="https://docs.dexpaprika.com/knowledge-base/rate-limits">rate limits</a> and <a href="https://docs.dexpaprika.com/knowledge-base/error-handling">error handling</a></li><li>Agent integrations: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a> and the hosted MCP at <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Explore: <a href="https://docs.coinpaprika.com/">docs.coinpaprika.com</a></li></ul><p><strong>One query to try today,</strong> live prices pushed with no key and no signup:</p><pre>curl -N &quot;https://streaming.dexpaprika.com/sse/prices\<br>?method=token_price\<br>&amp;chain=ethereum\<br>&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&quot;</pre><h3>Questions?</h3><p>If you’re building on our APIs and have questions about these updates:</p><ul><li>DexPaprika documentation: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li><li>CoinPaprika documentation: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li></ul><p><strong>About the author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e0e1f5cead1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/july-2026-product-update-coinpaprika-dexpaprika-4e0e1f5cead1">July 2026 Product Update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI agent skills go stale (so we taught ours to check their own pulse)]]></title>
            <link>https://medium.com/coinpaprika/ai-agent-skills-go-stale-so-we-taught-ours-to-check-their-own-pulse-f90c9b3858d9?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/f90c9b3858d9</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 07:10:34 GMT</pubDate>
            <atom:updated>2026-07-14T07:10:34.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M3B4VDTjdC9cW73Skpf7Ng.png" /></figure><p>This week I found a skill file on one of our own pages confidently teaching AI agents to call API endpoints that have returned HTTP 410 since June 30. Nobody touched the file. That’s the point: nobody touched the file. The world changed underneath it, and a markdown document has no way to notice.</p><p>If you’re publishing skills for AI agents (and if you run an API in 2026, you probably are, or will be), this post is about the failure mode nobody’s update channel covers. We got burned by it three different ways in a single month. It ends with the small pattern we now ship in every skill: a version header plus an instruction that makes the agent verify the skill’s freshness before trusting it.</p><h3>Skills are the integration surface with no update mechanism</h3><p>A skill is a markdown file that teaches an agent how to use something: which endpoints exist, what parameters they take, what the responses look like. Agents load it into context and follow it. We’ve written about <a href="https://coinpaprika.com/education/ai-agent-skills-how-agents-self-configure-with-skill-md-files/">how agents self-configure with skill files</a> before; the short version is that a good skill turns a model from “vaguely aware your API exists” into “makes correct calls on the first try.”</p><p>Now look at how skills reach users. They get copied. Pasted into a config directory, fetched once by an installer, bundled into a plugin, cached by a marketplace. Every one of those is a snapshot with no version stamp, no update check, and no channel to push a fix through. Compare that with the rest of the stack: your SDK has npm and semver, your docs redeploy on merge, your hosted MCP updates server-side. The skill file, the thing that most directly steers what an agent <em>does</em>, is distributed like a chain letter.</p><p>And nothing in the format pushes back. I checked Anthropic’s official skills while writing this: the frontmatter carries name, description, sometimes a license. No version field, on the reference implementations, from the company that defined the format. The format tolerates extra frontmatter keys just fine; there&#39;s simply no convention demanding one. Which means staleness isn&#39;t just unfixed by default. It&#39;s <em>undetectable</em> by default.</p><h3>Three ways ours went stale in one month</h3><p>We didn’t learn this from a thought experiment. In one month our skills rotted through three different mechanisms.</p><p><strong>Split-brain drift.</strong> A July audit found two copies of our DexPaprika skill, each holding half the truth: the GitHub copy had the June endpoint migration but documented a streaming event that no longer existed, while the local working copy had the streaming fix but still listed four endpoints that now return 410. Both copies had been “updated recently.” Neither was correct. Without versions, there wasn’t even a way to say which one was newer.</p><p><strong>The version-gated cache that gates fixes out.</strong> Our Claude Code plugin re-copies skill content only when the plugin’s version string changes. In May we shipped content corrections without bumping the version. Result: for six weeks, the fix was merged, published, and visible in the repo, and not a single installed user received it. A version gate with no bump discipline doesn’t just fail to help; it actively holds fixes hostage.</p><p><strong>Served-page rot.</strong> The freshest embarrassment, the one from this week: the skill file served on our agents page turned out to be an old snapshot still teaching removed endpoints, while the corrected copy sits one deploy away (the fix is in flight as I write this). The page looked fine. The URL answered 200. An agent reading it would build against an API that stopped existing on June 30, then report to its user that the data source seems broken.</p><p>Three mechanisms, one root cause. A skill is a claim about the present tense written at a fixed point in the past, and every copy of it ages independently, silently, in places you don’t control.</p><h3>The fix: make the skill check its own pulse</h3><p>You can’t recall the copies. What you can do is make every copy carry its own freshness protocol. Since July, the first thing in each of our skills, before any endpoint documentation, is this block, verbatim from the <a href="https://raw.githubusercontent.com/coinpaprika/skills/main/dexpaprika-api/SKILL.md">live file</a>:</p><pre>Freshness check (run once per session, before relying on this skill):<br>this file is `version: 2.0.0`. Fetch the latest copy&#39;s header:</pre><pre>    curl -s -r 0-400 <a href="https://raw.githubusercontent.com/coinpaprika/skills/main/dexpaprika-api/SKILL.md">https://raw.githubusercontent.com/coinpaprika/skills/main/dexpaprika-api/SKILL.md</a></pre><pre>If the remote `version:` differs from this file&#39;s, this copy is outdated:<br>fetch the full remote file, follow it instead of this one, and replace<br>your local copy with it.</pre><p>The reader of that instruction is the agent. It loads the possibly stale skill, and the skill’s first move is to tell it how to find out. The -r 0-400 is a Range request: it pulls only the first ~400 bytes, which is exactly enough to cover the frontmatter where version: lives. One tiny HTTP call per session, and the copy your user grabbed eight months ago either confirms itself or replaces itself.</p><p>The infrastructure choices matter, and we tested them before committing:</p><ul><li><strong>Raw file hosting, not the API.</strong> raw.githubusercontent.com answers in well under a second, needs no auth, and publishes no request quota (no rate-limit headers either; we checked). The GitHub commits API would have been the obvious &quot;check for updates&quot; call, and it allows 60 unauthenticated requests per hour, which an agent fleet burns through before breakfast.</li><li><strong>Range requests keep it cheap.</strong> 400 bytes instead of a 16 KB file, per session, per agent.</li><li><strong>ETags come free.</strong> The raw endpoint serves strong ETags and honors If-None-Match (we verified the 304 path live), so a more sophisticated client can skip even those 400 bytes when nothing changed.</li><li><strong>Propagation is fast enough.</strong> The raw CDN caches for about five minutes, so a fix we push is what agents worldwide see within minutes, no release pipeline in between.</li></ul><h3>What this doesn’t fix (learn from our bruises)</h3><p>Honesty section, because the pattern has real limits.</p><p>The version bump is a human act, and humans forget: that’s precisely how the plugin incident happened. A freshness check keyed on version: inherits that weakness, so treat the version bump as part of the definition of done for any skill edit, enforce it in review, and if you can, compare content hashes or ETags instead of trusting the string alone.</p><p>The check only works while the canonical URL keeps answering. Move the repo, rename the file, and every distributed copy’s freshness protocol dies with the old path. The URL in your skills is a forever commitment, the same way a removed API endpoint’s tombstone is.</p><p>And it’s advisory. An agent can skip the instruction, a client can block network calls, a copy can have the header stripped. This is a seatbelt, not a force field. The structural complement is keeping the heavyweight logic server-side (hosted MCP, live docs) so the skill is a thin, cheap-to-refresh pointer rather than a fat cached truth.</p><h3>The checklist for skill authors</h3><ul><li>Add version: to your SKILL.md frontmatter today. The format accepts extra keys; nothing breaks.</li><li>Put a freshness-check instruction in the skill’s first lines, pointing at a raw URL you commit to keeping alive, with a Range request so it’s cheap.</li><li>Make the version bump part of your review checklist. An unbumped content fix is a fix nobody gets.</li><li>If any layer caches your skill behind a version gate (plugins, marketplaces), assume it does exactly what it promises: no bump, no propagation.</li><li>Audit what’s actually being served. Our stale copy this week wasn’t in a user’s cache; it was on our own page. curl your own URLs and read what comes back.</li></ul><p>Skills are documents that configure intelligence. It took us three separate incidents to internalize what that implies: a document that steers an agent needs to be able to tell the agent when it’s lying. Make your skills check their own pulse; the agents will do the rest.</p><p><em>Mateusz Sroka is the Lead Developer Advocate at CoinPaprika and DexPaprika. The versioned skills live in the </em><a href="https://github.com/coinpaprika/skills"><em>coinpaprika/skills</em></a><em> repo, agent onboarding starts at </em><a href="https://agents.dexpaprika.com/"><em>agents.dexpaprika.com</em></a><em>, and the APIs they teach are documented at </em><a href="https://docs.dexpaprika.com/"><em>docs.dexpaprika.com</em></a><em> and </em><a href="https://docs.coinpaprika.com/"><em>docs.coinpaprika.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f90c9b3858d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/ai-agent-skills-go-stale-so-we-taught-ours-to-check-their-own-pulse-f90c9b3858d9">AI agent skills go stale (so we taught ours to check their own pulse)</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we removed 5 API endpoints without breaking AI agents]]></title>
            <link>https://medium.com/coinpaprika/how-we-removed-5-api-endpoints-without-breaking-ai-agents-c83c828a7279?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/c83c828a7279</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 07:00:35 GMT</pubDate>
            <atom:updated>2026-07-14T07:00:35.542Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f26j0sI0hGGty6RnIm9osA.png" /></figure><p>On June 30 we shut off five endpoints on the <a href="https://docs.dexpaprika.com/introduction">DexPaprika API</a>. Not deprecated with a warning banner. Removed. Requests to them now get an HTTP 410 and a three-field JSON body.</p><p>Ten years ago the checklist for this was well understood: announce early, email the integrators, publish a migration guide, watch support tickets. All of that assumes the thing calling your API has an inbox and reads documentation. In 2026, AI agents are a real slice of any public API’s traffic, ours included, and agents read neither. They pick tools from schemas, follow errors, and retry. Some of them were configured a year ago by a developer who has since changed jobs.</p><p>This is the story of how we designed the removal for that audience, what actually broke elsewhere in the industry when APIs didn’t, and the small piece of JSON that does most of the work.</p><h3>What we removed and why</h3><p>DexPaprika’s discovery surface had grown organically into five overlapping list endpoints: /pools, /networks/{chain}/pools, /networks/{chain}/pools/filter, /networks/{chain}/tokens/top, and /networks/{chain}/tokens/filter. Each returned slightly different shapes with slightly different filters and pagination.</p><p>Humans coped. Agents didn’t. When a model sees five near-identical tools for “find pools,” it picks one mostly at random, and the differences between them (which one has liquidity filters? which one paginates?) burn context and produce wrong calls. Consolidating into two search endpoints (/pools/search and /tokens/search, each with global and per-network forms, cursor pagination, results under a consistent results key) made the API smaller and every tool-calling model measurably less confused about it.</p><p>So the destination was clear. The problem was the journey: how do you move an audience that doesn’t read announcements?</p><h3>What happens when you deprecate at an agent that isn’t looking</h3><p>You don’t have to imagine it; the public issue trackers already ran the experiment. When Jira retired its classic search endpoint with an HTTP 410 this year, the <a href="https://github.com/sooperset/mcp-atlassian/issues/1295">most popular community Jira MCP server</a> (5,500+ stars) broke in the worst possible way: jira_search silently returned empty results for every query, because the layer between the model and the API swallowed the 410. Users were confused enough about where the failure lived that the <a href="https://github.com/atlassian/atlassian-mcp-server/issues/70">same breakage got filed on Atlassian&#39;s own MCP server repo</a> too.</p><p>Read that failure mode again, because it’s worse than a crash. The agent didn’t error. It reported <em>no matching issues</em>, confidently, to users who had no reason to doubt it. An error gets investigated; an empty result gets believed. And nobody in that chain did anything unusual: the API owner deprecated properly by their own docs, the MCP maintainers ship fixes fast, and it still shipped silence to end users. That’s how easy this is to get wrong.</p><p>That was the outcome we were designing against.</p><h3>The 410 contract</h3><p>Here’s the entire response from one of our removed endpoints today, captured live:</p><pre>curl -i &quot;https://api.dexpaprika.com/networks/ethereum/pools/filter&quot;</pre><pre>HTTP/2 410<br>{<br>  &quot;code&quot;: 410,<br>  &quot;message&quot;: &quot;endpoint removed&quot;,<br>  &quot;replacement&quot;: &quot;/networks/:network/pools/search&quot;<br>}</pre><p>Three decisions in those few bytes, each of them specifically for machine callers.</p><p><strong>410, not 404.</strong> A 404 says “nothing here, maybe you typo’d,” and a well-built client treats it as <em>my mistake, try to fix my parameters</em>. A 410 says “this existed, it’s gone on purpose, and it is not coming back.” For a retry loop, that difference decides between hammering a dead path and giving up correctly. HTTP had the right semantics for deliberate removal since 1997; most APIs just don’t bother using them.</p><p><strong>A machine-readable </strong><strong>replacement field.</strong> This is the piece that does the heavy lifting. A human reads a migration guide; a model reads the error body it just received, because the error body lands directly in its context. While writing this piece I ran the experiment on a fresh coding agent with no documentation access: I asked it to fetch top Ethereum pools from the <em>removed</em> filter endpoint. It called the dead path, got the 410, read &quot;replacement&quot;: &quot;/networks/:network/pools/search&quot;, substituted ethereum into the placeholder on its own, and had live results two calls later. Nobody told it to migrate. The error did. (It even fixed its sort parameter from a second error listing the valid values, which is a strong argument for putting your enums in your error messages too.) Error messages are prompts now. You should write them like prompts.</p><p><strong>Nothing else.</strong> No HTML error page, no prose paragraph, no link farm. Small enough that no client truncates it, unambiguous enough that no model misreads it.</p><h3>The server is the easy half</h3><p>Flipping five routes to 410 took a morning. The real project was everything downstream, because an endpoint isn’t deprecated when your server says so. It’s deprecated when the last cached copy of your tooling stops calling it.</p><p>Agents reach an API through layers: an MCP server installed from npm months ago, an SDK pinned in a lockfile, a CLI in someone’s dotfiles, a skill file pasted into an agent’s config, docs that a model scraped in January. Every one of those layers keeps working against the old paths right up until removal day, and every one fails at once if you only changed the server.</p><p>So the migration window was mostly propagation. Updated releases of the MCP server, the TypeScript and Python SDKs, the Go and PHP SDKs, and the CLI all shipped with the endpoint change (the exact versions are in our <a href="https://medium.com/coinpaprika/june-2026-product-update-coinpaprika-dexpaprika-b81635f337ba">June 2026 product update</a>). The same window covered the <a href="https://docs.dexpaprika.com/api-reference/introduction">API docs</a>, the machine-readable llms.txt files, and the agent skill files on <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a>.</p><p>The one layer that needed zero user action is worth highlighting: the hosted MCP server. Anyone whose agent connects to it got the new tools the moment we deployed, because the tooling lives on our side of the wire. After this migration I think of that as a deprecation feature, not just a convenience. Every layer users install and cache is a layer that can go stale; every layer you host is one you can fix for everyone at once.</p><p>And for whoever updates on their own schedule, the 410 contract sits underneath as the safety net. The layers that updated moved on. The layers that didn’t get told exactly where to go, in JSON, forever.</p><h3>The checklist, if you’re about to do this</h3><ul><li>Consolidate first if you can: fewer, more regular endpoints help agents more than any migration doc will.</li><li>Use 410 for removal, never 404. The semantics exist; use them.</li><li>Put the replacement path in the error body as a named field. The model that broke your integration is also the thing most likely to read it and self-repair.</li><li>Inventory every cached layer between agents and your API: MCP servers, SDKs, CLIs, skills, llms.txt, scraped docs. Ship them together, in the same window.</li><li>Host what you can. Server-side tooling is the only layer you can migrate for all users at once.</li><li>Announce the date ahead in headers (RFC 8594), not just in prose.</li><li>Keep the tombstones forever.</li></ul><p>The result on our side, as I write this ten days after removal: zero user-reported 410 issues across our SDK, MCP, and CLI repos, no “search returns nothing” reports, and anything still calling the old paths gets a machine-usable answer instead of a dead end.</p><p>Deleting endpoints used to be a communications project. It’s an interface-design project now, and your most important reader is a language model holding your error message in its context window, deciding what to do next. Write it something useful.</p><p><em>Mateusz Sroka is the Lead Developer Advocate at CoinPaprika and DexPaprika. The unified search endpoints are documented in the </em><a href="https://docs.dexpaprika.com/api-reference/introduction"><em>DexPaprika API reference</em></a><em>, and if you’re wiring an agent to on-chain data, start at </em><a href="https://agents.dexpaprika.com/"><em>agents.dexpaprika.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c83c828a7279" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/how-we-removed-5-api-endpoints-without-breaking-ai-agents-c83c828a7279">How we removed 5 API endpoints without breaking AI agents</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[June 2026 Product Update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/june-2026-product-update-coinpaprika-dexpaprika-b81635f337ba?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/b81635f337ba</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Fri, 03 Jul 2026 07:07:36 GMT</pubDate>
            <atom:updated>2026-07-03T08:55:13.183Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Date:</strong> July 2, 2026 <strong>Author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TZ7o9o0WszH9_lA4bUnBWw.png" /></figure><p>In May we opened pool reserves up as a live stream. In June we did the same for the trades themselves: every swap on a tracked pool can now be streamed as it lands, with USD amounts attached. On the REST side, June was the month pool and token discovery got rebuilt around a single, more powerful search endpoint family, and that one is a breaking change, so please read on if you list or filter pools programmatically.</p><h3>TL;DR</h3><p><strong>DexPaprika:</strong></p><ul><li><strong>Breaking: unified search endpoints.</strong> Five legacy list/filter endpoints were removed and replaced by /pools/search and /tokens/search (global and per-network). Old paths return 410 Gone with a machine-readable pointer to their replacement. All our SDKs, MCP servers and the CLI are already migrated</li><li><strong>New: live swap stream.</strong> /sse/transactions pushes individual swaps in real time, per pool or per token, with USD-denominated amounts on both sides of the trade</li><li><strong>Pool details now include </strong><strong>liquidity_usd</strong>, so one lookup gives you TVL without a second call</li><li><strong>Fresher prices and stats:</strong> token prices are computed continuously from volume-weighted trade data with smoothing against single-trade flicker, and pool/token statistics update as trades arrive instead of on a schedule</li><li><strong>Cleaner history:</strong> anomaly detection for OHLCV now adapts to each token’s volatility, and the cleanup was applied retroactively across roughly a year of candles</li><li><strong>New DEXes on Base:</strong> <a href="https://dexpaprika.com/base/hydrex">Hydrex</a> and <a href="https://dexpaprika.com/base/aerodrome_slipstream_2">Aerodrome Slipstream 2</a></li><li><strong>Web app:</strong> one-click branded chart snapshots, full display of multi-token pools, liquidity shown on every network, shareable tab links, and a 5-minute trending timeframe</li></ul><p><strong>CoinPaprika:</strong></p><ul><li><strong>15 new DEX market sources across 11 networks</strong>, from Base and Ethereum to Sui, Aptos, Sei, Sonic, HyperEVM, Celo and MegaETH</li><li>DEX-native assets are getting deeper backfilled price history, so charts no longer have to start on listing day</li><li>No breaking API changes on CoinPaprika</li></ul><h3>The headline: one search endpoint family for pools and tokens (breaking)</h3><p>Until June, finding pools and tokens meant juggling several endpoints with different parameter names and response shapes: a global pool list, per-network pool lists, a pool filter, a token filter, and a top-tokens ranking. As of June 30 those five are gone, replaced by a unified search family:</p><pre>Removed (now 410 Gone)                        Replacement<br>--------------------------------------       --------------------------------------<br>GET /pools                                    GET /pools/search<br>GET /networks/{network}/pools                 GET /networks/{network}/pools/search<br>GET /networks/{network}/pools/filter          GET /networks/{network}/pools/search<br>GET /networks/{network}/tokens/top            GET /networks/{network}/tokens/search<br>GET /networks/{network}/tokens/filter         GET /networks/{network}/tokens/search</pre><p>The search endpoints do everything the old five did, in one place: rank by volume, liquidity, transactions, FDV or price change, filter by volume, liquidity, transaction count and creation date, and page through results with a cursor. Rows come back under a results array with canonical field names (volume_usd_24h, transactions_24h, liquidity_usd, fdv_usd).</p><p><strong>Try it now</strong> (top Ethereum pools with at least $1M liquidity):</p><pre>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/search?liquidity_usd_min=1000000&amp;order_by=volume_usd_24h&amp;sort=desc&amp;limit=5&quot;</pre><p><strong>If you still call an old path, the API tells you where to go.</strong> Removed endpoints return 410 Gone with a JSON body that names the replacement:</p><pre>{&quot;code&quot;: 410, &quot;message&quot;: &quot;endpoint removed&quot;, &quot;replacement&quot;: &quot;/networks/:network/pools/search&quot;}</pre><p><strong>Your tools are already migrated.</strong> Update to these releases and the change is absorbed for you, with legacy parameter names mapped automatically:</p><ul><li>dexpaprika-mcp <a href="https://www.npmjs.com/package/dexpaprika-mcp">2.1.1 on npm</a>, and the hosted MCP at <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a> (no action needed there)</li><li>dexpaprika-sdk <a href="https://www.npmjs.com/package/dexpaprika-sdk">1.6.1 on npm</a> (TypeScript) and <a href="https://pypi.org/project/dexpaprika-sdk/">0.5.1 on PyPI</a> (Python)</li><li><a href="https://github.com/coinpaprika/dexpaprika-sdk-go">Go SDK v1.5.1</a> and <a href="https://packagist.org/packages/coinpaprika/dexpaprika-sdk">PHP SDK v1.4.0</a></li><li>dexpaprika-cli <a href="https://crates.io/crates/dexpaprika-cli">0.4.1 on crates.io</a></li></ul><p>The SDKs also surface the replacement hint as a typed error, so if a future endpoint is ever deprecated, your code learns the new path from the error itself.</p><p><strong>Migration notes:</strong> the search family paginates with a cursor (has_next_page plus next_cursor) instead of page numbers, and sort fields use the canonical names above. Full parameter reference is in the <a href="https://docs.dexpaprika.com/api-reference/introduction">API docs</a>.</p><h3>New: stream every swap as it happens</h3><p>The Reserve Stream API from May told you when liquidity moved. June adds the other half of the picture: /sse/transactions streams the individual swaps, per pool or per token, over the same SSE infrastructure.</p><p><strong>Try it now</strong> (live swaps on the Uniswap V3 USDC/WETH pool):</p><pre>curl -N &quot;https://streaming.dexpaprika.com/sse/transactions?method=pool&amp;chain=ethereum&amp;address=0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640&quot;</pre><p>Each event is a single swap, with the trade size already converted to dollars on both sides:</p><pre>event: pool<br>data: {&quot;chain&quot;:&quot;ethereum&quot;,&quot;pool_id&quot;:&quot;0x88e6...5640&quot;,&quot;block_number&quot;:&quot;25444452&quot;,<br>       &quot;tx_hash&quot;:&quot;0x093f...5605&quot;,&quot;sender&quot;:&quot;0xbdb3...47b6&quot;,<br>       &quot;amount_0&quot;:29161070863,&quot;amount_1&quot;:-17674162641451120640,<br>       &quot;amount_0_usd&quot;:29184.29,&quot;amount_1_usd&quot;:29185.16,<br>       &quot;price_0_usd&quot;:1.0008,&quot;price_1_usd&quot;:1651.29,&quot;volume_usd&quot;:14589.37}</pre><p>Use method=pool to follow one pool, or method=token to follow every swap involving a token across all its pools. A POST variant multiplexes up to 25 subscriptions over one connection.</p><p><strong>Why this matters:</strong></p><ul><li>Trade-level data used to require polling the transactions endpoint; now it is push-based, block by block</li><li>USD amounts on both legs mean no client-side price joins to figure out trade size</li><li>Combined with /sse/prices and /sse/reserves, you can now watch prices, liquidity and order flow on one stack</li></ul><p><strong>Perfect for:</strong> whale alerts, volume dashboards, execution monitoring, and feeding trading agents that react to flow rather than candles.</p><h3>DexPaprika: fresher numbers everywhere</h3><h4>Prices computed from live trade flow</h4><p>Token prices are now derived continuously from volume-weighted trade data as swaps arrive, instead of on a periodic recalculation cycle, and a smoothing layer stops a single outsized trade from making a price flicker. Aggregate token prices are also better protected against distortion from pools with unreliable pricing, which mainly benefits long-tail tokens. The result on both REST and streaming: fresher, steadier prices, especially on actively traded tokens.</p><p>Pool and token statistics (volumes, transaction counts) got the same treatment and now update continuously as trades land.</p><h4>Cleaner OHLCV, a year back</h4><p>May introduced anomaly filtering for candles; June made it smarter and applied it backwards. Detection now adapts to each token’s own volatility, so genuinely volatile assets are not over-filtered while thin-pool spikes still get caught. The cleanup ran retroactively across roughly the past year of OHLCV history, so charts built on historical candles show fewer bogus wicks.</p><h4>liquidity_usd on pool details</h4><p>GET /networks/{network}/pools/{address} now returns the pool&#39;s total liquidity in USD directly, so you no longer need a second call to get TVL alongside pool details:</p><pre>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640&quot;</pre><h4>New DEXes on Base</h4><p>Hydrex (concentrated liquidity) and Aerodrome Slipstream 2 are now indexed on Base:</p><pre># Top Hydrex pools on Base<br>curl &quot;https://api.dexpaprika.com/networks/base/dexes/hydrex/pools?limit=5&quot;</pre><pre># Top Aerodrome Slipstream 2 pools on Base<br>curl &quot;https://api.dexpaprika.com/networks/base/dexes/aerodrome_slipstream_2/pools?limit=5&quot;</pre><h4>Web app: share-ready charts and honest multi-token pools</h4><ul><li><strong>Copy Chart:</strong> every pool and token chart on dexpaprika.com now has a one-click button that copies a publication-ready PNG, with the pair title, token icons and chain/DEX badges, straight to your clipboard</li><li><strong>Multi-token pools displayed in full:</strong> weighted and multi-asset pools now show their complete token list on the pool page, quick-view drawer and favorites, instead of being squeezed into a two-token pair</li><li><strong>Liquidity shown on every network</strong> in the pools tables and drawers, not just Solana</li><li><strong>Charts backfill more completely</strong> when you scroll into history, with fewer error banners and faster repeat loads</li><li><strong>Shareable tabs and layouts:</strong> the active tab is now part of the URL, and the chart/panel divider remembers your preferred position</li><li><strong>Homepage discovery:</strong> the trending strip gained a 5-minute timeframe and minimum-volume filters ($50K/$100K), and hero stats now show true platform-wide totals</li></ul><h3>CoinPaprika: 15 new DEX market sources</h3><p>CoinPaprika’s market coverage took a big step into DeFi this month. Fifteen new decentralized exchange sources across eleven networks now feed tickers, market listings and volumes:</p><pre>Base        Hydrex, Aerodrome SlipStream 2, Aerodrome SlipStream 3, Alien Base V3<br>Ethereum    SushiSwap V3, Curve TwoCrypto<br>BNB Chain   Thena V3<br>Cronos      VVS V3<br>Sui         Momentum<br>Aptos       Hyperion<br>Sei         Dragonswap V2<br>Sonic       Beets V3<br>HyperEVM    Kittenswap V3, Curve Twocrypto (HyperEVM)<br>Celo        Velodrome SlipStream<br>MegaETH     Prism</pre><p>Tokens trading on these venues are mapped to their contract platforms, so prices and market listings attribute correctly on coin pages and through the API:</p><pre># Hydrex markets on CoinPaprika<br>curl &quot;https://api.coinpaprika.com/v1/exchanges/hydrex/markets&quot;</pre><p><strong>Also this month:</strong></p><ul><li><strong>HTX (formerly Huobi):</strong> the integration migrated to the exchange’s current official API, keeping tickers, market listings and order-book data flowing without interruption under the htx exchange ID. CrateX ticker collection got the same refresh</li><li><strong>Deeper DEX history:</strong> assets that trade mainly on DEXes are getting backfilled minute-level price history, so their charts and historical endpoints no longer start on the day the market was integrated. This is rolling out progressively</li></ul><p>No breaking changes on CoinPaprika this cycle.</p><h3>Availability &amp; rollout</h3><p><strong>DexPaprika:</strong></p><ul><li>The five removed endpoints return 410 Gone as of June 30; the search family is live now</li><li>/sse/transactions is live now, same limits as the other streams (25 subscriptions per POST connection, 10 concurrent SSE streams per IP)</li><li>The legacy /stream price path remains deprecated (since May) and now has a published removal date in 2027; new integrations should use /sse/prices</li><li>liquidity_usd on pool details, the new Base DEXes, and all data-quality improvements are live</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>All 15 DEX sources and the HTX migration are live (<a href="https://coinpaprika.com/exchanges/aerodrome-slipstream-2/">Aerodrome SlipStream 2</a>, <a href="https://coinpaprika.com/exchanges/hydrex/">Hydrex</a>, <a href="https://coinpaprika.com/exchanges/aerodrome-slipstream-3/">Aerodrome SlipStream 3</a>, <a href="https://coinpaprika.com/exchanges/alien-base-v3/">Alien Base V3</a>, <a href="https://coinpaprika.com/exchanges/sushiswap-v3-ethereum/">SushiSwap V3</a>, <a href="https://coinpaprika.com/exchanges/curve-twocrypto/">Curve TwoCrypto</a>, <a href="https://coinpaprika.com/exchanges/thena-v3-bsc/">Thena V3</a>, <a href="https://coinpaprika.com/exchanges/vvs-v3-cronos/">VVS v3</a>, <a href="https://coinpaprika.com/exchanges/momentum/">Momentum</a>, <a href="https://coinpaprika.com/exchanges/hyperion/">Hyperion</a>, <a href="https://coinpaprika.com/exchanges/dragonswap-v2-sei/">DragonSwap v2</a>, <a href="https://coinpaprika.com/exchanges/beets-v3-sonic/">Beets V3</a>, <a href="https://coinpaprika.com/exchanges/kittenswap-v3/">Kittenswap V3</a>, <a href="https://coinpaprika.com/exchanges/curve-twocrypto-hyperevm/">Curve Twocrypto (HyperEVM)</a>, <a href="https://coinpaprika.com/exchanges/velodrome-slipstream-celo/">Velodrome SlipStream</a>, <a href="https://coinpaprika.com/exchanges/prism-megaeth/">Prism</a></li><li>No breaking API changes</li></ul><p><strong>Action needed:</strong> only if you call one of the five removed DexPaprika endpoints directly. Upgrade to the SDK/CLI/MCP versions listed above, or point your code at the search endpoints.</p><h3>Measurable impact</h3><ul><li>DexPaprika now tracks <strong>35 chains, 226 DEX factories, 35.5M pools and 32.9M tokens</strong> (live /stats at the time of writing)</li><li><strong>15 new DEX market sources</strong> on CoinPaprika in a single month</li><li>Roughly <strong>a year of OHLCV history</strong> re-cleaned against price-spike artifacts</li><li>Trade-level data latency drops from polling intervals to <strong>push on block arrival</strong></li></ul><h3>Get started</h3><p><strong>DexPaprika:</strong></p><ul><li>Search endpoints: <a href="https://docs.dexpaprika.com/">docs.dexpaprika.com</a></li><li>Streaming (prices, reserves, and now transactions): <a href="https://docs.dexpaprika.com/streaming/introduction">streaming docs</a></li><li>Agent integrations: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a> and the hosted MCP at <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Explore: <a href="https://docs.coinpaprika.com/">docs.coinpaprika.com</a></li></ul><p><strong>One query to try today</strong> (every swap on a pool, live, with USD sizes):</p><pre>curl -N &quot;https://streaming.dexpaprika.com/sse/transactions?method=pool&amp;chain=ethereum&amp;address=0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640&quot;</pre><h3>Questions?</h3><p>If you’re building on our APIs and have questions about these updates:</p><ul><li>DexPaprika documentation: <a href="https://docs.dexpaprika.com/">https://docs.dexpaprika.com</a></li><li>CoinPaprika documentation: <a href="https://docs.coinpaprika.com/">https://docs.coinpaprika.com</a></li></ul><p><strong>About the author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b81635f337ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/june-2026-product-update-coinpaprika-dexpaprika-b81635f337ba">June 2026 Product Update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[May 2026 Product Update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/may-2026-product-update-coinpaprika-dexpaprika-341a3850c9b0?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/341a3850c9b0</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 12:07:05 GMT</pubDate>
            <atom:updated>2026-06-09T12:07:05.786Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Date:</strong> June 9, 2026 <strong>Author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FuKy-VcHpedfrlig6ni2ZQ.png" /></figure><p>In April, DexPaprika started watching pool reserves and correcting them when they drifted. In May, we took the next step and opened those reserves up as a live stream you can subscribe to. That, plus a rebuilt streaming layer, two new chains, and a brand-new on-site glossary, was the month.</p><h3>TL;DR</h3><p><strong>DexPaprika:</strong></p><ul><li><strong>New: Reserve Stream API</strong> — subscribe to block-level pool and token reserve changes over SSE, with USD-denominated deltas</li><li><strong>Streaming layer rebuilt:</strong> new /sse/prices and /sse/reserves paths, heartbeat pings, request IDs, clearer errors. The legacy /stream path is now deprecated (still works, emits a warning)</li><li><strong>JS precision fix:</strong> streaming numbers are now sent as strings, so large values no longer lose precision in JavaScript clients</li><li><strong>New chains:</strong> Celo and MegaETH</li><li><strong>New DEXs:</strong> Hyperion (Aptos), Prism (MegaETH), Sushiswap V3 (Ethereum), Aerodrome Slipstream V3 (Base), Velodrome Slipstream (Celo)</li><li><strong>Cleaner market data:</strong> OHLCV and 24h high/low now exclude detected price spikes, on both REST and streaming</li><li>Reserve tracking extended to more AMM protocols</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Four new exchanges: WEEX, Dexomy, Ourbit, KCEX</li><li>Redesigned price calculator / converter, backed by a new converter API</li><li>Reliability: no more 500s on coins with retired platforms or cold caches; smarter fiat-rate fallback</li><li>Faster coin and converter pages</li><li>No breaking API changes</li></ul><h3>The headline: a new Reserve Stream API</h3><p>This is the most important update of the month. In April, DexPaprika made its pool-reserve data accurate behind the scenes; in May, we opened it up as a live stream. You can now subscribe to pool and token reserve updates over Server-Sent Events, block by block, with USD-denominated deltas attached.</p><p>Two subscription modes:</p><ul><li>pool_reserves follows a single pool — an event every time that pool&#39;s reserves change.</li><li>token_reserves follows one token across every pool that contains it.</li></ul><p>Each event carries the new reserve, the delta since the last update, the USD value of both, and the block it landed on.</p><p><strong>Try it now</strong> (live WETH reserve changes on Ethereum, one event then close):</p><pre>curl -N &quot;https://streaming.dexpaprika.com/sse/reserves?method=token_reserves&amp;chain=ethereum&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&amp;limit=1&quot;</pre><p>You get back something like:</p><pre>event: token_reserves<br>data: {&quot;chain&quot;:&quot;ethereum&quot;,&quot;token_id&quot;:&quot;0xc02aaa39...&quot;,&quot;reserve&quot;:&quot;317053665553816373018387&quot;,&quot;delta&quot;:&quot;61105506774448689456&quot;,&quot;price_usd&quot;:1680.13,&quot;reserve_usd&quot;:532691824.29,&quot;delta_usd&quot;:102665.28,&quot;block&quot;:&quot;25278469&quot;,...}</pre><p>Or follow a single pool:</p><pre># Uniswap V3 USDC/WETH 0.05% pool on Ethereum<br>curl -N &quot;https://streaming.dexpaprika.com/sse/reserves?method=pool_reserves&amp;chain=ethereum&amp;address=0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640&amp;limit=5&quot;</pre><p>A POST /sse/reserves variant multiplexes up to 25 pools and tokens over one connection, so you can watch a whole basket without opening 25 sockets.</p><p><strong>Why this matters:</strong> liquidity depth, price-impact, and TVL changes used to require polling pool endpoints on a loop. Now you can react to a reserve move the moment the block lands — with USD deltas already attached, so you don’t have to price the reserve yourself.</p><p><strong>Perfect for:</strong> depth and TVL dashboards, slippage and price-impact estimators, liquidity-drain alerting, and agents that need to know the moment a pool gets thin.</p><h3>How this builds on April</h3><p>If you read <a href="https://medium.com/coinpaprika/april-2026-product-update-coinpaprika-dexpaprika-7172f44d9abd">last month’s update</a>, the throughline is clear. April was about reserve <em>accuracy</em>: DexPaprika began monitoring 20 AMM protocols for reserve drift and silently resyncing pools that fell out of line. That work lived entirely behind the scenes, making depth and price-impact numbers truer without you having to do anything.</p><p>May exposes that same reserve data as something you can consume directly. The drift-corrected reserves April produced are now streamable in real time. April built the accurate state; May lets you subscribe to it.</p><p>The web app story carries over too. April shipped the redesign and hit Level 5 Agent-Native. May filled it in with a glossary, a global cross-chain homepage, and search you can actually filter.</p><h3>DexPaprika</h3><h3>Streaming layer, rebuilt</h3><p>The whole streaming surface got an overhaul this month, and it changes how you connect.</p><p><strong>New paths.</strong> Token prices now live at GET /sse/prices; reserves at GET /sse/reserves. The old /stream path is <strong>deprecated</strong>. It still works, but on connect it now emits a one-shot warning event telling you to migrate. New integrations should target the /sse/* paths directly.</p><pre># New price stream path<br>curl -N &quot;https://streaming.dexpaprika.com/sse/prices?method=token_price&amp;chain=ethereum&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&amp;limit=1&quot;</pre><p><strong>Heartbeats.</strong> Streams now send periodic ping events so you (and any proxy in between) can tell a quiet connection apart from a dead one. No more guessing whether a silent stream is idle or broken.</p><p><strong>JavaScript precision fix.</strong> Numbers in streaming payloads are now encoded as strings. JavaScript’s native number type silently mangles large integers, so a raw numeric reserve or timestamp could come back subtly wrong in the browser. Sending them as strings means the value you parse is the value we sent. You can see it in the response above — &quot;price&quot;:&quot;1680.48981448952&quot; comes back quoted.</p><p><strong>Request IDs and clearer errors.</strong> Each request now carries an ID through the stream, and the endpoints return proper 4XX codes with readable messages on bad input instead of failing opaquely.</p><h3>New chains: Celo and MegaETH</h3><p>Two new chains are live and free to query.</p><pre># Top Velodrome Slipstream pools on Celo<br>curl &quot;https://api.dexpaprika.com/networks/celo/dexes/velodrome_slipstream/pools?limit=5&quot;</pre><pre># Top Prism pools on MegaETH<br>curl &quot;https://api.dexpaprika.com/networks/megaeth/dexes/prism/pools?limit=5&quot;</pre><h3>New DEXs across five chains</h3><p>Beyond the new chains, May added protocol coverage on chains we already index:</p><ul><li><strong>Hyperion</strong> on Aptos</li><li><strong>Sushiswap V3</strong> on Ethereum</li><li><strong>Aerodrome Slipstream V3</strong> on Base</li><li><strong>Velodrome Slipstream</strong> on Celo</li><li><strong>Prism</strong> on MegaETH</li></ul><pre># Hyperion pools on Aptos<br>curl &quot;https://api.dexpaprika.com/networks/aptos/dexes/hyperion/pools?limit=5&quot;</pre><pre># Sushiswap V3 pools on Ethereum<br>curl &quot;https://api.dexpaprika.com/networks/ethereum/dexes/sushiswap_v3/pools?limit=5&quot;</pre><p>Reserve tracking was also extended to more protocols this month (Balancer V3, Curve, Equalizer, Algebra, Uniswap V2, and the new Slipstream pools among them), continuing the accuracy work from April.</p><h3>Cleaner market data: anomaly filtering</h3><p>Tiny-liquidity tokens occasionally print a single wild candle — a one-off trade at an absurd price that shows up as a spike on the chart and skews the 24h high/low. DexPaprika now detects those outliers and excludes them from OHLCV responses and 24h high/low figures.</p><p>This applies on <strong>both REST and the streaming candle feed</strong>. The result is fewer phantom spikes on charts and more trustworthy daily ranges, especially for long-tail tokens. You don’t need to change anything — clean data is the default now.</p><h3>Pool listing: use the per-network endpoints</h3><p>The old global /pools listing endpoint now returns 410 Gone. Pool lists are served per network — query /networks/{chain}/pools (optionally scoped to a DEX with /networks/{chain}/dexes/{dex}/pools) instead. Per-network pool listing supports order_by and sort, so you can pull, say, the top pools on a chain by volume in one call.</p><pre># Top Ethereum pools by 24h volume<br>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools?order_by=volume_usd&amp;sort=desc&amp;limit=10&quot;</pre><h3>Web app: glossary, global homepage, better search</h3><p>The DexPaprika web app picked up where April’s redesign left off.</p><ul><li><strong>A new glossary.</strong> Every DEX and market term we use — liquidity, FDV, volume, order book, and dozens more — now has a plain-language definition at <a href="https://dexpaprika.com/glossary">dexpaprika.com/glossary</a>, with the stats on token and pool pages linking straight to the relevant entry. It’s also exposed in a markdown-friendly form for agents.</li><li><strong>Global, cross-chain homepage.</strong> The homepage and the new /tokens pages now show pools and tokens across all chains by default, with chain and DEX badges on each row, instead of defaulting to a single chain.</li><li><strong>Filterable command-palette search.</strong> Search now lets you filter by result type (tokens, pools, DEXs) so you land on what you meant faster.</li><li><strong>Watchlist and chart fixes.</strong> A watchlist card on the homepage opens your favorites in the sidebar, and the price chart got fixes for tiny sub-cent prices, very high prices, and a misleading volume label.</li></ul><h3>CoinPaprika</h3><h3>Four new exchanges</h3><p>Four centralized exchanges were integrated this month: <strong>WEEX</strong>, <strong>Dexomy</strong>, <strong>Ourbit</strong>, and <strong>KCEX</strong>. Their tickers and market data now flow through the standard CoinPaprika endpoints.</p><pre># WEEX exchange detail<br>curl &quot;https://api.coinpaprika.com/v1/exchanges/weex&quot;</pre><p>If you list exchanges or pull per-coin market breakdowns, the new sources appear automatically on the next refresh.</p><h3>Redesigned price calculator</h3><p>The price calculator / converter on CoinPaprika.com was rebuilt on a new converter API, with a cleaner layout and a redesigned currency dropdown. The page is faster and easier to use, and the underlying converter API is what powers the new experience.</p><h3>Reliability fixes</h3><p>A few quiet fixes that remove failure modes partners and integrators were hitting:</p><ul><li><strong>No more </strong><strong>500s on retired platforms.</strong> Requesting a coin whose underlying platform had been removed used to throw a server error. It now skips the dead platform and returns the coin cleanly.</li><li><strong>Cold caches return data, not errors.</strong> A freshly-warmed-but-empty cache is now treated as loaded, so endpoints return empty results instead of a 500 during that window.</li><li><strong>Smarter fiat fallback.</strong> Before the day’s fiat rates publish (early UTC morning), conversions now fall back to the previous day’s rate instead of coming back without one.</li></ul><h3>Faster pages</h3><p>Coin pages and the converter page got a load-time pass. Less to download, quicker first render — same data, less waiting.</p><h3>Availability &amp; rollout</h3><p><strong>DexPaprika:</strong></p><ul><li>Reserve Stream API (/sse/reserves, GET and POST): live</li><li>New streaming paths (/sse/prices, /sse/reserves) with heartbeats, request IDs, string-encoded numbers: live</li><li>Legacy /stream path: <strong>deprecated</strong>, still functional, emits a migration warning on connect</li><li>Celo and MegaETH chains: live and queryable</li><li>New DEXs (Hyperion, Prism, Sushiswap V3, Aerodrome Slipstream V3, Velodrome Slipstream): live</li><li>OHLCV / 24h high-low anomaly filtering: live on REST and streaming</li><li>Global /pools listing: <strong>now returns </strong><strong>410 Gone</strong> — migrate to /networks/{chain}/pools</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>WEEX, Dexomy, Ourbit, KCEX: live, indexing on the standard refresh cycle</li><li>Redesigned calculator + new converter API: live on CoinPaprika.com</li><li>Reliability fixes (retired platforms, cold caches, fiat fallback): live in production</li></ul><p><strong>Heads-up on deprecations:</strong> the legacy streaming /stream path and the global /pools endpoint are both on the way out. If you use either, plan a migration — /stream to /sse/prices, and /pools to the per-network pool endpoints.</p><h3>Measurable impact</h3><p><strong>DexPaprika:</strong></p><ul><li>Reserve data went from internal-only (April) to a <strong>public real-time stream</strong> (May)</li><li>One streaming connection can now follow <strong>up to 25</strong> pools and tokens at once</li><li>Two new chains and five new DEXs added to free coverage</li><li>Anomaly filtering removes phantom spikes from OHLCV and 24h ranges across REST and streaming</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Four new exchange data sources</li></ul><h3>Get started</h3><p><strong>DexPaprika:</strong></p><ul><li>Reserve stream: curl -N &quot;https://streaming.dexpaprika.com/sse/reserves?method=token_reserves&amp;chain=ethereum&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&amp;limit=1&quot;</li><li>Price stream: curl -N &quot;https://streaming.dexpaprika.com/sse/prices?method=token_price&amp;chain=ethereum&amp;address=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&amp;limit=1&quot;</li><li>New chains: curl &quot;https://api.dexpaprika.com/networks/celo/pools?limit=10&quot;</li><li>Explore: <a href="https://dexpaprika.com/">dexpaprika.com</a></li><li>Docs: <a href="https://docs.dexpaprika.com/">docs.dexpaprika.com</a></li><li>Agent onboarding: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a></li><li>Hosted MCP server: <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a></li><li>On-site glossary: <a href="https://dexpaprika.com/glossary">dexpaprika.com/glossary</a></li><li>Prefer a client library? <a href="https://github.com/coinpaprika/dexpaprika-sdk-python">Python SDK</a>, <a href="https://github.com/coinpaprika/dexpaprika-cli">CLI</a>, and <a href="https://github.com/coinpaprika">everything else on GitHub</a></li></ul><p><strong>CoinPaprika:</strong></p><ul><li>New exchanges: curl &quot;https://api.coinpaprika.com/v1/exchanges/weex&quot;</li><li>Explore: <a href="https://coinpaprika.com/">coinpaprika.com</a></li><li>Docs: <a href="https://docs.coinpaprika.com/">docs.coinpaprika.com</a></li><li>Client libraries: <a href="https://github.com/coinpaprika/coinpaprika-api-nodejs-client">Node.js</a> and <a href="https://github.com/coinpaprika/coinpaprika-api-python-client">Python</a> clients on GitHub</li></ul><h3>Questions?</h3><p>If you’re building on our APIs and have questions about these updates:</p><ul><li>DexPaprika docs: <a href="https://docs.dexpaprika.com/">docs.dexpaprika.com</a></li><li>CoinPaprika docs: <a href="https://docs.coinpaprika.com/">docs.coinpaprika.com</a></li><li>Agent onboarding: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a></li><li>Last month’s changelog: <a href="https://medium.com/coinpaprika/april-2026-product-update-coinpaprika-dexpaprika-7172f44d9abd">April 2026 Product Update</a></li></ul><p><strong>About the author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=341a3850c9b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/may-2026-product-update-coinpaprika-dexpaprika-341a3850c9b0">May 2026 Product Update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[April 2026 Product Update: CoinPaprika & DexPaprika]]></title>
            <link>https://medium.com/coinpaprika/april-2026-product-update-coinpaprika-dexpaprika-7172f44d9abd?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/7172f44d9abd</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Thu, 07 May 2026 07:31:04 GMT</pubDate>
            <atom:updated>2026-05-07T09:30:50.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXFmr4NYXA7jkaj1IpI5Tw.png" /></figure><p><strong>Date:</strong> May 1, 2026 <strong>Author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika</p><p>April was the month <a href="https://dexpaprika.com/">DexPaprika</a> took pool-reserve accuracy seriously, added Cronos and Manifest to its coverage, and shipped a redesigned web app that scores Level 5 Agent-Native on Cloudflare’s new agent-readiness scanner.</p><h3>TL;DR</h3><p><a href="https://coinpaprika.com/"><strong>CoinPaprika</strong></a><strong>:</strong></p><ul><li>Two new exchange integrations: Manifest (Solana, via DexPaprika) and Cexius</li><li>Nexo “quick action” buttons added on coin pages</li><li>Streaming clients now get an explicit 400 (not 500) on failed WebSocket upgrades</li><li>No breaking API changes</li></ul><p><strong>DexPaprika:</strong></p><ul><li>New blockchain: <strong>Cronos</strong> (CRO native asset + VVS V3 DEX)</li><li>New DEX on Solana: <strong>Manifest</strong></li><li><strong>Sui</strong> protocol upgraded to v2</li><li>New API capability: <strong>time-range filters on swap and transaction queries</strong> (from, to params)</li><li>Pool reserves now self-correct across 20 AMM protocols when drift exceeds threshold</li><li>Web app redesigned and now scores <strong>13/13 Level 5 Agent-Native</strong> on isitagentready.com —<a href="https://medium.com/coinpaprika/from-4-13-to-13-13-in-a-week-how-we-made-dexpaprika-agent-ready-640a473710d8"> read how we did it here</a></li><li>No breaking API changes</li></ul><h3>CoinPaprika</h3><h3>New exchange integrations</h3><ul><li><strong>Manifest (Solana).</strong> Manifest order-book trading data on Solana is now part of CoinPaprika’s market coverage, sourced via DexPaprika. Spot orderbook data and pricing flow through the standard /exchanges and /coins/{id}/exchanges endpoints.</li><li><strong>Cexius.</strong> A new centralized exchange added through the YAML exchange skill, with order book and ticker data pulled into CoinPaprika.</li></ul><p>If you query exchange listings for Solana-native trading or for newly-onboarded CEX coverage, both should appear in the next refresh cycle.</p><h3>Nexo on coin action buttons</h3><p>Coin pages on CoinPaprika.com now show <a href="https://nexo.com/?utm_source=aff_coinpaprika&amp;utm_campaign=aff_coinpaprika_button_earn_desktop_website"><strong>Nexo</strong></a> as one of the partner quick-action buttons (alongside the existing providers). Useful for partners building affiliate flows or comparing yield offerings inline with token detail.</p><h3>Streaming: clearer WebSocket failures</h3><p>The streaming layer used to return HTTP 500 when a WebSocket upgrade failed, which made it hard to tell whether the failure was a client mistake or a server problem. It now returns 400 for upgrade-handshake failures, so client libraries can branch correctly.</p><h3>DexPaprika</h3><h3>Blockchain expansion: Cronos</h3><p>Cronos is now a first-class chain on DexPaprika. Three things landed together:</p><ul><li>WCRO is supported as a quote token and as a CoinPaprika asset</li><li>CronosChainID is in the supported chains list</li><li>VVS V3is integrated as a DEX, with reserves and pool data flowing through the standard endpoints</li></ul><pre># List VVS V3 DEX pools<br>curl &quot;https://api.dexpaprika.com/networks/cronos/dexes/vvs_v3/pools?limit=5&quot;</pre><p>If you’ve been waiting on Cronos for an aggregator or analytics tool, it’s live now and free to query.</p><h3>New DEX on Solana: Manifest</h3><p>Manifest is a hybrid orderbook DEX on Solana. April added a dedicated processor, swap parser, and metadata fetcher for it, plus support for Manifest’s optional-owner instruction in the on-chain decoder.</p><pre># Top Manifest pools by volume<br>curl &quot;https://api.dexpaprika.com/networks/solana/dexes/manifest/pools?order_by=volume_usd&amp;limit=10&quot;</pre><h3>Sui v2 protocol upgrade</h3><p>DexPaprika’s Sui integration was upgraded to v2 of the protocol. It took two attempts to land cleanly (the first PR was reverted twice while edge cases were sorted), but the v2 path is now stable.</p><h3>Velodrome V2 and Trader Joe V2 added to reserve monitoring</h3><p>Velodrome V2 (Optimism / Base) and Trader Joe V2 (Avalanche) are now first-class participants in the reserve resync system. If their on-chain reserves drift from DexPaprika’s cached state, the system catches and corrects it.</p><h3>API: time-range filters on swap and transaction queries</h3><p>Probably the most agent-friendly change of the month. Swap and transaction endpoints now accept from and to parameters (Unix timestamps), so you can pull a clean window of trade history without paging through everything since launch.</p><pre># All swaps on a Uniswap V3 pool between two timestamps<br>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/transactions?from=1714521600&amp;to=1714608000&amp;limit=100&quot;</pre><p>This is the kind of thing that turns “pull recent activity” into one HTTP call instead of a paginated loop. Good for backtests, trade monitors, agent workflows.</p><h3>Pool reserve accuracy: self-healing across 20 protocols</h3><p>Background: pool reserves on AMMs occasionally drift between what the DEX reports on-chain and what an indexer like DexPaprika has cached. Drift means stale price-impact and depth calculations.</p><p>April shipped a system that monitors drift and automatically resyncs pools whose reserves move outside an acceptable window.</p><ul><li>Aerodrome, Aerodrome V3, Algebra, Balancer V2, Balancer V3, Curve, Equalizer, KyberSwap, Lynex, Maverick V2, PancakeSwap V3, QuickSwap V3, SunSwap V3, SwapBased V3, SyncSwap V2, Thena V3, Thruster V3, Trader Joe V2, UniswapV2, Velodrome V2</li></ul><p>If you build market-depth charts, route quotes, or anything that relies on accurate pool state, this is the change that quietly makes those numbers truer.</p><h3>Solana token metadata: better fetching, fewer broken tokens</h3><p>A wave of fixes targeted Solana token metadata:</p><ul><li>Concurrent metadata retrieval with bounded goroutines</li><li>URI validation that catches invalid metadata before it hits the database</li><li>Permanent vs transient HTTP error distinction (so a temporary RPC blip doesn’t poison a token’s record)</li><li>Reimport path for SPL tokens that previously failed because of unsupported token-2022 extensions</li></ul><p>Net effect: more Solana tokens render with correct names, symbols, and logos, and fewer ghost tokens with missing fields.</p><h3>Other fixes worth naming</h3><ul><li><strong>OHLCV decimals</strong>: rounding to storage precision before validation eliminates a class of zero-price candles that occasionally appeared on tiny-decimal tokens</li><li><strong>SOL → WSOL handling</strong>: the swap parser no longer double-converts SOL to WSOL on Solana DEXes, fixing a subtle inconsistency in pair creation</li><li><strong>Cache safety</strong>: stale reads during background flushes are blocked, removing an edge case where a freshly-written value could be served as old</li></ul><h3>Web app: redesign + agent-readiness</h3><p>The DexPaprika web app finished a multi-week redesign focused on three goals: faster mobile, cleaner pool/token detail layout, and full agent-readiness.</p><ul><li><strong>Level 5 Agent-Native (13/13)</strong> on Cloudflare’s <a href="https://isitagentready.com/">isitagentready.com</a> scanner across <a href="https://dexpaprika.com/">dexpaprika.com</a>, <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a>, and <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a>. Full case study: <a href="https://medium.com/coinpaprika/from-4-13-to-13-13-in-a-week-how-we-made-dexpaprika-agent-ready-640a473710d8">Four site archetypes for agent-ready APIs</a></li><li>Pool and token detail pages restructured: bigger charts, cleaner tabs, smarter right-drawer</li><li>Mobile UX overhaul: pagination compacted, command palette polished, chart range selector tightened</li><li>Trading View / streaming view rethemed to match the new design system</li><li>Watchlist and chart-data fixes (issues #176, #177, #179)</li></ul><h3>Highlighted feature: time-range filters on transactions</h3><p>If you’ve been building anything that needs a slice of swap or transaction history (a backtester, a wallet activity monitor, an alerting bot, an agent that summarizes “what happened in this pool yesterday”), this is the call that makes it a one-shot:</p><p><strong>Try it now (Uniswap V3 USDC/ETH 0.05% pool, last 24 hours):</strong></p><pre>NOW=$(date +%s)<br>DAY_AGO=$((NOW - 86400))<br>curl &quot;https://api.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/transactions?from=$DAY_AGO&amp;to=$NOW&amp;limit=200&quot;</pre><p><strong>Why this matters:</strong></p><ul><li>Cuts out paginated walks for fixed time windows</li><li>Plays well with cron-driven jobs and agent task loops</li><li>Makes “show me all trades on pool X between time A and time B” a single HTTP call</li><li>No API key, no rate-limit changes, free as always</li></ul><p><strong>Perfect for:</strong> trade monitors, alerting bots, backtest pipelines, agent workflows, treasury dashboards.</p><h3>Availability &amp; rollout</h3><p><strong>CoinPaprika:</strong></p><ul><li>Manifest and Cexius integrations: live now, indexing on the standard refresh cycle</li><li>Nexo action buttons: live on coin pages</li><li>WebSocket streaming 400 response: live in production</li></ul><p><strong>DexPaprika:</strong></p><ul><li>Cronos (chain + WCRO + VVS V3 DEX): live, queryable via the standard endpoints</li><li>Manifest DEX on Solana: live</li><li>Sui v2: live and stable</li><li>Time-range filters on swaps/transactions: live, no flag required, additive</li><li>Reserve drift monitoring across 20 protocols: live</li><li>Web app redesign + agent-readiness: live across <a href="https://dexpaprika.com/">dexpaprika.com</a>, <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a>, and <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a></li></ul><p><strong>No breaking API changes</strong> to either CoinPaprika or DexPaprika this cycle.</p><h3>Measurable impact</h3><p><strong>DexPaprika:</strong></p><ul><li>Pool reserve now auto-correct on drift across <strong>20 AMM protocols</strong> (was tracked-but-not-corrected before)</li><li>Window queries reduce a typical “last 24h of trades” from a paginated walk to a <strong>single HTTP call</strong></li><li>Solana metadata fetching is now bounded-concurrent with proper error categorization (fewer ghost tokens with empty fields)</li><li>Three DexPaprika web surfaces hit <strong>Level 5 / 13/13</strong> on Cloudflare’s agent-readiness scanner. For comparison the scanner’s own homepage scores 10/13 and Cloudflare’s developer docs score 7/13.</li></ul><p><strong>CoinPaprika:</strong></p><ul><li>Two new exchange data sources added (Manifest, Cexius)</li><li>Streaming clients can now distinguish bad-handshake (400) from server failure (500)</li></ul><p><strong>Overall:</strong></p><ul><li>Cronos partners and aggregators can now treat DexPaprika as a primary data source on that chain</li><li>Sui v2 unblocks integrators waiting for the upgraded protocol</li><li>Time-range filters cut HTTP volume for any consumer doing windowed analysis</li></ul><h3>Get started</h3><p><strong>CoinPaprika:</strong></p><ul><li>Browse the new exchanges: curl &quot;https://api.coinpaprika.com/v1/exchanges&quot;</li><li>Docs: <a href="https://docs.coinpaprika.com/">docs.coinpaprika.com</a></li></ul><p><strong>DexPaprika:</strong></p><ul><li>Cronos pools: curl &quot;https://api.dexpaprika.com/networks/cronos/pools?limit=10&quot;</li><li>Manifest pools on Solana: curl &quot;https://api.dexpaprika.com/networks/solana/dexes/manifest/pools?limit=10&quot;</li><li>Docs: <a href="https://docs.dexpaprika.com/">docs.dexpaprika.com</a></li><li>Agent onboarding: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a></li><li>Hosted MCP server: <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a></li></ul><p><strong>Example: pull a Cronos pool’s last 24 hours of swaps:</strong></p><pre>NOW=$(date +%s); DAY_AGO=$((NOW - 86400))<br>POOL=&quot;&lt;replace-with-cronos-pool-address&gt;&quot;<br>curl &quot;https://api.dexpaprika.com/networks/cronos/pools/$POOL/transactions?from=$DAY_AGO&amp;to=$NOW&amp;limit=100&quot;</pre><h3>Questions?</h3><p>If you’re building on our APIs and have questions about these updates:</p><ul><li>DexPaprika docs: <a href="https://docs.dexpaprika.com/">docs.dexpaprika.com</a></li><li>CoinPaprika docs: <a href="https://docs.coinpaprika.com/">docs.coinpaprika.com</a></li><li>Agent onboarding: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a></li><li>Last month’s changelog: <a href="https://medium.com/coinpaprika/march-2026-product-update-coinpaprika-dexpaprika-ba63df779fa4">March 2026 Product Update</a></li><li>Agent-readiness case study: <a href="https://medium.com/coinpaprika/from-4-13-to-13-13-in-a-week-how-we-made-dexpaprika-agent-ready-640a473710d8">Four site archetypes for agent-ready APIs</a></li></ul><p><strong>About the author:</strong> Mateusz Sroka, Lead Developer Advocate at CoinPaprika &amp; DexPaprika.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7172f44d9abd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/april-2026-product-update-coinpaprika-dexpaprika-7172f44d9abd">April 2026 Product Update: CoinPaprika &amp; DexPaprika</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four site archetypes for agent-ready APIs]]></title>
            <link>https://medium.com/coinpaprika/from-4-13-to-13-13-in-a-week-how-we-made-dexpaprika-agent-ready-640a473710d8?source=rss-d64356972b83------2</link>
            <guid isPermaLink="false">https://medium.com/p/640a473710d8</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Mateusz Sroka]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 09:11:05 GMT</pubDate>
            <atom:updated>2026-04-23T12:52:11.869Z</atom:updated>
            <content:encoded><![CDATA[<h3>A case study in WebMCP, A2A agent cards, OpenAPI discovery, and the decisions the checklist doesn’t make for you.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfIG28O10H5tVNSQk83fqQ.png" /></figure><h3>TL;DR</h3><ul><li><strong>Three DexPaprika subdomains now score 13/13 Level 5 Agent-Native</strong> on Cloudflare’s new <a href="https://isitagentready.com/">isitagentready.com</a> scanner. Cloudflare’s own docs score 7/13. The scanner’s homepage scores 10/13.</li><li><strong>Two engineers took opposite WebMCP approaches</strong> on adjacent surfaces and both hit 13/13. One wrote 15 lines of JavaScript. The other wrote 107 HTML attributes. The collision produced a framework.</li><li><strong>Four site archetypes decide which tools to expose</strong>: site-as-UI, site-as-API, site-as-MCP, site-as-directory. Each archetype gets a different WebMCP style, a different agent card, a different set of discovery files.</li><li><strong>The audit that the scanner forced was the real payoff.</strong> Cleaning up metadata is cheap. The thinking it forces about which surfaces do what — and auditing your stack against the answer — is the thing worth the time.</li></ul><p>Two engineers on our team shipped the same agent-readiness checklist on adjacent subdomains. One wrote 15 lines of JavaScript. The other wrote 107 HTML attributes. Both passed every check. Neither was wrong. That’s the thing the checklist doesn’t tell you: which tools should each surface actually expose?</p><p>The model we landed on has four archetypes. A <strong>site-as-UI</strong> (our product dashboard) exposes UI actions tagged on DOM elements. A <strong>site-as-API</strong> (our REST endpoints) exposes its schema. A <strong>site-as-MCP</strong> (our hosted MCP server) exposes the MCP protocol itself. A <strong>site-as-directory</strong> (our agent onboarding hub) exposes meta-tools and cross-surface links. Different surfaces, different tools, same score.</p><h3>Baseline</h3><p>Cloudflare shipped a scanner that grades sites on 13 open standards for AI-agent discoverability: RFC 8288 Link headers, RFC 9727 API catalogs, MCP server cards, WebMCP, Content Signals, A2A agent cards, OAuth discovery, and more. Levels run 0 “Not Ready” to 5 “Agent-Native.” Nobody is at Level 5.</p><p>I ran it against DexPaprika and got this:</p><pre>dexpaprika.com          Level 1    3/13<br>agents.dexpaprika.com   Level 0    0/13<br>mcp.dexpaprika.com      Level 0    0/13</pre><p>Three out of thirteen on the main marketing site. Zero out of thirteen on the subdomain literally called agents.dexpaprika.com. DexPaprika&#39;s pitch is free data for AI agents with no API key required, and we were scoring Level 1 on a scanner that measures exactly that claim.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jRG12QVaJUpBY3rqxKOx-w.png" /></figure><h3>First attempt, on a Cloudflare Worker</h3><p>I started with <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a>, a Vite + React site fronted by a Cloudflare Worker. The Worker already did markdown negotiation (serving text/markdown when asked for it), which was one of the 13 checks we passed from day one. For everything else, I wrote a route handler for each discovery file and dropped the JSON into TypeScript constants.</p><pre>// Worker&#39;s fetch handler: new switch at the top of the request path<br>switch (url.pathname) {<br>  case &quot;/robots.txt&quot;:<br>    return textResponse(ROBOTS_TXT);<br>  case &quot;/.well-known/api-catalog&quot;:<br>    return jsonResponse(API_CATALOG, &quot;application/linkset+json&quot;);<br>  case &quot;/.well-known/mcp/server-card.json&quot;:<br>    return jsonResponse(MCP_SERVER_CARD);<br>  case &quot;/.well-known/agent-skills/index.json&quot;:<br>    return jsonResponse(AGENT_SKILLS_INDEX);<br>  case &quot;/.well-known/agent-card.json&quot;:<br>    return jsonResponse(A2A_AGENT_CARD);<br>  // …OAuth stubs, alias paths, etc<br>}</pre><p>First deploy: Level 4, 9/13 passing. Three more iterations to reach 13/13. Each iteration surfaced a real gap.</p><h3>Four spec gotchas that cost me three deploys</h3><p><strong>1. A2A agent card path.</strong> I assumed /.well-known/a2a/agent-card.json based on an earlier spec draft. The scanner expects /.well-known/agent-card.json without the subfolder. Both paths exist on our Worker now for compatibility across client vintages.</p><blockquote><em>Check: serve both paths. Old clients and new ones will ask for different ones for a while.</em></blockquote><p><strong>2. OAuth protected resource origin mismatch.</strong> RFC 9728 specifies that the resource field must match the origin hosting the metadata. I had written &quot;resource&quot;: &quot;https://api.dexpaprika.com&quot; in a file served from agents.dexpaprika.com. Scanner flagged it correctly.</p><blockquote><em>Check: does your </em><em>resource field match the origin serving the file, not the API it describes? They&#39;re usually different.</em></blockquote><p><strong>3. A2A card schema.</strong> Each skill entry needs an id field, not just a name. The card itself needs supportedInterfaces, not interfaces. I&#39;d copied the shape from an older draft. Scanner validates against the current one.</p><blockquote><em>Check: validate against the current A2A schema, not blog posts or earlier drafts. Field names changed during the spec’s evolution.</em></blockquote><p><strong>4. OAuth discovery as a no-op.</strong> A public API has no auth server to advertise. My first attempt simply omitted /.well-known/openid-configuration and /.well-known/oauth-authorization-server entirely. Scanner marked both failed. Turns out a minimal RFC 8414 document with empty arrays for grant_types_supported, response_types_supported, and scopes_supported is valid metadata that truthfully declares &quot;no flows supported.&quot;</p><blockquote><em>Check: “no auth” is not the same as “no metadata.” Publish an honest empty document rather than omitting the file.</em></blockquote><p>Four iterations, 13/13. I then applied the same Worker template to our <a href="https://mcp.dexpaprika.com/">hosted MCP server at mcp.dexpaprika.com</a> and hit 13/13 on the first deploy. Templates carried over cleanly.</p><h3>Then our frontend dev shipped dexpaprika.com</h3><p>The main marketing site wasn’t ours to fix directly. I filed a four-ticket epic for the frontend team with exact JSON contents, expected URLs, and RFC references. A week later the scanner reported Level 5, 13/13 PASS on <a href="https://dexpaprika.com/">dexpaprika.com, the DexPaprika product dashboard</a>.</p><p>I audited the implementation to check that it matched the ticket. Some of it did. Several things went past the ticket.</p><h3>The argument I lost</h3><p>My ticket told the dev to skip publishing /openapi.json. My reasoning was descriptive: Stripe doesn&#39;t publish OpenAPI at a well-known path, GitHub doesn&#39;t, CoinGecko doesn&#39;t, so we shouldn&#39;t either.</p><p>The dev published it anyway. Linked from the Link header as service-desc with application/openapi+json content-type. Their call was correct.</p><p>RFC 9727’s service-desc relation genuinely wants a machine-readable spec. Agents benefit from being able to fetch and parse the schema directly. My &quot;industry norm&quot; argument was an observation about what other APIs do, not an argument for <em>why</em> they do it. Describing what others do is a bad reason to skip something useful.</p><h3>The WebMCP collision</h3><p>The scanner counted 107 tools on dexpaprika.com and 15 on agents.dexpaprika.com. The honest number on dexpaprika.com is 9 — one of them is a favorite button repeated across every row of the pool table, and the scanner counts each tool-name attribute occurrence. The other implementation has 15 genuinely distinct REST endpoints. Both are legitimate. They measure different things.</p><p>The WebMCP check looks for navigator.modelContext.registerTool() calls on page load. On agents.dexpaprika.com I had written a standalone JavaScript file with 15 tool registrations, one per public DexPaprika REST endpoint. Drop-in, self-contained, ~20 KB.</p><pre>navigator.modelContext.registerTool({<br>  name: &quot;dexpaprika_getTokenDetails&quot;,<br>  description: &quot;Get token metadata and summary metrics...&quot;,<br>  inputSchema: { /* JSON Schema */ },<br>  execute: async ({ network, token_address }) =&gt; {<br>    const r = await fetch(<br>      `https://api.dexpaprika.com/networks/${network}/tokens/${token_address}`<br>    );<br>    return r.json();<br>  },<br>});<br>// ...14 more</pre><p>Our dev didn’t do that. They added tool-name=&quot;...&quot; attributes directly to existing DOM elements: the star button on each pool row, the search form, the network selector, the hamburger menu.</p><p>Both approaches are valid. They expose different things:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNVRD09Qb4APIahcVk6XUQ.png" /></figure><p>The dev made the right choice for dexpaprika.com, which is a product UI where the value is the interface. I made the right choice for agents.dexpaprika.com, which is an agent-facing subdomain where the backing service is a REST API.</p><p>Different surfaces. Different tools. Same score.</p><h3>The four archetypes</h3><p>Three surfaces, two implementations, one rule that fell out of the work:</p><p><strong>If your surface renders pixels for humans, go declarative. If it returns JSON for machines, go imperative. If it’s both, split the subdomain.</strong></p><p>Each site exposes tools appropriate to its purpose. Purpose falls into four archetypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84qyF9uhm36yua4mgKMxKg.png" /></figure><p><strong>Site-as-UI.</strong> Curated interface for browsing and acting on data. WebMCP approach: declarative, tool-name on UI elements. Example: <a href="https://dexpaprika.com/">dexpaprika.com</a>.</p><p><strong>Site-as-API.</strong> Programmatic access to data. WebMCP approach: none native. Expose via OpenAPI + api-catalog. Example: <a href="https://api.dexpaprika.com/">api.dexpaprika.com</a>.</p><p><strong>Site-as-MCP.</strong> Persistent stateful protocol. WebMCP approach: minimal, scanner-only. Real interface is the MCP protocol itself. Example: <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a>.</p><p><strong>Site-as-directory.</strong> Onboarding and discovery. WebMCP approach: meta-tools and shortcuts. Example: <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a>.</p><p>A product UI should expose UI actions, because the UI is its value. An API should expose its schema, because the schema is its value. An MCP server should expose the MCP protocol, not duplicate it. A directory page should help agents pick the right destination.</p><p>Duplicating the same 15 REST tools across all four surfaces would be fake consistency. Real consistency comes from each surface saying “this is my thing” and linking to its siblings so agents can navigate between them.</p><p>Consider agents.dexpaprika.com, which we treated as site-as-directory. We briefly considered tagging the nav links with tool-name attributes to juice the declarative count. The scanner would have counted them. Agents would have learned nothing — &quot;click home link&quot; is not a task. Picking the wrong archetype produces tools that pass the scanner and teach nothing.</p><h3>The cross-surface problem no spec solves yet</h3><p>An agent landing on any DexPaprika URL needs to answer three questions:</p><ol><li>What is this site?</li><li>What can I do here?</li><li>Where do I go if my task fits somewhere else?</li></ol><p>The scanner checks (1) and (2). We searched the A2A spec, the IETF well-known URI registry, and the current MCP discovery drafts for anything that addresses (3). Nothing describes sibling-service navigation. If you know of prior art, tell me — happy to be wrong here.</p><p>An agent on <a href="https://mcp.dexpaprika.com/">mcp.dexpaprika.com</a> looking for a single token price should skip the MCP session handshake and hit api.dexpaprika.com/networks/{net}/tokens/{addr} instead. An agent on <a href="https://dexpaprika.com/">dexpaprika.com</a> looking for multi-step analytics should connect to the MCP server. Without metadata telling them the ecosystem exists, agents either probe every subdomain or stick with whatever URL they landed on.</p><p>We added a custom relatedServices[] field to the A2A agent card on every subdomain. Six entries covering product-ui, rest-api, streaming-api, mcp-server, docs, and agents-front-door. Each has a role, a URL, and a one-sentence description explaining when an agent should prefer it.</p><pre>&quot;relatedServices&quot;: [<br>  {<br>    &quot;role&quot;: &quot;rest-api&quot;,<br>    &quot;url&quot;: &quot;https://api.dexpaprika.com&quot;,<br>    &quot;description&quot;: &quot;Public REST API. Best for stateless one-off queries. No auth, no rate limits.&quot;<br>  },<br>  {<br>    &quot;role&quot;: &quot;mcp-server&quot;,<br>    &quot;url&quot;: &quot;https://mcp.dexpaprika.com&quot;,<br>    &quot;description&quot;: &quot;Hosted MCP server with 16 tools. Best for multi-step agent workflows that benefit from a persistent session.&quot;<br>  }<br>  // …four more<br>]</pre><p>Not a standard field. If the A2A spec adds an official one later, we rename. The value is that an agent fetching any of our /.well-known/agent-card.json files gets the full ecosystem map in one request, with guidance on which surface fits which task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xqD0A2_T06KktfIy6QWYhw.png" /></figure><blockquote><em>This is where the scanner stops being useful and the thinking starts. The checklist gives you 13/13 for filling in the slots. It doesn’t tell you whether your slots make sense together.</em></blockquote><h3>The audit behind the scan</h3><p>Before promoting the score publicly I ran an end-to-end audit on each surface: does what the metadata claims actually match what the service does? Server card says 16 tools — are all 16 reachable over every transport? Agent card lists skills — do they correspond to real endpoints? Related-services pointers resolve?</p><p>They mostly did. A handful didn’t, in small ways that are cheap to fix once you’re looking for them. The useful takeaway wasn’t any individual miss. It was that publishing an agent card is a public commitment to a shape, and keeping the service aligned with that shape is a second job nobody had assigned. The scanner turned out to be good at exposing the gap between “what we say we expose” and “what we expose.”</p><blockquote><em>The scanner’s job is to check your discovery files. Your job is to check that your service matches them.</em></blockquote><h3>Results</h3><p>Three DexPaprika surfaces at 13/13:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfIG28O10H5tVNSQk83fqQ.png" /></figure><pre>dexpaprika.com          Level 5 Agent-Native    13/13    Declarative WebMCP<br>agents.dexpaprika.com   Level 5 Agent-Native    13/13    Imperative WebMCP<br>mcp.dexpaprika.com      Level 5 Agent-Native    13/13    Real MCP + scanner-facing WebMCP</pre><p>For context on what “13/13” means:</p><pre>isitagentready.com (scanner&#39;s own homepage)     Level 4    10/13<br>developers.cloudflare.com                       Level 4    7/13<br>blog.cloudflare.com                             Level 3    5/13</pre><p>Hitting 13/13 on three services means we took the checklist seriously for a week. It doesn’t mean we’ve solved agent UX. The scanner’s own creators haven’t shipped OAuth discovery or A2A agent cards on their own site. The whole field is new.</p><h3>What sticks</h3><p>Six months from now half of this post’s specifics will be outdated. Attribute names will change. Content Signals is still an IETF draft. The relatedServices field we invented might be replaced by an official A2A one. The framework outlasts the specifics.</p><ul><li><strong>Each surface serves one role.</strong> Site-as-UI, site-as-API, site-as-MCP, or site-as-directory. Don’t copy tools across surfaces just to feel consistent.</li><li><strong>Cross-surface navigation is a gap.</strong> No spec solves it. Publish metadata that does, and rename when an official field appears.</li><li><strong>The scanner is a forcing function, not a goalpost.</strong> The thinking about which tools to expose where is the interesting part. The number just tells you when to stop.</li></ul><h3>FAQ</h3><h4>What is WebMCP?</h4><p>WebMCP is a browser-facing extension of the <a href="https://modelcontextprotocol.io/">Model Context Protocol (MCP)</a> that lets a webpage advertise tools directly to AI agents. It has two flavors. The imperative form uses navigator.modelContext.registerTool() in JavaScript to register tool schemas and handler functions at page load. The declarative form puts tool-name HTML attributes on existing DOM elements so agents can treat UI actions (click, submit, toggle) as callable tools. Cloudflare&#39;s isitagentready scanner accepts either form.</p><h4>What’s the difference between MCP and A2A?</h4><p>MCP (Model Context Protocol) is a stateful protocol between a single AI client and a single server exposing tools, resources, and prompts. Think of it as the agent’s connection to one service. A2A (Agent-to-Agent) is a discovery and capability protocol for agents to find and talk to each other, advertised via a /.well-known/agent-card.json file that lists skills, supported interfaces, and authentication requirements. MCP is how an agent uses a tool. A2A is how an agent finds other agents.</p><h4>How do I test my API for agent-readiness?</h4><p>Run <a href="https://isitagentready.com/">isitagentready.com</a> against your domain. It tests 13 open standards: RFC 8288 Link headers, RFC 9727 API catalogs at /.well-known/api-catalog, MCP server cards, WebMCP, Content Signals in robots.txt, A2A agent cards at /.well-known/agent-card.json, OAuth authorization server metadata (RFC 8414), OAuth protected resource metadata (RFC 9728), OpenAPI discovery via service-desc link relation, markdown content negotiation, agent skills index, and more. Scores run from Level 0 (0/13) to Level 5 Agent-Native (13/13). Most sites score 3-7 on first run.</p><h4>Is declarative or imperative WebMCP better?</h4><p>Neither. They expose different things. Use declarative when your surface is a product UI where clicking a button is the operation the agent wants to perform. Use imperative when your surface is a headless service where calling an endpoint is the operation. Our dashboard at <a href="https://dexpaprika.com/">dexpaprika.com</a> is declarative. Our agent onboarding at <a href="https://agents.dexpaprika.com/">agents.dexpaprika.com</a> is imperative. Both hit 13/13.</p><h4>What are the four site archetypes?</h4><p>Site-as-UI (a product dashboard, tools are UI actions), site-as-API (a REST or GraphQL service, tools are endpoints exposed via OpenAPI), site-as-MCP (a hosted MCP server, the MCP protocol is the tool surface), and site-as-directory (an onboarding or discovery page, tools are meta-actions and cross-surface links). Each archetype implies a different WebMCP style, a different agent card, and a different set of discovery files. Picking the wrong archetype makes the work feel wrong even when the scanner passes.</p><h4>How do I solve cross-surface discoverability between my subdomains?</h4><p>No RFC solves this yet. Neither does the scanner. We added a custom relatedServices[] array to our A2A agent card on every subdomain, with each entry giving a role (rest-api, mcp-server, product-ui, etc), a URL, and a one-sentence description of when an agent should prefer that surface. An agent fetching /.well-known/agent-card.json on any of our domains gets the full ecosystem map in one request. If an official spec field appears later, we rename ours to match.</p><p><em>DexPaprika is a free, public DEX analytics platform. 35+ blockchain networks, 29M+ tokens, 31M+ pools. No API key, no rate limits. The </em><a href="https://mcp.dexpaprika.com/sse"><em>hosted MCP server</em></a><em> and </em><a href="https://agents.dexpaprika.com/"><em>agent onboarding guide</em></a><em> are the fastest ways to connect DexPaprika to Claude, Cursor, or any MCP-compatible client. If you’re working on agent-readiness for your own API, the </em><a href="https://isitagentready.com/"><em>isitagentready.com</em></a><em> scanner is the honest starting point.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=640a473710d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinpaprika/from-4-13-to-13-13-in-a-week-how-we-made-dexpaprika-agent-ready-640a473710d8">Four site archetypes for agent-ready APIs</a> was originally published in <a href="https://medium.com/coinpaprika">CoinPaprika</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>