RAVN vs Symbiosis
Symbiosis moves every swap through its own pools, its own chain and its own relayers. We race 20 outside venues, from relayers and solvers to RFQ market makers, DEX aggregators and cross-chain pools. Here is how that plays out, starting with Bitcoin.
Quick answer
Symbiosis is a cross-chain exchange with its own liquidity. It locks your tokens on the source chain, swaps stand-in tokens in its own pools on its own chain, and releases real tokens on the other side, with its own relayer network signing each step. Its API lists 59 chains, including TON, Tron and XRP.
We race 20 venues that each move money their own way: relayers like Across and Relay, solver and intent networks like NEAR Intents and CoW, RFQ market makers like 0x Gasless and Bebop, DEX aggregators like Jupiter and KyberSwap, and cross-chain pools like THORChain and Chainflip. Your swap goes to whichever pays you the most, and it settles there. We cover 17 chains, including native Bitcoin both ways.
The biggest difference right now is Bitcoin. When we checked on 2026-09-25, Symbiosis's own Bitcoin bridge was not quoting, and BTC went through outside services instead.
How we compare
| Symbiosis | RAVN | |
|---|---|---|
| What it is | Cross-chain exchange with its own pools, chain, relayers and SIS token | API with open-source SDKs (JS/TS, Python, React), a widget, a free MCP server and x402. Our app runs on it |
| How funds move | Locked in Symbiosis contracts, swapped as stand-in tokens in its pools, released by its relayers | Through whichever venue wins the quote: a relayer, a solver or intent network, an RFQ market maker, a DEX aggregator, or a cross-chain pool. We write no contracts and never hold funds |
| Bridge or wrapped token in the path | Yes: your tokens are locked in its contracts and minted as synthetic sTokens on its chain mid-swap | You always receive the real token. No bridge of our own, though NEAR Intents routes pass through NEAR's bridge mid-swap |
| Chains | 59 in its API, including TON, Tron, XRP and Dogecoin. Some only through partners | 17: native BTC, Solana and 15 EVM chains |
| Native Bitcoin | Its own bridge was not quoting. BTC in went through Changelly, BTC out through Chainflip | Both ways: Relay, NEAR Intents, THORChain, Chainflip, Rift |
| Fee on top of venue cost | No fixed rate published. A cross-chain fee covers gas on its chain and the destination | 0 bps by default. Integrators can add their own, up to 100 bps |
| Integrator fee | Set up by Symbiosis on request. Paid out in stand-in tokens on its chain. None on same-chain swaps | You set 0 to 100 bps on a free key you create yourself. Paid out automatically |
| API key to start | Not required. 10 requests a second | Not required. 30 requests a minute per IP |
| AI agent access | Hosted MCP server with 10 tools. Not in its docs. No x402 | Free MCP server with 10 tools, plus x402 pay-per-call in USDC |
| SDK | Archived on GitHub, "no longer the recommended integration method". 568 packages, 652 MB | 1 package, 52 KB, zero dependencies, maintained |
Figures for Symbiosis come from its own docs, site and API on 2026-09-25. Both products change often, so read this as a snapshot.
Bitcoin, right now
Symbiosis's docs describe its own native Bitcoin bridge. When we asked its API for BTC routes on 2026-09-25, every route through that bridge came back "not available".
BTC still moves through partners. BTC in was quoted through Changelly, which Symbiosis's own API labels "semi-centralized". BTC out went through Chainflip. With us, up to five venues quote every Bitcoin swap in both directions: Relay, NEAR Intents, THORChain, Chainflip and Rift. None of them is an instant-exchange service.
The real token, every time
A Symbiosis swap is lock and mint. Your tokens are locked in its contracts on the source chain, minted as synthetic sTokens on its own chain, swapped there, then burned to release real tokens on the other side. Its docs say a group of relayers signs each step, with a second group picked by Symbiosis's admins able to veto. Its Bitcoin bridge worked the same way, minting syBTC.
What you receive is always the real token on the chain you picked, never a wrapped copy. The only wrapped token you get from us is one you picked yourself, like WBTC. We run no bridge of our own and write no contracts.
How your coins travel depends on the venue that wins. Relayers such as Across and Relay pay you out from their own funds, and cross-chain pools such as THORChain and Chainflip swap from vaults of real coins. NEAR Intents works differently: its own bridge holds your deposit and issues a matching token on NEAR while solvers fill the swap, then burns it and sends you the real asset, usually within minutes. Every quote names the winning venue, so you can see which path you are on.
The SDK situation
Symbiosis's JavaScript SDK is archived on GitHub, and its docs say it is no longer the recommended way to integrate. Installing it on 2026-09-25 pulled in 568 packages and 652 MB, including a full copy of the Hardhat developer toolkit. Its REST API is the supported path.
Our SDK, @ravnexchange/sdk, is one package of about 52 KB with zero dependencies, MIT-licensed and actively maintained on GitHub. Python and React clients sit next to it.
Where Symbiosis wins
- Chain range. 59 chains against our 17, including TON and Tron through its own pools, and XRP, Dogecoin and Litecoin through partners. We support none of those.
- Its own liquidity. Stablecoin routes between its chains do not depend on an outside venue having inventory.
- Rate limit. 10 requests a second without a key, well above our 30 a minute. A free key raises ours.
- Track record. Running since 2021, with published audits of its core contracts.
When Symbiosis fits better
- Your users need TON, Tron or another chain we do not support.
- You want one protocol's pools behind every stablecoin route.
If you need native Bitcoin in both directions today, or want no extra protocol layer between your users and the venue, compare a live quote on our side.
Try it yourself
Parallel venues. Best execution. Live in beta. We never touch your funds.
FAQ
Does Symbiosis support native Bitcoin?
Its docs describe its own native BTC bridge, but every route through it returned "not available" when we checked on 2026-09-25. BTC in was quoted through Changelly, which Symbiosis's API labels "semi-centralized", and BTC out through Chainflip. We swap native BTC both ways through Relay, NEAR Intents, THORChain, Chainflip and Rift.
Does RAVN use bridges or wrapped tokens?
We run no bridge of our own, and you always receive the real token, never a wrapped copy. The only wrapped token you get from us is one you picked yourself, like WBTC. One venue, NEAR Intents, moves coins in and out through its own bridge, so on its routes your deposit is held as a matching token on NEAR for the minutes the swap takes. Symbiosis locks your tokens and mints synthetic sTokens on its own chain mid-swap.
How does Symbiosis move funds?
It locks tokens in its contracts, swaps stand-in tokens in its own pools on the Symbiosis chain, and releases real tokens on the destination. A group of relayers signs each step. We send each swap to whichever of 20 venues pays the most: relayers such as Across and Relay, solver and intent networks such as NEAR Intents and CoW, RFQ market makers such as 0x Gasless and Bebop, DEX aggregators such as Jupiter, or cross-chain pools such as THORChain and Chainflip. It settles on that venue.
Does Symbiosis charge a fee?
Symbiosis publishes no fixed rate. Its quotes include a cross-chain fee that covers gas on its chain and on the destination. We add 0 bps by default.
Is the Symbiosis SDK still maintained?
Its JavaScript SDK is archived on GitHub, and its docs say it is no longer the recommended integration method. The REST API is the supported path. Our SDK is one 52 KB package with zero dependencies, maintained on GitHub.
Which one supports more chains?
Symbiosis: 59 in its API, including TON, Tron and XRP, some of them only through partners. We support 17: native Bitcoin, Solana and 15 EVM chains.
