Vault Agent monitoring
Monitoring continuously checks measurable limits in the Vault Agent’s effective rules against live data for vaults it holds. It tracks rule boundaries; it does not rank candidate vaults or decide where funds should move.
What’s monitored
Section titled “What’s monitored”Supported rules with measurable conditions can create boundaries for each held vault. Current Vault Agent boundaries can watch:
- Available liquidity and its ratio to vault deposits.
- Total deposits in the vault.
- Collateral assets you have excluded.
Capacity and position-size rules can also set boundaries tied to the size of a held position. Not every rule has a monitorable condition, so not every active rule creates a boundary.
A numeric boundary breaches at its configured threshold; monitoring also sets a warning boundary at 1.25× that threshold. For lower-limit rules, the warning can show that a vault is approaching your line before the breach threshold is reached. A collateral boundary is breached when the vault uses an excluded asset.
Status on the agent overview
Section titled “Status on the agent overview”The overview shows boundaries as:
- Clear — no warning or breach condition is active.
- Approaching — a warning threshold is reached, or the observed trend projects a breach. A projected breach is labeled confirming breach in the UI.
- Breached — the rule’s breach condition is reached.
You can see the status and any flagged boundary details on the agent overview, beneath its holdings.
When the agent acts
Section titled “When the agent acts”A triggered breach makes the agent eligible for its next Autoseek run early, bypassing its usual frequency limit. It does not start an immediate run or guarantee a particular action. Monitoring itself does not decide on an allocation, execute a transaction, or send a user notification.
What Autoseek re-checks on every run
Section titled “What Autoseek re-checks on every run”Monitoring watches your limits between runs; Autoseek, the Allocation Engine, re-evaluates your whole position each time it runs. Managing your funds doesn’t stop at the first allocation. On each run it looks at:
- Yield and liquidity — current rates, available liquidity and deposit capacity for your positions and the alternatives.
- Rewards — which accrued rewards are worth claiming and converting; small or unsupported rewards are skipped.
- Eligibility — whether each vault is still active and registered with an approved adapter. Vaults that no longer qualify drop out of the candidates.
- Your whole portfolio — concentration and diversification across the agent, not just one position, together with your profile and preferences.
A rebalance, exit, or reward claim is only made when the expected benefit justifies the transaction cost and stays within your rules; a run can also keep your current allocation. See the decision pipeline for how those choices are made.
Verify, don’t trust
Section titled “Verify, don’t trust”Wherever practical, YieldSeeker reads protocol state from the protocols’ own contracts, such as available liquidity, deposits, and adapter registrations, rather than relying only on third-party dashboards. This keeps decisions grounded in current onchain state. See Architecture.
Platform safety controls
Section titled “Platform safety controls”Some safety controls apply to every agent and cannot be overridden by your profile or preferences. If a vault or protocol presents an unacceptable risk, such as a security incident, YieldSeeker can make it ineligible platform-wide. Agents then stop allocating to it and move out of it on their next run, where liquidity allows. Registry-level emergency controls are described in Governance.