RAVN vs LI.FI
LI.FI is one of the biggest bridge and DEX aggregators, with 70 chains, and its API adds a 0.25% fee to every swap. We cover fewer chains and add no fee of our own. Here is where each one fits.
Quick answer
LI.FI is one of the largest bridge and DEX aggregators. Its API reaches 70 chains, including native Bitcoin, Solana, Sui and Tron, and it runs inside wallets like MetaMask and Phantom. If you build on its API, LI.FI adds a 0.25% fee to every swap, on top of what the venue charges.
We cover fewer chains and add no fee of our own. Our API races 17 venues across 17 chains, including native Bitcoin both ways. Open-source SDKs, a widget, a free MCP server and x402 endpoints are all live, and no API key is needed to start.
Eleven of our 17 venues also appear in LI.FI's list. So this is mostly about what sits on top of the same plumbing: the fee, the venues only one of us has, and how much code you install.
How we compare
| LI.FI | RAVN | |
|---|---|---|
| What it is | Bridge and DEX aggregator: API, SDK and widget. Jumper is its own app | API with open-source SDKs (JS/TS, Python, React), a widget, a free MCP server and x402. Our app runs on it |
| Chains | 70 mainnets in its API, including Bitcoin, Solana, Sui, Tron and Stellar | 17: native BTC, Solana and 15 EVM chains |
| Venues | 36 bridge and 37 exchange entries in its API | 17 venues, all quoted in parallel on every request |
| Native Bitcoin | Yes, both ways. Our test quotes went through Layerswap and NEAR Intents | Yes, both ways: Relay, NEAR Intents, THORChain, Chainflip |
| Bridge or wrapped token in the path | Depends on the route. Its list includes lock-and-mint bridges such as Polygon PoS Bridge and Gnosis Bridge | Neither. No lock-and-mint bridge and no wrapped copy of your token, so no custodian in between |
| Fee on top of venue cost | 0.25% on every API swap, with volume discounts on request. Jumper, its own app, charges its own smaller fee | 0 bps by default. Integrators can add their own, up to 100 bps |
| Integrator fee | You set it after signing up in LI.FI's partner portal. LI.FI keeps a share it does not publish | You set 0 to 100 bps on a free key you create yourself, no approval. On most venues you keep 60% |
| API key to start | Not required. 75 quotes per 2 hours without one | Not required. 30 requests a minute per IP |
| AI agent access | Hosted MCP server with 25 tools. No x402 | Free MCP server with 10 tools, plus x402 pay-per-call in USDC |
| SDK install footprint | 2 packages, 3.2 MB for the core. 16 packages, 81 MB with its Ethereum provider | 1 package, 52 KB, zero dependencies |
| Source available | SDK (Apache-2.0) and smart contracts on GitHub | SDK on GitHub (MIT). We write no contracts of our own |
Figures for LI.FI come from its own API and docs on 2026-09-25. Both products change often, so read this as a snapshot.
No bridge in the path
LI.FI aggregates bridges. Its list of 36 includes relayers like Across and Relay, and also lock-and-mint bridges such as Polygon PoS Bridge and Gnosis Bridge. Which one your swap goes through depends on the route LI.FI picks.
We never route a swap through a lock-and-mint bridge: a contract that locks your tokens on one chain and mints a copy on the other. That design is behind the biggest hacks in crypto. Our cross-chain venues are relayers, solvers and cross-chain pools that deliver the real token on the destination chain.
We never wrap your asset along the way either. No custodian and no synthetic token sits between what you send and what you receive. It is a deliberate rule, and it keeps users, integrators and agents on the safe path.
The fee on every API swap
Every quote LI.FI's API returned to us carried a line called "LIFI Fixed Fee" at 0.25%. That held for bridges, for same-chain swaps and for Bitcoin. On a $10,000 swap, that is $25 to LI.FI before the venue takes its own cut. LI.FI's docs say larger customers can get volume discounts.
That fee is for developers building on the API. Jumper, LI.FI's own app, shows its own "Jumper fee" instead: $1.68 on a 0.1 BTC swap we quoted there, about 0.02%.
We add 0 bps by default. You still pay what the venue charges, the same as you would through LI.FI. A fee on top only appears if an integrator building on our API chooses one, capped at 100 bps.
If you build on LI.FI and add your own fee, LI.FI takes a share that depends on your use case and volume. On our side the split is public. On most venues you keep 60% of what you collect and we keep 40%, and our pricing docs list the exceptions.
Venues only one of us has
LI.FI's list is far longer than ours: Stargate, Symbiosis, Squid, 1inch, OKX and dozens more. If a route needs one of those, LI.FI can reach it and we cannot. Circle's CCTP is on LI.FI's list too, but that one is not a real gap: several of our venues already move USDC over CCTP under the hood.
Five of our venues were missing from LI.FI's list when we checked: THORChain, CoW Protocol, and 0x Gasless, 0x Swap and 0x Solana. Bebop, the market maker, showed up there only on HyperEVM. 0x Gasless, Bebop and CoW are how we get you a firm, gasless price on EVM: you sign a message, and the market maker pays the gas and commits to the rate. THORChain is one of the four ways we move native Bitcoin.
Tools for AI agents
An MCP server lets an AI assistant like Claude take actions, not just talk about them. LI.FI runs a hosted one with 25 tools for quotes, routes, status and its Earn product. Neither of us signs transactions for you: both hand back a transaction for your own wallet to sign.
The gap is payment. Our x402 endpoints let an agent pay per call in USDC with no account at all, 0.001 a quote and 0.01 an execute. We found no x402 support at LI.FI. Our MCP server also covers the Bitcoin side end to end, down to building the transaction your Bitcoin wallet signs.
How much code you install
LI.FI's SDK is modular. The core is 2 packages and 3.2 MB. To send transactions on EVM chains you add its Ethereum provider, and the install grows to 16 packages and 81 MB, mostly the viem library. We measured both with a clean install on 2026-09-25.
Our SDK, @ravnexchange/sdk, is one package of about 52 KB with zero dependencies. It never touches a private key, so you bring the signer you already use. If your app already has viem or ethers, that is all you need.
Where LI.FI wins
- Coverage. 70 chains against our 17, and several times as many venues. If your users need Sui, Tron, Stellar or one of dozens of EVM chains we do not support, LI.FI gets them there.
- Scale. LI.FI says more than 1,000 partners use it, and names MetaMask, Phantom, Robinhood, Binance and Ledger. We are in beta and have not reached that scale.
- More than swaps. Its Composer can deposit into a vault or stake in the same call. We do not offer that today.
- Security program. LI.FI publishes an audit log for its contracts and runs a bug bounty of up to $1M. We have no contracts to audit, because we settle through independent venues.
When LI.FI fits better
- You need chains outside EVM, Solana and Bitcoin, or an EVM chain we do not support yet.
- You want swaps, bridging and DeFi deposits from one integration, and 0.25% per swap is fine at your volume.
- You want the vendor that MetaMask, Phantom and other large wallets already use.
If your users mostly move between EVM, Solana and native Bitcoin, compare a live quote for your own pair. On those routes the 0.25% is the difference you will feel.
Try it yourself
Parallel venues. Best execution. Live in beta. We never touch your funds.
FAQ
Does LI.FI charge a fee?
Yes, on its API. LI.FI's docs list a 0.25% service fee on each transaction, and every API quote we pulled on 2026-09-25 carried it as a "LIFI Fixed Fee" line. Larger customers can get volume discounts. Jumper, LI.FI's own app, charges its own smaller fee: $1.68 on a 0.1 BTC swap we quoted there. We add 0 bps by default; a fee only appears if an integrator building on us sets one, capped at 100 bps.
Does RAVN use bridges or wrapped tokens?
No. We never route a swap through a lock-and-mint bridge, the design behind the biggest hacks in crypto, and we never wrap your asset to complete a swap. Our cross-chain venues are relayers, solvers and cross-chain pools that deliver the real token on the destination chain. The only wrapped token you get from us is one you picked yourself, like WBTC. LI.FI aggregates bridges, and its list includes lock-and-mint bridges such as Polygon PoS Bridge and Gnosis Bridge.
Does LI.FI support native Bitcoin?
Yes, in both directions. Our API test quotes went through Layerswap, and a BTC quote in its Jumper app went through NEAR Intents. We also move native BTC both ways, through Relay, NEAR Intents, THORChain and Chainflip, and pick whichever pays the most.
Which venues does RAVN have that LI.FI does not?
When we checked LI.FI's API on 2026-09-25, five of our 17 venues were missing: THORChain, CoW Protocol, 0x Gasless, 0x Swap and 0x Solana. Bebop was listed only on HyperEVM. LI.FI has many venues we do not, such as Stargate, Symbiosis, Squid and 1inch.
Do I need an API key for LI.FI or RAVN?
Neither needs one to start. LI.FI allows 75 quotes per 2 hours without a key. We allow 30 requests a minute per IP, and a free key you create yourself raises that.
Which one supports more chains?
LI.FI, by a wide margin: 70 mainnets in its API, including Sui, Tron and Stellar. We support 17: native Bitcoin, Solana and 15 EVM chains.
Can AI agents use LI.FI and RAVN?
Both run MCP servers, and neither signs transactions for you. We also accept x402 pay-per-call payments in USDC with no account, which we did not find at LI.FI.
