Skip to main content

​
Quote routes

bridge quote requires an explicit --provider. 
defi bridge quote --provider across --from 1 --to 8453 --asset USDC --amount 1000000 --results-only
Use a specific provider: 
defi bridge quote --provider lifi --from 1 --to 8453 --asset USDC --amount 1000000 --results-only
defi bridge quote --provider bungee --from hyperevm --to 8453 --asset USDC --amount 5000000 --results-only
Amount inputs: 
defi bridge quote --provider across --from 1 --to 8453 --asset USDC --amount-decimal 1.5 --results-only

​
Execution notes (Across and LiFi)

Bridge execution is available through bridge plan|submit|status for --provider across|lifi. 
defi bridge plan --provider across --from 1 --to 8453 --asset USDC --amount 1000000 --wallet agent-treasury --results-only
export DEFI_OWS_TOKEN=...
defi bridge submit --action-id <action_id> --results-only
Plan with --wallet (OWS) or --from-address (local signer). See Execution & Signing for submit auth details.

​
Bridge analytics

These commands require DEFI_DEFILLAMA_API_KEY: 
defi bridge list --limit 20 --results-only
defi bridge details --bridge layerzero --results-only

​
Notes

  • --to-asset is optional; default is source symbol on destination chain.
  • --provider is required for bridge quote; there is no implicit default provider.
  • Bungee quote mode is keyless by default.
  • Optional bungee dedicated backend mode requires both DEFI_BUNGEE_API_KEY and DEFI_BUNGEE_AFFILIATE.
  • Bungee quote requests use deterministic placeholder sender/receiver addresses for quote-only flows.
  • Quotes include fee_breakdown with lp_fee, relayer_fee, gas_fee, totals, and a consistency check against amount deltas.
  • Across can omit native USD fee fields on some routes; in those cases estimated_fee_usd may use a stable-asset approximation.
  • Across /swap/approval responses can include max-allowance approve calldata. defi-cli blocks approval amounts above planned input by default; use --allow-max-approval on bridge submit only when you explicitly accept that larger allowance.
  • Bridge submit validates canonical execution targets on covered Across/LiFi source chains before signing. Use --unsafe-provider-tx only when you intentionally want to bypass that provider-payload guardrail.
  • action_policy_error can also indicate an OWS policy denial when the wallet backend rejects execution.
  • Bridge submit marks bridge steps complete only after destination settlement is confirmed by provider status APIs (Across /deposit/status, LiFi /status).
  • --step-timeout applies to each bridge wait stage (receipt and settlement polling). Slow routes may need higher values (for example --step-timeout 15m).
  • Global --timeout controls provider/planning requests. Execution wait budget is derived from --step-timeout and remaining action stages.