Read the docs
← Cross-chain swap APIs compared

LI.FI alternatives for swaps. For swaps across chains.

Checked October 27, 2026.

Why wallets running swaps look past LI.FI

LI.FI picks a route across third-party bridges, DEXs and solvers, among them Relay, NEAR Intents, Across and Mayan, and returns a transaction for the user to sign. Funds in transit sit with whichever provider fills each step.

Best for: Wallets that want one SDK in front of dozens of bridges, DEXs and solvers, with a ready-made widget. What wallets running swaps run into:

  • A 0.25% fee on every transaction, on top of your fee and those of the bridges and DEXs it routes through.
  • If a bridge step lands but the swap after it fails, the user is refunded on the destination chain in the bridged asset.
  • No Lightning or XRP, and no webhooks: integrations poll for status every 10 to 30 seconds.

The alternatives

  1. 1. Flashnet

    Deposits, swaps and withdrawals API

    Best for: Wallets that want native swaps across Bitcoin, Lightning, Solana, Tron and EVM chains, long-tail tokens included, each funded by a plain transfer, with their own fee on every order.

    Choose Flashnet if your wallet needs Lightning or XRP, wants one quote and one order status from deposit to delivery, or wants status by webhook rather than polling.

  2. 2. Relay

    Intent-based cross-chain protocol

    Best for: EVM and Solana wallets that want published low swap fees, a mature SDK and a long list of chains.

  3. 3. NEAR Intents

    Intent-based cross-chain protocol with competing market makers

    Best for: Wallets that want market makers competing on every swap across a very wide set of chains.

  4. 4. deBridge

    Intent-based cross-chain swap protocol

    Best for: EVM and Solana wallets that want a rate guaranteed at signing and hooks that act after the swap.

How they compare

On the points above, with each fact linked to its source. Every provider on every point is on the comparison page.

LI.FI alternatives for swaps, as of October 27, 2026
FlashnetLI.FIRelayNEAR IntentsdeBridge
Orders
Automatic refundsYesOrders that can't fill within the quote's bounds go back to the refund address you set.SourcePartlyIf a bridge step lands but the swap after it fails, the user is refunded in the bridged asset on the destination chain.SourceYesRefunds go to the refundTo address on the origin chain, less gas. Without one, there's no automatic refund.SourceYesUnfilled or underpaid deposits go to your refundTo address after the deadline.SourcePartlyBy default the user cancels on the destination chain. Auto-cancel needs deBridge's approval, and refunds usually arrive as USDC.Source
Networks
LightningYesIn and out over Lightning, including BOLT11 invoices and Lightning addresses.SourceNoNot among LI.FI's chains.SourceNoNot among the chains in Relay's API.SourceNoNot among the supported chains.SourceNoNot among the supported chains.Source
XRPYesXRP.SourceNoNot among LI.FI's chains.SourceYesListed in Relay's chains API.SourceYesClassic addresses with destination tags aren't supported through 1Click.SourceNoNot among the supported chains.Source
Operations
WebhooksYesWebhooks, plus a server-sent event stream of order status.SourceNoPoll the status endpoint every 10 to 30 seconds.SourceYesWebhooks and a websocket status stream.SourceNoPoll the status endpoint by deposit address.SourceNoPoll the order tracking API.Source
Platform feeSet per partner and route, and itemized on every quote.Source0.25% on every transaction, plus the fees of the bridges and DEXs it routes through.Source0% on same-token bridges; 0.01% on stablecoin, 0.06% on major-token and 0.15% on other swaps, plus gas.Source20 bps with an API key (1 bp on stablecoin and same-asset routes), 25 bps without, plus a 0.0001% protocol fee.SourceA flat fee in the source chain's gas token (0.001 ETH, 0.015 SOL) plus 4 bps, before solver margin and gas.Source