Batch swaps and multi-chain execution

swap.multi returns multiple swap or bridge quotes in a single MCP call. Each request in the batch is quoted in parallel. Use it to compare routes, split a position across chains, or prepare several transactions before the user or agent signs.

When to use swap.multi

Use swap.quote when you need one optimal route for a single swap or bridge. Use swap.multi when you need two or more quotes at once: e.g. "Swap half my USDC on Base to ETH and half to Arbitrum," or "Quote USDC→ETH on Ethereum, Base, and Arbitrum so I can pick the best chain." Responses are independent; each item includes its own transactionRequest and metadata. Quotes are valid for a short window (about 30 seconds); sign and submit sequentially to avoid nonce issues.

Parameters

One argument: requests, an array of 1–10 swap request objects. Each object uses the same shape as swap.quote:

fromToken, toToken: symbol or contract address.
fromAmount: amount in smallest unit (e.g. 6 decimals for USDC).
fromAddress: sender wallet (for routing and approvals).
toAddress (optional): recipient; defaults to fromAddress.
fromChain, toChain (optional): e.g. "ethereum", "base". Omit or set equal for same-chain; set different for bridge.
slippage (optional): decimal, e.g. 0.005 for 0.5%.
order (optional): "CHEAPEST" or "FASTEST".

Demo: two quotes in one call

Ask the agent: "Get swap quotes for (1) 1000 USDC to ETH on Base and (2) 1000 USDC to ETH on Arbitrum, from address 0x...." The agent calls swap.multi with requests containing two elements: one with fromChain: "base", toChain: "base", the other with fromChain: "arbitrum", toChain: "arbitrum". The response returns two quotes; the agent can compare output amount or gas and then use swap.quote again for the chosen route if needed, or the user signs both txs.

Demo: split across chains

"Quote bridging 5000 USDC from Base to Ethereum and 5000 USDC from Base to Arbitrum." Two requests, same fromChain: "base", different toChain. Each result has its own transactionRequest. Execute one bridge at a time and use swap.status to track each.

Response shape

Each item in the response array mirrors a single swap.quote result: route summary, expected output, fees, and transactionRequest (to, data, value, gasLimit). The agent or user signs and submits; Syenite never holds keys. For bridges, use swap.status with the sending tx hash and chain to monitor completion.