ApexLiquid vs Sushi

ApexLiquid vs Sushi on 1 shared OpenChainBench benchmark, awaiting live measurements.

Read methodology Last measured Window: rolling 24h1 shared benchmark
ApexLiquid logo
ApexLiquid

ApexLiquid is a Telegram bot and smart wallet that auto copies on chain smart money traders on Hyperliquid in roughly one second, routing mirrored fills via a registered builder code.

Sushi logo
Sushi

Sushi is a multichain DEX whose Sushi Perps v2 frontend routes orders into the Hyperliquid orderbook via a builder code, layering Sushi points incentives on top.

Side by side measurements

Hyperliquid frontends builder revenue leaderboard

Trading
ProviderVolume routedUsers 24hEffective fee bpsTime since last fill
ApexLiquid$2.52M1190.048%11.4 s
Sushi$254.3K50.060%27.0 min

Ranking is by raw builder fee revenue in USD, not by value for users. Bigger number means more fees collected via the on-chain builder code field. For the trader cost perspective, switch to the Effective fee bps companion tab. Native Hyperliquid UI orders carry no builder code and are excluded. Data from a local hl node tailing every fill on mainnet.

Rolling 24h · Builder fees collectedRaw JSON

Frequently asked questions

ApexLiquid vs Sushi: which one is better?

ApexLiquid and Sushi are compared on 1 shared OpenChainBench benchmarks. See the live table on this page for every metric.

How is the ApexLiquid vs Sushi 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

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.