Skip to main content

1inch (key required)

Uniswap (key required)

Tempo (keyless, on-chain)

Jupiter (Solana, key optional)

Optional higher-limit setup:

Fibrous (keyless)

TaikoSwap (keyless, on-chain)

Bungee auto (keyless default)

Execution (plan, run, submit, status)

Swap execution is currently available for Tempo and TaikoSwap:
Plan with --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 quote requires an explicit --provider.
  • --type defaults to exact-input.
  • --amount and --amount-decimal are for --type exact-input.
  • --amount-out and --amount-out-decimal are for --type exact-output.
  • Providers currently supporting exact-output: uniswap, tempo.
  • --from-address is required for --provider uniswap.
  • --slippage-pct is 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 --recipient must be omitted or match --from-address.
  • Wallet-backed standard EVM submit requires DEFI_OWS_TOKEN.
  • actions estimate returns fee-token-denominated estimates for Tempo actions (includes fee_unit and fee_token fields).
  • Output includes normalized trade_type, input_amount, and estimated_out with base and decimal forms.
  • Fibrous currently supports base, hyperevm, and citrea.