Best DEX aggregator for quoting newly-launched tokens
Jupiter leads quote coverage at 95.0% (24h avg) on Best DEX aggregator for quoting newly-launched tokens. Share of newly-launched tokens each aggregator can return a valid swap quote for, sampled hourly from 6 launchpads across Solana, Base, BNB and Robinhood.
TL;DR. As of , Jupiter leads quote coverage at 95.0% (24h avg) on Best DEX aggregator for quoting newly-launched tokens. Source: OpenChainBench, https://openchainbench.com/benchmarks/token-quote-coverage.
Read this carefully
Coverage means the aggregator returned a non-zero output amount for the probed token. It says nothing about quote quality, price accuracy or transaction success rate. A high score means the routing engine found at least one valid path. Latency is measured separately on evm-quote-latency and solana-dex-quote-latency. The token universe rotates hourly so the score reflects live indexer freshness, not a curated whitelist.
Every DEX aggregator claims to cover "millions of tokens". This benchmark forces the question. given a token that graduated from a launchpad in the last 24 hours, can the aggregator actually return a swap quote for it right now. The harness samples 20 random graduated tokens per launchpad per hour from Dexscreener's latest-pairs feed, fires a 1 USDC to token quote at each aggregator, and records whether a non-zero output amount came back. No whitelists, no curated lists, just the aggregator's live routing engine against the tokens the market is actually trading. The leaderboard splits by launchpad because the coverage challenge is different on each one. Pump.fun graduates need Raydium routing. Virtuals tokens need a live Base pool graph. Four.meme graduates need PancakeSwap v2 event indexing. An aggregator that dominates one launchpad can have gaps on another depending on how it discovers new pools.
Methodology
We benchmark DEX aggregators on their ability to quote tokens that graduated from a major launchpad in the last 24 hours. The harness pulls 20 random graduated tokens per launchpad per hour from Dexscreener's latest-pairs API (neutral third-party source), then fires a quote request (1 USDC to token) at each aggregator in parallel. A probe is a coverage hit when the response carries a non-zero output amount. Errors (no route, token not found, 4xx, timeout) count as misses. Coverage is the rolling ratio of hits to attempts over 24 hours, expressed as a percentage. The token universe changes every hour: the same token is never probed twice in the same hourly batch, so the score reflects live indexer freshness rather than accumulated historical coverage. The venue dimension lets readers see whether a provider's gap is structural (it does not index Meteora DBC pool types) or temporary (it lags new Raydium pairs by a few minutes). The chain dimension narrows to a single chain for providers that are chain-specific (Jupiter is Solana-only; ParaSwap covers Base, BNB and Robinhood; KyberSwap, Mobula, and Relay cover all four chains).
Frequently asked
Which DEX aggregator supports the most newly launched tokens?
Jupiter currently leads at 95.0% overall coverage (24h) across 4 measured providers. The leaderboard reflects live quote probes on tokens graduated in the last 24 hours from 6 launchpads, not a static token catalogue. Rankings shift by launchpad: an aggregator that saturates Pump.fun may trail on Meteora DBC or Virtuals depending on which pool types its router explicitly supports.
Why measure coverage on graduated tokens only, not all tokens?
Tokens still on a bonding curve cannot be externally swapped by definition. Coverage is meaningful only once a token has a real DEX pool. Graduation criteria vary: for Pump.fun and Moonshot it means a Raydium CPMM pool; for Meteora DBC it means a DLMM concentrated liquidity pool; for Virtuals a Uniswap V3 pool; for Four.meme a PancakeSwap v2 pool; for Pons a Uniswap V3-based pool on Robinhood chain.
Does coverage mean the swap will actually succeed on-chain?
No. A coverage hit means the routing API returned a non-zero output amount. The actual transaction could still revert due to slippage on a thin pool, a front-run, or an RPC issue. The quote coverage bench measures indexer freshness and routing capability, not transaction success rate.
Why is 1 USDC used as the probe amount instead of a larger notional?
Newly-launched tokens often have thin liquidity. A larger probe amount would trigger high-slippage rejection paths in many aggregators, recording a miss not because the aggregator lacks routing for the token but because the pool cannot absorb the size. 1 USDC isolates routing capability from liquidity depth.
Why is Dexscreener used as the token source rather than each aggregator's own list?
Using any aggregator's own token list as the probe universe would give that aggregator a structural information advantage: it would probe only tokens it already knows about and trivially score 100%. Dexscreener is a neutral third-party indexer that tracks on-chain pool creation events independently of all measured providers.
Why is Jupiter queried with strictMode=false?
Jupiter's strictMode=true restricts quotes to verified tokens on its curated list, which defeats the purpose of a coverage bench targeting newly-launched tokens. strictMode=false instructs Jupiter to attempt routing for any token with an existing pool, matching how wallets typically call the API when displaying all tradeable tokens.
What happens when a provider is chain-specific?
Jupiter is Solana-only and appears as null on EVM rows. ParaSwap covers Base, BNB, and Robinhood. KyberSwap covers Base, BNB, and Robinhood. Mobula and Relay cover all four chains including Solana. Null cells are excluded from cross-chain aggregates so chain-restricted providers are not penalized.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/token-quote-coverage