Skip to main content

​
What is a Zap?

In DeFi, a “zap” bundles multiple actions into a single plan. The /app Mission Control does not expose a public bridge-plus-lend or swap-plus-deploy zap workflow. For example, doing this manually is two separate steps:
  1. Bridge: Move 100 USDC from Base to Arbitrum. (Approve + confirm.)
  2. Lend: Deposit the 100 USDC into an Aave pool on Arbitrum. (Approve + confirm.)
Conceptually, a zap could bundle that bridge + Aave deposit. That combined action is not a current Mission Control rail.

​
Key Benefits of Zaps

  • Convenience: A multi-step goal can share one plan.
  • Atomic intent: The steps and final destination can be reviewed together when a rail supports the bundle.
  • Complexity reduction: A zap can hide protocol-specific routing details.

​
Current Otto Flow

Run the supported steps separately:
  • Use the Otto Swap & Bridge Mini-Agent for a swap or cross-chain bridge.
  • Use the /app Featured Yield card only when it shows an exact registry-backed Base USDC Aave or Morpho venue and the unified Otto session is armed.
Do not assume that a bridge quote will redeploy the received asset into a protocol. Verify the completion of the first step before initiating the next supported action.