Cross-Chain Swap APIs in 2026: Coverage, Execution and Private Routes Compared

Rubic, LI.FI and Rango can all put a cross-chain swap inside a wallet. The choice depends on what the user came to do and what they need from your app along the way.

TL;DR: Choose Rubic API when your wallet needs regular and private swap routes through one integration. Look at LI.FI when the user wants to do more than swap, such as bridge funds and deposit them into a vault. Consider Rango when your wallet needs to guide users through a route across different blockchain ecosystems, one transaction at a time.

What should the user have when they’re done?

“Add cross-chain swaps” sounds like a single feature. A wallet user wants to turn ETH on Ethereum into USDC on another network and receive it at a separate address. A vault user starts with the same ETH but wants a funded position. For the wallet, USDC arriving can mean success. For the vault, there’s still a deposit to make.

That difference tells you more about which API to choose than a chain count does.

APIWhen it fitsWhat that means for your app
Rubic APIYou want to compare DEX, bridge and deposit routes, including private options where available.For one route, the user signs a swap. For another, they need an amount and a deposit address.
LI.FIThe swap is part of a larger action. Composer can bridge funds and call a protocol on a supported destination chain.A vault deposit needs its own confirmation. A successful bridge alone doesn’t tell the user they have a position.
RangoYour wallet serves users across EVM chains, Bitcoin, Solana or Cosmos. You want to choose how much of the route your app manages.The Basic API offers a single-step flow. The Main API lets you track each step and prompt the user when it’s time for the next one.

Rango’s distinction is easiest to see when a route needs two signatures. The first transaction has landed. The next one is waiting for the user. If your wallet still says “Processing,” both sides are waiting on each other. Knowing which step has finished lets you show the signature request instead.

What happens after the user picks a quote?

With Rubic API, a wallet can compare what each route expects to deliver before asking the user to commit. Once the user picks one, Rubic returns the details the wallet needs to carry it out.

On a contract route, the wallet might ask the user to approve a token and then sign the swap. On a manual deposit route, it shows where to send the funds, which asset to send and how much. A wallet built only around a Sign transaction button can display that second quote perfectly well and still leave the user with no way to complete it.

A deposit route can be worth supporting because the provider has access to its own liquidity. It may be able to exchange a pair that a swap and bridge can’t cover. The tradeoff is that the provider handles the funds until it pays out. If your wallet rules out that arrangement, leave those routes out before you compare prices.

There’s one more decision between choosing a quote and signing. If the expected payout has changed, show the new amount. Someone who picked a route because it offered the most USDC should get to decide whether they still want it.

When does a wallet need private routes?

Suppose a user wants to fund a payment wallet without linking it publicly to their main wallet. A second address field tells your app where to send the money. It doesn’t change what someone can see when the money arrives.

With Rubic API, your wallet can use the onlyPrivate filter to request private routes for the user’s tokens, networks and amount. On a supported route, the provider accepts the deposit and makes a separate payout. That breaks the visible onchain link between the sending and receiving wallets. The provider itself can still match the two.

This matters most when the search comes back empty. “No private route available” is a useful answer. You can let the user switch to a regular swap, but that choice belongs to them. A regular route with a better price still won’t do what they asked.

What if the user already holds USDC and wants USDC in another wallet on the same network? Rubic calls that a Private Transfer. If it’s a launch requirement, confirm how your integration supplies the receiving and refund addresses and tracks the payout; the private quote filter alone doesn’t document that whole flow.

What will your wallet say when a swap stops halfway?

The sending wallet says “confirmed.” The receiving wallet still shows nothing. What the user wants to know is simple: Where are my funds, and do I need to do anything?

Take the LI.FI vault example. If the bridge succeeds but the vault deposit doesn’t go through, the funds can be refunded on the destination chain. Telling the user which wallet and network to check is more helpful than showing “Deposit failed” next to an empty vault balance.

Even LI.FI’s DONE status needs a second look. With PARTIAL, the user received a different token than they requested. With REFUNDED, their funds were returned. If USDC arrived but the final conversion didn’t happen, say which token arrived and where. A green checkmark can’t tell that story.

On Rubic, NOT_FOUND can simply mean the transaction hasn’t been indexed yet. Check again before asking anyone to send another deposit. If the route does fail, the selected provider determines how the refund works: many refunds happen automatically, while some need action from the user.

FAQ

Can we add cross-chain swaps without replacing our wallet interface?

Yes. Rubic, LI.FI and Rango all offer APIs for teams that want to keep their own swap screens. An SDK can handle some transaction logic in your code; a widget gives you a ready-made interface.

Can we try these APIs before arranging production access?

Rubic’s standard keyless tier allows 10 requests per minute. LI.FI offers keyless access to public routing endpoints, with limits that vary by endpoint. Rango provides a test key with a low limit and asks teams to request their own key for production. When estimating what you’ll need, count quote refreshes too: a user can compare several amounts before signing a single swap.

Is every deposit route private?

No. A deposit address tells the user where to send funds. It doesn’t tell them whether the payout can be linked to their sending wallet. Only label a route private when the provider offers that protection for the selected swap.

Does a private feature in an API or SDK also work in the widget?

Not necessarily. LI.FI, for example, documents a private route option in its SDK. That doesn’t establish that its widget supports private transfers of the same asset. Check the specific operation in the product and version you plan to ship.

What should support ask for if a payout is missing?

Get the source transaction hash, the token and network the user expected, and the last status shown in the wallet. For Rubic, include the swap ID and selected provider if available. For Rango, the request ID and last completed step give support a place to start.

Last Verified: 17 November 2026

Website |  + posts

Marketing specialist with 5+ years of experience and a deep understanding of crypto, AI, market narratives, and industry insights.