Fastest cross-chain bridge quote API, live ms ranking
BridgesNEAR Intents
Trails2.00 s
- p99
- 4.95 s
- rank
- #8
- samples
- 5,073
Squid Router
Leads354 ms
- p99
- 1.04 s
- rank
- #1
- samples
- 863
NEAR Intents vs Squid Router
NEAR Intents leads on 0 of 2 shared benchmarks, Squid Router on 2. Squid Router wins on Fastest cross-chain bridge quote API, live ms ranking (354 ms vs 2.00 s), Cheapest cross-chain bridge for USDC at $300 notional (0.011% vs 1.19%).
NEAR Intents
Cross-chain intent layer from NEAR Protocol. The 1Click API runs a solver auction bus, signed quotes are settled by the winning market maker. Quote latency reflects bid arrival, not route search across LPs.
Squid Router
Cross-chain swap and liquidity routing built on Axelar. The Squid Router API sources routes across EVM chains via Axelar GMP, covering swaps and bridges in a single call.
Side by side measurements
Cheapest cross-chain bridge for USDC at $300 notional
BridgesNEAR Intents
Trails1.19 %
- p99
- 1.19%
- rank
- #5
- samples
- 103,290
Squid Router
Leads0.011 %
- p99
- 0.093%
- rank
- #1
- samples
- 17,280
Frequently asked questions
NEAR Intents vs Squid Router: which one is better?
NEAR Intents and Squid Router are compared on 2 shared OpenChainBench benchmarks. Squid Router leads on Fastest cross-chain bridge quote API, live ms ranking. See the live table on this page for every metric.
Which is faster on fastest cross-chain bridge quote api, live ms ranking, NEAR Intents or Squid Router?
On the Fastest cross-chain bridge quote API, live ms ranking benchmark, Squid Router leads at 354 ms versus NEAR Intents at 2.00 s. Live measurement is updated continuously by the OpenChainBench harness.
How is the NEAR Intents vs Squid Router 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.
How this pair was selected
A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.