Mobula vs Relay

Mobula leads on 3 of 5 shared benchmarks, Relay on 2. Mobula wins on Fastest cross-chain bridge quote API, live ms ranking (45 ms vs 178 ms), Best DEX aggregator for quoting newly-launched tokens (96.8% vs 40.1%), Fastest Solana cross-chain bridge quote API, live ms ranking (44 ms vs 172 ms). Relay wins on Cheapest cross-chain bridge for USDC at $300 notional (0.094% vs 0.19%), Fastest on-chain bridge execution (1.96 s vs 3.08 s). Data as of 2026-11-08 UTC.

Read methodology Last measured Window: rolling 24h6 shared benchmarks, 5 measured on both sides
Mobula logo
Mobula

Onchain data aggregator covering 80+ chains. WebSocket fast-trade feed, REST market and metadata, wallet portfolio APIs. Its swap endpoint routes multi-hop across named pools, so it is typed as an aggregator on the quote benches.

Relay logo
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

Fastest cross-chain bridge quote API, live ms ranking

Bridges

Mobula

Leads

45 ms

p99
479 ms
rank
#1
samples
4,608

Relay

Trails

178 ms

p99
497 ms
rank
#3
samples
4,547

Per chain · per region

ChainProviderEU-WestAggregate
Sol to BaseMobula40 ms40 ms
Relay174 ms174 ms
Base to ArbMobula42 ms42 ms
Relay161 ms161 ms
Arb to SolMobula63 ms63 ms
Relay301 ms301 ms
Arb to HyperCoreMobula43 ms43 ms
Relay211 ms211 ms
Quote latency
Mobulan/aRelayn/a

Cheapest cross-chain bridge for USDC at $300 notional

Bridges

Mobula

Trails

0.19 %

p99
0.20%
rank
#6
samples
46,080

Relay

Leads

0.094 %

p99
0.11%
rank
#5
samples
46,080

Per chain

ChainMobulaRelay
Sol to Base0.10%0.030%
Base to Arb0.12%0.037%
Arb to Sol0.26%0.050%
Arb to HyperCore0.32%0.27%
Effective fee
Mobulan/aRelayn/a

Best DEX aggregator for quoting newly-launched tokens

Aggregators

Headline: All chains

Mobula

Leads

96.8 %

p99
96.8%
rank
#1
samples
741

Relay

Trails

40.1 %

p99
40.1%
rank
—
samples
2,164

Per chain

ChainMobulaRelay
BNB100.0%33.5%
Robinhood100.0%16.7%
Quote coverage
Mobulan/aRelayn/a

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 what the quote is worth on evm-quote-output. The token universe rotates hourly so the score reflects live indexer freshness, not a curated whitelist.

Fastest Solana cross-chain bridge quote API, live ms ranking

Bridges

Mobula

Leads

44 ms

p99
479 ms
rank
#1
samples
2,881

Relay

Trails

172 ms

p99
496 ms
rank
#3
samples
2,821

Per chain · per region

ChainProviderEU-WestAggregate
SOL to BaseMobula40 ms40 ms
Relay174 ms174 ms
SOL to ArbitrumMobula42 ms42 ms
Relay167 ms167 ms
SOL to BNBMobula36 ms36 ms
Relay166 ms166 ms
SOL to EthereumMobula41 ms41 ms
Relay167 ms167 ms
SOL to RobinhoodMobula175 ms175 ms
Relay188 ms188 ms
Quote latency
Mobulan/aRelayn/a

Frequently asked questions

Mobula vs Relay: which one is better?

Mobula and Relay are compared on 6 shared OpenChainBench benchmarks. Mobula leads on Fastest cross-chain bridge quote API, live ms ranking. Relay leads on Cheapest cross-chain bridge for USDC at $300 notional. See the live table on this page for every metric.

Which is faster, Mobula or Relay?

On the Fastest cross-chain bridge quote API, live ms ranking benchmark, Mobula leads at 45 ms versus Relay at 178 ms. Live measurement is updated continuously by the OpenChainBench harness.

Which is cheaper, Mobula or Relay?

On the Cheapest cross-chain bridge for USDC at $300 notional benchmark, Relay leads at 0.094% versus Mobula at 0.19%. Live measurement is updated continuously by the OpenChainBench harness.

How is the Mobula 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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.