Skip to main content

​
Key Capabilities

  1. Deposit & Earn: Otto’s discovery service compares eligible lending and staking markets across its active protocol adapters and ranks them by net APY. From /app Mission Control, the Featured Yield card shows live stablecoin discovery rows. Its deposit control is available only when the current top row exactly matches one of three server-registry markets: Aave V3 Base USDC, Morpho Gauntlet USDC Prime on Base, or Morpho Steakhouse Prime USDC on Base.
  2. AI-Powered Vault Selection: Active discovery reads Aave, curated Morpho vaults, Syrup (Maple), and Lido. Compound’s adapter is currently dormant. Markets are ranked by net APY; rows with reported TVL below $1 million or APY above 50% are filtered out as data-quality checks. The DApp does not accept an arbitrary protocol or vault address for execution.
  3. Withdraw Anytime: The registry-bound server rail supports deposits and withdrawals for its exact Aave and Morpho markets. The current Featured Yield card exposes deposits only; it does not yet expose a withdrawal control.

​
Supported Protocols

​
Supported Tokens

Discovery admits configured stablecoins plus ETH, WETH, stETH, and wstETH. The Featured Yield feed requests stablecoin markets, and its registry-bound execution asset is USDC on Base.

​
How to Use (DApp)

  1. Open /app Mission Control and inspect the Featured Yield card. Its venue table is discovery; a row marked discovery-only cannot move funds.
  2. Check eligibility: The deposit input activates only for an eligible top row — one carrying an exact executable-market ID and registry commitment.
  3. Review the target: Confirm the displayed venue, Base USDC asset, APY, and amount. The table is not an arbitrary protocol, chain, or vault picker.
  4. Deploy: Enter the amount and confirm the deposit. The server revalidates the registry identity and calldata before submitting the deposit.
The standalone Yield Copilot mini-agent page remains discovery-only. Registry-bound one-click deposits are live from the Featured Yield card for its current exact Aave or Morpho Base USDC row; auto-rebalance and alerts remain disabled.

​
How to Use (Agent Rails)

For the separate ACP execution rail, request the Trade Execution Agent’s earn_yield service. The main x402 catalog does not expose a matching yield-execution endpoint.
Use acp-cli or the ACP Web GUI for that ACP job. Use x402 for read-only yield discovery; it does not move principal.

​
How It Works

The DApp discovery service reads protocol-native sources: the Aave client, Morpho’s GraphQL API, and onchain Syrup and Lido data. DApp execution uses native Aave or Morpho calldata builders and accepts only an exact server-registry market; the legacy ACP job is a separate rail with its own provider logic. All deposits and withdrawals go through your Safe smart account — agent-custodial on the live rail today (an Otto-managed key signs execution). See Your Safe Account & Custody for how custody works across Otto’s surfaces. You receive yield-bearing tokens (like aUSDC for Aave deposits) as proof of deposit, and you can withdraw through the applicable live-rail path.
For protocol-specific details, see the Aave V3 guide. The DApp shows broader discovery than it can execute: only the exact Aave and Morpho Base USDC registry rows activate the Featured Yield deposit control.