Agent type integration contract
An agent type defines a strategy runtime inside the shared YieldSeeker account, wallet, authorization, and safety model.
Required type definition
Section titled “Required type definition”Every type should specify:
- a stable type identifier
- its goal and success metrics
- supported chains and assets
- creation and activation fields
- permitted operations
- monitoring data and status states
- user controls and exit behavior
- API errors and retry/idempotency rules
- strategy-specific risks
Shared platform boundary
Section titled “Shared platform boundary”A type does not receive unrestricted wallet access. It operates through the same ownership, authorization, adapter, registry, and emergency controls described in Security and AgentWalletKit integration.
Current type
Section titled “Current type”vault is the currently available type. It allocates supported assets across approved DeFi vaults and exposes Vault Agent-specific yield, position, and Autoseek operations.
See Creating an agent via API and Vault Agent API integration.
Adding a future type
Section titled “Adding a future type”A future borrowing, basis-trade, or other type should be added as a sibling integration with its own API guide, user guide, metrics, risk disclosure, and support matrix entry.
Do not make Vault Agent fields, APY metrics, vault addresses, or rebalance semantics mandatory for every type.