Coinbase Developer Platform supplies the embedded wallet and delegated-signing infrastructure. Otto provides the workflow and its own checks. You choose whether to grant a permission and when it expires.
When this flow is enabled, the controls below sign you into a CDP embedded account on Base. Check its displayed address: a connected wallet or legacy funding Safe can be a different account.
The transfer control below reviews Base USDC sent to an external wallet. It requires revoked permission, resolved transactions and enough ETH for network fees. Card funding through the legacy dashboard does not fund this account.
You do not need a coinbase.com exchange account. Signing in does not grant trading permission.
Know who enforces each limit.
When enabled, Otto’s policy review describes USDC swaps through LI.FI on Base and the supported Morpho vault operations. Coinbase’s project policy carries the shared $5,000 ceiling. A lower amount you choose, and the destination of the output, are checked by Otto’s server.
The cap is per swap, not a daily budget or a lifetime loss limit. Repeated actions can use more capital.
Stopping and moving funds are different steps.
01
Expiry or revoke
The grant ends at its recorded expiry, or you can revoke it earlier. Revocation prevents future delegated signing; it does not undo a submitted trade or cancel signatures already created.
02
Withdraw a vault position
A supported vault withdrawal returns USDC to the same delegation account. Stopping Otto does not automatically close the position.
03
Move USDC out
After resolving existing transactions and revoking permission, review a separate Base-USDC transfer below. Confirm the account, destination, amount and network fee before signing. A submitted transfer stays unresolved until its receipt is verified.
Review the account, policy and availability shown below before granting permission. Coinbase infrastructure does not guarantee Otto’s checks, investment returns or protection from losses.