What it does
Squid provides cross-chain token swaps through a browser app and integration tools for wallets and other applications. Its router combines exchange and bridge providers, with market makers competing on Squid Intents routes. Route costs vary, and some app routes carry a convenience charge. Users must meet Squid’s age and sanctions conditions.
Choose what arrives and where
A cross-chain swap can change both the asset and its network, such as ETH on Ethereum to USDC on Arbitrum. In the app, select the sending and receiving tokens and networks, then review the quote before confirming through your wallet.
A connected wallet can prefill the destination address field, or you can paste another compatible address. Certain Cosmos routes also ask for an Osmosis address to handle a possible reversal. That extra address serves a different purpose from the final recipient.
Squid lists no protocol fee, but charges a convenience fee on selected frontend routes. The quote includes the relevant route and network costs; a zero Squid charge on a supported stablecoin route does not remove every external cost.
Follow the route after sending
Completion and refund behavior depends on the route. For an Axelar route whose final swap fails, the wallet may receive axlUSDC on the destination chain instead of the requested asset. Failed Squid Intents routes return the route's settlement asset to the originating chain. That may be a native coin or USDC. A refund is therefore not always the original token on the original terms.
The terms require at least 18 years of age and contractual capacity in Panama and the user's home jurisdiction. They exclude sanctioned parties and users tied to comprehensively embargoed locations, including Cuba, Iran, North Korea and Syria. Price changes and transaction failures can cause losses.
Building with Squid
Developers can embed a widget or use the API, an application programming interface, and the JavaScript/TypeScript toolkit. Integrator IDs are issued after partnership review. The API example takes chain and token inputs, requests a route, executes the returned transaction and checks status.
For Squid Intents, status checking must include the route's quoteId. Omitting it can cause the transaction to fail and be refunded. Preserve that identifier with the transaction hash when building a status screen.
Strengths
- Destination-address controls support a recipient different from the connected wallet
- Status guidance distinguishes complete swaps, partial delivery and route-specific refunds
Watch out for
- Sanctions restrictions and adulthood conditions apply to use
- A failed route can deliver a settlement asset instead of the token originally requested
Best for
- Wallet users converting assets between supported networks
- Developers adding cross-chain transactions and a usable status screen
Sources
- Squid cross-chain swaps and developer tools (Oct 27, 2026)
- Squid: set a different destination address (Oct 27, 2026)
- Squid architecture and fees FAQ (Oct 27, 2026)
- Squid terms of service (Oct 27, 2026)
- Squid integration overview (Oct 27, 2026)
- Squid API swap integration (Oct 27, 2026)
- Squid transaction status and refund behavior (Oct 27, 2026)
