1inch (key required)
Uniswap (key required)
Tempo (keyless, on-chain)
Jupiter (Solana, key optional)
Fibrous (keyless)
TaikoSwap (keyless, on-chain)
Bungee auto (keyless default)
Execution (plan, run, submit, status)
Swap execution is currently available for Tempo and TaikoSwap:--wallet (OWS) or --from-address (local signer). Tempo is a separate path and always uses --from-address. See Execution & Signing for full details.
Standard EVM submit (OWS-first)
Tempo execution
Tempo swaps use native type 0x76 transactions that batch approve+swap into a single atomic call. Fee payment is in a fee token (defaults to USDC.e on mainnet).Notes
swap quoterequires an explicit--provider.--typedefaults toexact-input.--amountand--amount-decimalare for--type exact-input.--amount-outand--amount-out-decimalare for--type exact-output.- Providers currently supporting
exact-output:uniswap,tempo. --from-addressis required for--provider uniswap.--slippage-pctis optional and currently applies to Uniswap quotes only.- Tempo DEX currently supports USD-denominated TIP-20s only and auto-routes supported pairs through quote-token relationships.
- Tempo DEX swap execution settles to the caller, so
--recipientmust be omitted or match--from-address. - Wallet-backed standard EVM submit requires
DEFI_OWS_TOKEN. actions estimatereturns fee-token-denominated estimates for Tempo actions (includesfee_unitandfee_tokenfields).- Output includes normalized
trade_type,input_amount, andestimated_outwith base and decimal forms. - Fibrous currently supports
base,hyperevm, andcitrea.

