Squid Router alternative for in-app buys on other chains
A Squid Router alternative for wallets that buy tokens via postHooks: the Unigox Trade API quotes the destination gas and refunds a failed buy in stablecoin on the token's network. Stay on Squid for Cosmos chains, stablecoin swaps and widgets.
When to stay with Squid
Your users hold funds on Cosmos, XRPL or Stellar
Squid reaches Cosmos chains, XRPL, Stellar and Hedera, and runs Bitcoin and Solana swaps in a closed beta. A Trade API buy runs only on the stablecoin and network pairs Unigox confirms with you during integration.
Users swap stablecoins or sell back
Squid says it charges zero fees on stablecoin swaps, and it routes any token to any token in either direction. The Trade API only buys; selling the token later is a separate swap where it is held.
You need a ready swap, deposit or stake widget
Squid ships a swap widget for React, Next.js, Vite or an iframe, plus deposit and stake widgets. The Trade API has no widget: your app draws the buy screen and calls the API from its backend.
A Squid postHook buy and a Trade API buy
Each row follows one purchase: the user holds a stablecoin on one network, and your contract calls buy a token on a second one.
| Topic | Squid | Unigox |
|---|---|---|
| How the buy runs | You add postHook calls, any number of them, to the route request. After the swap or bridge, the tokens sit on Squid's Multicall contract on the destination chain, which then runs your calls. | Your backend sends your calls and the receiver with the quote request. Unigox brings the stablecoin to the destination network and runs up to eight calls there in one transaction, within 16,384 bytes and 3,000,000 gas. |
| Destination gas | Paid by the user in the source chain's native token, inside the source transaction. If gas spikes on the destination of an Axelar route, the buy pauses with a needs_gas status. | Charged in the stablecoin and taken off the delivered amount; the quote shows it with a deadline before the user signs. |
| If the buy fails | Squid reports partial_success when the destination transaction reverts, which can mean a postHook call failed. On an Axelar route the user is left holding axlUSDC there. Squid's docs do not say whether postHooks run on Squid Intents routes, where a failed swap is refunded on the source chain within about 15 minutes. | The stablecoin delivered on the destination network goes back to the receiver there. Only gas a failed execution used comes off, capped at the quoted charge. |
| Tracking each buy | A status call returns one of six states: success, needs_gas, ongoing, partial_success, not_found and refund. On Squid Intents the call must carry the quoteId, or the transaction is refunded to the source chain. | A status call by source transaction hash, or a signed webhook on each change, returns the state, the destination transaction and any refund. Each buy ends with the token delivered or a stablecoin refund. |
| Fees and your revenue | Squid's FAQ lists no protocol fee, and its own app adds a convenience fee on some routes. Your flat or percentage fee is set up with Squid, sits on top of its platform fees, and Squid keeps half of it. | A share of trading revenue, agreed with Unigox before your first purchase. No price list is published. |
| Direction and networks | Any token to any token, both ways, across EVM and non-EVM chains. | Buys only, on the stablecoin and network pairs Unigox confirms with you. |
UnigoxFrom a Squid postHook to a Trade API quote
Name the buys that run through hooks
Request access on the Trade API page with the tokens and networks your users buy through Squid postHooks. Unigox reviews each pair and agrees your revenue share; your integrator ID keeps serving every other route.
Port each postHook call
The target and calldata of every postHook call go into the Trade API quote request next to the receiver. Show the user the delivered amount, gas charge and deadline before the stablecoin transfer is signed.
Swap the status loop
For these buys, read the Trade API status by transaction hash or take its signed webhooks. The needs_gas and partial_success screens and the quoteId rule stay for Squid routes only. Tell users a failed buy returns stablecoin on the destination network, not on the chain they paid from.
Questions about Squid Router alternatives
What can replace Squid Router hooks for token buys?
The Unigox Trade API, for stablecoin buys: the gas charge is in the quote, your calls run on the token's network, and a failed buy refunds stablecoin there. Keep Squid for bridging, stablecoin swaps, sells and chains such as Cosmos and XRPL.
See the Trade APIDoes Squid Router charge fees on cross-chain swaps?
Squid charges no protocol fee and says it takes no fee on stablecoin swaps; its own app adds a convenience fee on some routes. Users pay gas on the source chain, and any integrator fee comes on top, half of it kept by Squid.
Where does a failed Squid Router swap refund the user?
On a Squid Intents route, to the sender's address on the source chain, in the RFQ bridge token, within about 15 minutes. On an Axelar route, a failed destination swap leaves axlUSDC on the destination chain. A failed Trade API buy returns the delivered stablecoin to the receiver on the destination network.
Can a wallet keep its Squid integrator ID and add the Trade API?
Yes. Your Squid integrator ID keeps serving swaps, bridging, the widgets and non-EVM routes, while stablecoin buys go through the Trade API.
Send Unigox the tokens your Squid hooks buy
List the tokens and networks your postHooks buy on. Unigox confirms the pairs it can run and works through a first purchase with your developers.
Squid and other names and logos are trademarks of their respective owners. Unigox is not affiliated with, endorsed or sponsored by them. Information about other companies comes from public sources, mainly the companies' own websites, and each company can change its products and fees at any time.