Skip to content

Agent types

An agent type defines what an agent is trying to achieve, which actions it can take, and which results and risks matter.

Vault Agent

Section titled “Vault Agent”

The Vault Agent is the only currently available type.

Its goal is to allocate a supported base asset across approved DeFi vaults to pursue risk-adjusted yield. Vault Agents use Autoseek to evaluate opportunities, manage positions, and compound supported rewards.

Current support

Section titled “Current support”
Capability Current status
Agent type Vault Agent
Primary goal Risk-adjusted yield
Current network Base
Base assets accepted by the current API USDC, WETH, and cbBTC on Base; a specific asset is usable only while the API exposes an enabled opportunity
Main opportunities Approved DeFi vaults
User controls Profiles, preferences, memories, withdrawals, and deactivation
Main metrics Balance, positions, earnings, APY, and allocation history

The API and product configuration decide whether a specific asset or opportunity is enabled. A token supported by the wallet contracts does not automatically mean that every agent type can use it.

Current protocol integrations

Section titled “Current protocol integrations”

Vault Agent opportunities are currently reached through adapters for Aave V3, Compound V2, Compound V3, and generic ERC4626 vaults — which covers providers such as Morpho and Spark — with Aerodrome and Uniswap V3 used for reward-token swaps and Merkl for reward claims.

Availability changes as vaults are approved, paused, or blocked (for example after a protocol incident). Use the vault opportunities endpoint or the app for the current live list rather than this page.

Future agent types

Section titled “Future agent types”

Additional types may pursue different objectives, such as borrowing or basis-trade strategies. They may have different:

  • funding and activation flows
  • supported assets and networks
  • permitted actions
  • performance metrics
  • user controls
  • risks and exit conditions

Future types will be documented as separate pages after their names, behavior, and launch scope are finalized.

Choose the right guide

Section titled “Choose the right guide”