Aero API: Aerodrome and Velodrome contracts and pool data
On 16 November 2026, Aero carried 65.8% of Base DEX volume. Formed when Aerodrome and Velodrome merged, it is built on-chain; this guide covers its contracts, Sugar and Aero pool data over REST.

Aerodrome and Velodrome merged into Aero on 22 October 2026, and Aero is built "100% onchain": developers integrate through its contracts, and an SDK is announced. According to DexPaprika data, Aero's new concentrated-liquidity factory alone carried 55.6% of Base DEX volume on 16 November 2026.
For market data you need an index that knows Aero's new factory and the four Aerodrome factories still trading beside it. On Base the five together carried 65.8% of the chain's indexed DEX volume, almost three times Uniswap's three versions combined.
Search for the Aerodrome API or the Velodrome API today and you land on one protocol, Aero. Dromos Labs, the team behind both, launched Aero at 00:00 UTC on 22 October 2026 (8:00 PM EDT on 21 October). AERO converted 1:1 into the new AERO, VELO converted at about 0.044 AERO, and the new supply was split 94.5% to the Aerodrome community and 5.5% to Velodrome's, matching each protocol's share of combined revenue in the 52 weeks before Aero was announced.
Aero now runs as one exchange on seven networks: Ethereum, Base, OP Mainnet, Arbitrum, Robinhood Chain, Ink and Arc. Below: what Aero gives developers, how Sugar fits after the merger, and what DexPaprika's index shows about four weeks after launch.
Is there an Aero API? Aero's on-chain contracts
Aero's API is on-chain by design. Its own site puts it this way in its pitch to AI agents: "100% onchain, Aero eliminates reliance on fragile APIs or centralized indexers, giving agents direct, trustless access to protocol functions for permissionless execution." The launch post adds that "Aero's native onchain data contracts let AI agents, aggregators and wallets integrate and execute directly."
What exists today is contract source and addresses. Dromos Labs publishes the core contracts in dromos-labs/metadex-public and the concentrated-liquidity pools in metadex-slipstream-public, each with a deployment-addresses folder holding one JSON file per chain: pool factories, routers, gauges and a metaquoter contract for on-chain quotes. Reading any of it means an RPC endpoint per chain and the ABIs, the same mechanics as before the merger.
An SDK is announced: "An SDK will make integration quick and easy for wallets, aggregators, dApps, CEXs, AI agents, and more." Until it ships, the two contract repositories in the dromos-labs GitHub organization are the integration point. One more detail for anyone planning a fork: new Aero files carry the Dromos Restricted Use License 1.0, which the README says "does not allow production use".
Sugar, the Aerodrome and Velodrome helper contracts
Before the merger, the nearest thing to an Aerodrome API was Sugar, read-only helper contracts whose repository opens with "Onchain API for Velodrome and Aerodrome developers!" One LpSugar.all(limit, offset) call returns a page of pools with their reserves, gauge and fees, so you don't have to walk the factories one pool at a time.
Sugar lives in velodrome-finance/sugar. Its Base deployment file lists the three older Aerodrome Slipstream factories. Aero's new Base factory, 0x9CB220581b91b0C83223012FE69688b92aD07a76, is published in the Dromos Labs deployment files. If you read Base through Sugar, check that the factory you care about is in its list before trusting a pool count.
Five Aerodrome factories on Base, and the newest one carries most of the volume
Aero did not replace Aerodrome's pools in place. It deployed a new concentrated-liquidity factory and left the four older factories live beside it, so Base now has five pool factories under the Aero umbrella. DexPaprika indexes each as its own DEX, and every factory_id below matches an address published by Dromos Labs or in Sugar's Base deployment file:
Index the old Aerodrome ids and skip aerodrome_slipstream and you miss about 85% of Aero's Base volume. Index only the plain aerodrome id, the obvious guess from the old name, and you see $1.9 million of $602.5 million.
Aero carried 65.8% of Base DEX volume on 16 November 2026
Twenty-one DEXes carried volume on Base in the 24 hours to 12:05 UTC on 16 November 2026, $916,227,664 in total. Aero's five factories made up 65.8% of it. Uniswap's three versions came to 22.1% ($202.6 million) and PancakeSwap V3 to 12.0% ($109.7 million). Aero's new factory on its own, $509.2 million, did two and a half times the volume of every Uniswap version on Base combined.
At our first measurement, on 23 September 2026, before the merger, the order was the other way round: Aerodrome's four factories held 42.6% of Base and Uniswap's three versions 47.0%.
Seven Aero chains, and where DexPaprika indexes it so far
Aero's deployment files list a concentrated-liquidity factory on each of the seven chains. DexPaprika indexes three of them so far, and a builder should know which:
On Robinhood Chain Aero is the third DEX by volume behind Uniswap v3 and v4, mostly from one WETH/USDG pool. On OP Mainnet, Velodrome's home, DexPaprika's DEX list still has only the two pre-merger Velodrome factories and no entry yet for Aero's new Optimism factory, so the Velodrome figure there undercounts Aero.
Reading Aero pools over REST
An index that already reads the factories turns this into an HTTP call, no RPC and no ABI:
curl "https://api.dexpaprika.com/networks/base/pools/search?dex_name=aerodrome_slipstream&limit=3"
That returns HTTP 200, shaped {results, has_next_page, next_cursor, query}. Each row carries id, dex_id, volume_usd_24h, volume_usd_7d, liquidity_usd, transactions_24h, price_usd and a tokens array. The dex_name parameter takes the dex_id, so swap in aerodrome_slipstream_3 or aerodrome for the older factories, or change the network to ethereum or robinhood. The pool detail call returns factory_id, which tells you which factory a pool belongs to.
The top row on 16 November was WETH/cbBTC in Aero's new factory, $147.6 million in 24 hours. Candles for it work without a key for the last 24 hours, and a relative start keeps the call valid whenever you run it:
curl "https://api.dexpaprika.com/networks/base/pools/0xec3c3755b9ded4a2960ef50c9b48c1694ce274c2/ohlcv?start=-12h&interval=1h&limit=5"
Each candle carries time_open, time_close, open, high, low, close and volume. Individual swaps come from the pool's /transactions endpoint, which needs a Dev or Pro plan; without a key it answered HTTP 403 on 16 November.
Pool search and recent candles need no key. A free key from console.dexpaprika.com raises the rate and the quota and reaches further back in candle history; current numbers live on the pricing page, because they move. Free-tier data can lag up to 60 seconds; real-time is the paid tier.
Two AERO tokens on Base
The new AERO is a new contract. On Base it is 0x3f5bF3EdAc59d650D8fDf9657a71F2f904A3a4Ee, in 60 DexPaprika-indexed pools that traded $14.7 million on 16 November. The pre-merger token, 0x940181a94A35A4569E4529A3CDfB74e38FD98631, still sits in 2,168 pools that traded $1.8 million. Both report the symbol AERO and trade near the same price, so anything that resolves AERO by symbol can pick the wrong one. Resolve by contract address, and take it from the security page in Aero's docs, which Aero names as the place to verify addresses.
Common questions
Does Aero have an API?
Aero's data access is on-chain, through what it calls native onchain data contracts. It publishes the contracts and per-chain deployment addresses, and an SDK is announced. For pool data over HTTP, DexPaprika indexes Aero on Base, Ethereum and Robinhood Chain.
Is the Aerodrome API still available?
Aerodrome's developer tool was Sugar, the on-chain helper shared with Velodrome. It still serves the older Aerodrome factories; Aero's new Base factory is listed in Dromos Labs' deployment files.
What happened to Velodrome and VELO?
Velodrome merged into Aero on 22 October 2026. VELO converted at about 0.044 AERO, and Velodrome holders received 5.5% of the new supply. OP Mainnet, Velodrome's chain, is one of Aero's seven networks.
Which chains does Aero run on?
Seven: Ethereum, Base, OP Mainnet, Arbitrum, Robinhood Chain, Ink and Arc. DexPaprika indexed Aero's new factory on Base, Ethereum and Robinhood Chain on 16 November 2026.
Does Aero have a subgraph?
Dromos Labs does not publish one. Aero is designed for on-chain reads with no centralized indexer, and DexPaprika's REST API covers its pools on the three chains above.
How these numbers were measured
Everything above was read off a live source on 16 November 2026, except the 23 September figures, which come from our first measurement with the same calls.
The merger terms and the quotes come from Aero's own site, read through its llms-full.txt. Repositories, licence text, deployment addresses and Sugar's Base deployment file were read through the GitHub API.
The Base table is one call to GET /networks/base/dexes at 12:05 UTC, all 21 rows; shares are of the sum of those rows, DexPaprika-indexed Base DEX volume. The Ethereum, Robinhood Chain and OP Mainnet figures come from the same call on each network, a few minutes apart. Each Aero row was matched to Dromos Labs' published factory address through the factory_id of its busiest pools. The OHLCV call is quoted as it ran and returned HTTP 200 without a key; the transactions call returned HTTP 403.
Every volume figure is a 24 hour window closing on the measurement, so expect it to move, the split between the old Aerodrome ids and Aero's new one most of all.
Full REST reference at docs.dexpaprika.com, and DexPaprika's Aerodrome page on Base has a live feed. Background on the chain: a complete guide to the Base blockchain ecosystem, and on the OHLCV gap, how to get DEX candles when a protocol's own API doesn't have them. The same question for two other DEXes: what the Uniswap API returns, and what PancakeSwap documents for BNB Smart Chain.
Original CoinPaprika guide.