Jupiter vs Relay

Name: Jupiter vs Relay OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

Jupiter leads on the only live benchmark. Jupiter wins on Best DEX aggregator for quoting newly-launched tokens (98.6% vs 41.3%).

Read methodology Last measured Sat, 22 Aug 2026 03:13:58 UTCWindow: rolling 24h1 shared benchmark

Jupiter

Solana swap aggregator. REST APIs for quotes, swap routing, price, and token lists across Solana DEXs.

Relay

Cross-chain intent network from Reservoir. Users sign an intent, relayers compete to fill on the destination, settlement is typically sub-30 seconds.

Side by side measurements

Best DEX aggregator for quoting newly-launched tokens

Aggregators

Jupiter

Leads

98.6 %

p99: 98.6%
rank: #1
samples: 1,359

Relay

Trails

41.3 %

p99: 41.3%
rank: —
samples: 2,278

Per chain

Chain	Jupiter	Relay
Solana	98.6%	36.1%

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.

Frequently asked questions

Jupiter vs Relay: which one is better?

Jupiter and Relay are compared on 1 shared OpenChainBench benchmarks. Jupiter leads on Best DEX aggregator for quoting newly-launched tokens. See the live table on this page for every metric.

Which is more reliable, Jupiter or Relay?

On the Best DEX aggregator for quoting newly-launched tokens benchmark, Jupiter leads at 98.6% versus Relay at 41.3%. Live measurement is updated continuously by the OpenChainBench harness.

How is the Jupiter vs Relay comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

Related comparisons

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.