Vault Agent vault selection

Vault selection is a sequence of execution checks, typed rules, score adjustments, and portfolio constraints—not a single APY ranking.

Candidate universe

Autoseek starts with active vault options for the agent’s base asset. It removes experiment-blocked and permanently disabled vaults, then filters targets for the wallet’s execution path, such as registered adapters or approved addresses. The public vault-options list is not a promise that every returned vault will be eligible for an agent.

Rule filters and presets

The Vault Agent’s registered rule types include:

• ignored_vault and vault_type_filter to exclude addresses or vault types
• collateral_exclusion to exclude vaults with specified collateral exposure
• liquidity_filter to require minimum total deposits, withdrawable value, or withdrawable ratio
• capacity_cap to cap a vault’s allocation using its deposits and configured capacity factor
• liquidity_allocation_filter to cap an allocation relative to withdrawable liquidity
• forced_vault_allocation to request a target for a vault, subject to eligibility, capacity, remaining balance, and the portfolio’s vault-count limit
• yield_curve_scoring to adjust a model score for yield-curve and stability inputs; it is registered but not memory-compilable

The explorative preset is the default when an agent is created without one; conservative is the other supported preset. Presets generate platform defaults rather than saved user rules. GET /v1/users/{userId}/agents/{agentId}/memories/effective-rules returns userRules and defaultRules separately; a user rule replaces a default of the same type.

Scoring and allocation

Eligible options receive inference-model scores, which an optional yield-curve rule can adjust. The engine evaluates candidate allocations using those scores alongside liquidity and concentration risk and estimated transition costs. It also respects vault-count and capacity limits, so a high-scoring vault may receive only part of the portfolio or no allocation.

Monitoring boundaries

Some rules also produce measurable boundaries for held vault positions, including liquidity, capacity, and collateral limits. The Vault Monitor checks those boundaries continuously; a triggered breach can make the agent eligible for an early Autoseek run that bypasses the normal frequency limit. Monitoring itself does not select or execute an allocation.

Inspecting current data

Use the current effective-rules and vault-options API responses instead of hard-coding profile defaults, availability, APY, liquidity, or rewards. The list endpoint does not force a refresh, and these values can change.

See Vault Agent decision pipeline for how the engine combines these inputs and Vault Agent preferences for user-facing configuration.