Read the docs
← Cross-chain swap APIs compared

NEAR Intents alternatives for swaps. For swaps across chains.

Checked October 27, 2026.

Why wallets running swaps look past NEAR Intents

Through its 1Click API, market makers compete to quote each swap, which settles atomically on NEAR's verifier contract. Assets from other chains are bridged into NEAR Intents and withdrawn to the destination chain.

Best for: Wallets that want market makers competing on every swap across a very wide set of chains. What wallets running swaps run into:

  • Tokens come from 1Click's list; there's no swapping a token by its contract address.
  • No Lightning, and Bitcoin waits to be mined, which the API puts at around an hour.
  • No webhooks: integrations poll for status.

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, long-tail tokens by address on Solana and EVM chains, Bitcoin credited before confirmation, or status by webhook.

  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. 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.

  4. 4. LI.FI

    Cross-chain bridge and DEX aggregator

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

How they compare

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

NEAR Intents alternatives for swaps, as of October 27, 2026
FlashnetNEAR IntentsRelaydeBridgeLI.FI
Orders
Any token by addressYesAny SPL or ERC-20 token by address, in or out, on Solana and EVM chains, routed through a stablecoin on its own chain.SourceNoTokens come from 1Click's token list; naming a token by contract address isn't documented.SourceYesTokens with solver or DEX liquidity on most chains; Bitcoin, Tron, TON and XRP take listed tokens only.SourceYesAny token with DEX liquidity indexed by aggregators such as 1inch or Jupiter, settled through reserve assets.SourceYesAny token by address on its supported chains, liquidity permitting; high-tax tokens are rejected.Source
Networks
LightningYesIn and out over Lightning, including BOLT11 invoices and Lightning addresses.SourceNoNot among the supported chains.SourceNoNot among the chains in Relay's API.SourceNoNot among the supported chains.SourceNoNot among LI.FI's chains.Source
Bitcoin credited before confirmationYesEligible deposits can be credited before the first confirmation, for a fee. Otherwise after 1 confirmation.SourceNoCredited once mined; the API notes Bitcoin may take around an hour.SourceNoProcessed after 1 confirmation, or 2 for high-value deposits.SourceNoNo Bitcoin support.SourceNot documentedIt depends on the bridge filling the route.
Operations
WebhooksYesWebhooks, plus a server-sent event stream of order status.SourceNoPoll the status endpoint by deposit address.SourceYesWebhooks and a websocket status stream.SourceNoPoll the order tracking API.SourceNoPoll the status endpoint every 10 to 30 seconds.Source