Skip to content

Agent Wallet Overview

Akita Agent Wallet lets any LLM-powered agent send payments, stake tokens, trade NFTs, vote in DAOs, and more — all through a sandboxed escrow with spending limits set by the wallet owner.

Built on the ARC-58 abstracted account standard, with transaction signing powered by Intermezzo (HashiCorp Vault).

┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ AI Agent │─────>│ Agent Kit │─────>│ Intermezzo │─────>│ Algorand │
│ (Claude, etc)│ │ (Actions) │ │ (Vault) │ │ (ARC-58) │
└──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
  1. The wallet owner creates an escrow on their ARC-58 wallet and assigns the agent’s key
  2. The owner configures plugins (pay, stake, swap, etc.) and spending allowances
  3. The agent uses the SDK to execute actions — each action goes through the escrow’s plugin system
  4. Transactions are signed by Intermezzo (Vault) using the agent’s key, never exposed to the agent
PackagenpmDescription
packages/core@akta/agent-walletCore SDK — AgentKit, action providers, wallet providers
packages/mcp@akta/agent-wallet-mcpMCP server for Claude Desktop and other MCP clients
packages/cli@akta/agent-wallet-cliInteractive setup wizard and CLI tools

The agent wallet uses a layered security model:

  • ARC-58 Escrow — The agent operates within a sandboxed escrow. The escrow can be locked or revoked at any time by the wallet owner.
  • Plugin System — Each action (pay, stake, swap) is a plugin that must be explicitly installed. The agent can only execute actions for installed plugins.
  • Spending Allowances — The wallet owner sets spending limits (flat, window, or drip) per asset. The agent cannot exceed these limits.
  • Vault Signing — The agent’s private key never leaves HashiCorp Vault. Transactions are signed remotely via the Vault transit engine.
  • Intermezzo Auth — Two-step authentication (Vault AppRole + Pawn JWT) with automatic token caching and renewal.