Building with an AI assistant? Add the SODAX Builders MCP (
https://builders.sodax.com/mcp) to Claude, Cursor, or any MCP-capable tool and it can pull live token lists, real quotes, and these docs while it writes your integration.1. Install
2. Create a Redbelly wallet provider
Redbelly uses the sameEvmWalletProvider as every other EVM network, keyed by ChainKeys.REDBELLY_MAINNET. The account behind it must have Redbelly network access: without it, the account cannot send the transaction that creates the intent. See User access.
@sodax/wallet-sdk-react connects EVM wallets for you and hands back a ready-made provider via useWalletProvider. See Wallets.
3. Look up supported tokens
Token addresses and decimals come from the SDK config, so you never hard-code them.4. Quote and swap
swap() runs the full lifecycle: it creates the intent on Redbelly, verifies the transaction landed, relays it to the hub, and notifies the solver to fill on the destination network.
ok means the intent was created, relayed to the hub, and the solver notified, not that it was
filled. Poll sodax.swaps.getStatus({ intent_tx_hash: intentDeliveryInfo.dstTxHash }) until the
status is SolverIntentStatusCode.SOLVED, which is the only success signal. The
main quickstart has the full polling loop, including why NOT_FOUND is not terminal.
A few things to know on Redbelly:
- RBNT needs no approval. It is the native token. Swapping an ERC-20 token on Redbelly needs an allowance first; see Approvals.
- Amounts follow
token.decimals. RBNT has 18 decimals, but USDC and USDT on Redbelly have 6. Always build amounts from the token’s owndecimals. - No network access, no intent. If the account has not been enabled on Redbelly, the intent transaction cannot be sent. Have users complete Redbelly’s access flow before their first SODAX action.
Next steps
- Swaps on Redbelly: approvals, fees, manual orchestration.
- Money Market on Redbelly: supply and borrow with cross-network collateral.
- Full API reference: Swaps in the SDK docs.