Overview
Agents are autonomous executors that can perform transactions on behalf of wallets. They operate with capability-gated permissions, budget controls, and support both autonomous and supervised execution modes.Agent Lifecycle
Agents move through these states:Creating Agents
Execution Modes
Autonomous Mode
Agent executes transactions automatically based on its decision engine:Supervised Mode
Agent requires explicit approval for each transaction:approval_gate regardless of policies.
Setting Capabilities
Control which intents and protocols an agent can use:Capability Manifests
Manifests are signed, time-limited capability certificates:1
Issue Manifest
Create a signed capability manifest:Response:
2
Verify Manifest
Verify a manifest’s authenticity:Or from file:
3
Execute with Manifest
The agent runtime enforces manifest permissions at execution time.
Manifests require
AGENT_MANIFEST_SIGNING_SECRET and AGENT_MANIFEST_ISSUER configured. Set AGENT_REQUIRE_MANIFEST=true to enforce manifest validation.Budget Operations
Manage agent spending budgets:Check Budget
Allocate Budget
Rebalance Between Agents
Agent Lifecycle Management
Start Agent
Stop Agent
Pause Agent
Resume Agent
Executing Agent Transactions
Manually trigger agent execution:Autonomy Configuration
Configure autonomous decision-making:Decision Rules
Rules trigger actions based on conditions:lt, lte, gt, gte, eq, ne
Supported metrics:
balance_lamportstoken_balanceposition_valuedaily_pnlprice_deviation
Strategy Steps
Steps define recurring autonomous actions:Paper Trading & Backtesting
Execute Paper Trade
Test strategies without real funds:Backtest Strategy
Replay historical strategy:List Paper Trades
Real Examples from Source
From scripts/devnet-multi-agent.ts
Agent Security
Governance Controls
Next Steps
Protocol Interactions
Learn how agents interact with Jupiter, Marinade, Solend, and more
Setting Policies
Add policy controls to agent transactions