Shareable BAY Buddy position
A public, read-only view of vault shares, net USDC value, pending withdrawals, and the on-chain event timeline for one depositor.
—
Async withdrawal status
Track a vault withdrawal from request observation through actionable finality, liquidation, settlement, and durable closure.
—
The yield layer for autonomous agents.
BAY Buddy turns idle USDC into a transparent, vault-backed yield position through one agent-friendly integration. The first deployment is live on Base across Aave, Morpho, and Compound, with HTTP-native x402 deposits for clients that want to fund yield directly through a 402 payment flow.
Built where agents and APIs transact
Agents can discover BAY Buddy, coordinate investment intent, and receive a canonical deposit transaction hash through open agent commerce standards. HTTP clients can also deposit through a vanilla x402-style 402 challenge.
Vault custody users can verify
USDC moves into an ERC-4626 vault and shares mint directly to the depositor. The agent routes the transaction; it never becomes the custodian.
One flow, many yield markets
Generic execution and valuation adapters let BAY Buddy add new USDC markets while keeping the depositor experience and API surface consistent.
The live Base vault proves the model with real on-chain balances, venue telemetry, async USDC withdrawals, and performance fees only when depositors earn net new profit above their high-water mark.
How agents use BAY Buddy
BAY Buddy turns an agent investment flow into four simple steps: discover the service, confirm intent, submit a signed USDC authorization or x402 payment, then track or withdraw the resulting vault shares through the public API.
-
Discover & negotiate
Find BAY Buddy on the agent registry
Resolve BAY Buddy through
ERC-8004, read itsagentURI, and open anERC-8183ACP job. ACP coordinates the commercial intent; capital moves only when the depositor signs the ERC-3009 authorization. -
Deposit
Sign once, deposit immediately
The standard agent path signs an
ERC-3009authorization off-chain, so no token approval is needed. HTTP-native clients can instead callPOST /v1/x402/deposit, receive a 402 payment challenge, and retry withPAYMENT-SIGNATURE. In both paths, vault shares mint directly to the depositor. -
Earn
Capital routes across venues
The Base vault currently allocates USDC across Aave, Morpho, and Compound. Depositors participate through share price, while lot-level high-water mark accounting keeps the 15% performance fee tied to net new profit.
-
Withdraw
Async settlement by shares
Depositors receive vault shares as an accounting claim on their USDC position. Shares are not designed for secondary transfer; exits settle back to USDC through the withdrawal flow.
Withdrawals are requested in shares via
vault.requestWithdraworPOST /v1/withdraw. The orchestrator pays from the liquid buffer when possible, or unwinds venue positions in an atomic batch before sending USDC to the receiver.
Vault snapshot
Configured venues
Open a shareable view
Investor position
View net value, fee accrual, venue attribution, pending withdrawals, and on-chain history for a depositor.
Withdrawal status
Follow a request from observation through actionable finality, liquidation, settlement, and durable closure.
API endpoints
-
GET
/v1/statusVault and venue snapshot -
GET
/v1/venuesPer-venue telemetry -
GET
/v1/positions/{ownerAddress}Depositor position decomposition -
GET
/v1/history/{ownerAddress}Depositor event timeline -
GET
/v1/withdrawals/{requestId}/statusPublic withdrawal tracker state -
POST
/v1/depositPre-signed ERC-3009 deposit relay -
POST
/v1/x402/depositHTTP 402 one-shot USDC vault deposit -
GET
/v1/x402/deposit/{quoteId}x402 settlement status by quote -
POST
/v1/withdrawPre-signed withdrawal relay