What you can do
- Get a quote for a swap before committing
- Quote by source amount or target amount with
amountSide - Execute a swap between supported assets
- Swap from both master wallets and child addresses
- Route supported Stellar USDC destinations with the generic
recipientRoutingcontract
Endpoints
Recipient parameters
Stellar recipient routing
recipientRouting is supported only when the destination chain is Stellar. Existing EVM, Solana, and Tron swap requests are unchanged and must not send recipientRouting; requests that supply it are rejected. There is no separate recipient memo parameter.
For supported Stellar USDC destinations:
- Muxed
M...recipient: omitrecipientRouting. Its routing ID is already embedded in the address; sending routing data is rejected. - Base
G...recipient with a routing ID: sendrecipientRouting: { type: "memo_id", value: "123" }. The value must be a non-empty numeric string from0through18446744073709551615. Blockradar normalizes the destination to anM...address before requesting quote or execution. - Base
G...recipient without a routing ID: sendrecipientRouting: { type: "none" }with novalue. AG...recipient withoutrecipientRoutingis rejected. The destination base account must already have a Stellar USDC trustline before quote and execution. - Default Blockradar Stellar wallet: callers must explicitly send
recipientRouting: { type: "none" }.
Stellar base account with a routing ID
Stellar base account without a routing ID
Quote response metadata
Quote responses can includedata.recipientRouting to explain the routing result. Execute responses do not include this metadata.
Migrating from Stellar-only fields
Full API Reference
View all swap endpoints in the API Reference tab.

