Skip to main content
Agentic Wallet supports managing multiple AI agents simultaneously, each with independent wallets, capabilities, and budget controls. This enables complex multi-agent workflows with treasury management and coordinated actions.

Overview

Multi-agent orchestration provides:
  • Independent Wallets: Each agent has its own custody boundary
  • Capability Isolation: Per-agent intent and protocol allowlists
  • Budget Management: Treasury allocation and rebalancing between agents
  • Autonomous Coordination: Agents can transfer funds and trigger workflows
  • Execution Modes: Supervised or fully autonomous operation
The demo script scripts/devnet-multi-agent.ts showcases a complete multi-agent workflow.

Creating Multiple Agents

Each agent requires a wallet, capabilities, and execution mode configuration.

Agent Creation Workflow

1

Create first agent

Response includes:
2

Create second agent

3

Start both agents

Using the SDK

Treasury Allocation

Distribute funds from a treasury source to agent wallets.

Direct Allocation

Allocate SOL to an agent without a source (increases total budget):

Allocation from Source Agent

Budget Rebalancing

Transfer budget between agents to optimize capital allocation.

Rebalance Workflow

Response:

Using the SDK

Rebalancing only adjusts budget tracking. You must separately execute on-chain transfers if physical SOL movement is required.

Coordinating Agent Capabilities

Capability Profiles

Design agents with specialized roles:

Updating Capabilities

Autonomous Coordination Example

The devnet-multi-agent.ts script demonstrates end-to-end orchestration:

Running the Demo

Expected output:

Budget Management

Query Agent Budget

Response:

Budget Enforcement

Agents automatically reject intents that exceed remaining budget:

Advanced Patterns

Leader-Follower Architecture

Round-Robin Load Distribution

Observability

Agent Audit Trail

Transaction History per Agent

Multi-Agent Metrics

Filters available:
  • agentId
  • protocol
  • status (confirmed/failed)
  • startDate/endDate

Security Considerations

Multi-Agent Security Best Practices:
  • Use separate API keys per agent for revocability
  • Set conservative budget caps on autonomous agents
  • Require approval gates for high-value operations
  • Monitor cross-agent transfer patterns for anomalies
  • Implement rate limits per agent

Capability Manifests

For production deployments, issue signed manifests:
Enable enforcement:

Next Steps

Strategy Backtesting

Test multi-agent strategies before live deployment

Gasless Transactions

Enable gasless execution for agent operations