agentwallet.ai
AI agent wallet

A wallet for each AI agent, not a shared card.

Every agent gets its own balance, transaction history and limits. Funds flow down from your account through a principal, so you always know who an agent spends for and how much it can spend.

Request access →Wallet product tour

AgentWallet is invite-only. Request access and we will follow up.

In short

An AI agent wallet is a balance that belongs to one agent, with its own ledger and spending rules. In AgentWallet it sits under a principal (the accountable owner) and an account (your organisation), and an agent can only spend what has been allocated to it.

How it works

From account balance to agent spend.

  1. Fund the account

    Balances are held at the account level and shown per currency.

  2. Allocate to a principal

    Move funds to the principal responsible for a group of agents.

  3. Allocate to the agent

    The agent now has its own spendable balance and ledger.

  4. Agent spends through tools

    Via MCP or REST the agent checks its balance, pays with its card or requests a payout.

  5. Limits and approvals apply

    On gated tools such as agent_purchase, per-transaction, daily and monthly caps are checked before money moves; above them, a human approves. Card purchases also draw on the card's own loaded balance.

Capabilities

What each agent wallet includes

Verified against the current platform, not a roadmap.

Balance

Own balance

Allocated from its principal; never pooled with other agents.

Ledger

Transaction history

Wallet allocations and supported payout operations have ledger entries; card purchases can be recorded as activity rather than wallet spends. Review records through agent.transactions.

Limits

Spending caps

Per-transaction, daily and monthly USD limits on the agent.

Card

Virtual card

Optional card with its own authorization rules.

Identity

Agent passport

An identity record and optional on-chain registration (currently on Base Sepolia testnet).

Tools

MCP endpoint

A per-agent MCP server exposing balance, card, purchase and payout tools.

Use cases

Why teams give agents their own wallet

Isolate blast radius

If an agent misbehaves, freeze or drain that one wallet. Others keep working.

Attribute cost

See exactly what each agent spent and for which principal, without tagging a shared statement.

Delegate safely

Hand a research or purchasing agent a small allocation instead of a company card.

Give agents context

Agents can read their own balance and history before they decide to spend.

For developers

Wallet operations over REST and MCP.

Agents use MCP tools; your backend uses the REST API.

  • POST /api/principals/:id/allocate and POST /api/agents/:id/allocate to move funds down the tree
  • GET /api/agents/:id/overview for balance and status
  • GET /api/ledger for the account ledger
  • MCP tools agent.balance, agent.transactions, agent.card
DocsWallet for agentsPrincipalsMCP endpointOpenAPI spec
# Management API (dashboard session)
POST /api/agents/$AGENT_ID/allocate
{ "amount": 250, "memo": "May research budget" }

# Agent reads its own balance with a pak_ key
curl -X POST https://agentwallet.ai/api/tool-api/invoke \
  -H "Authorization: Bearer pak_…" \
  -d '{"name":"agent.transactions"}'

# From inside the agent (MCP)
tools/call agent.balance
Security & controls

A wallet the agent can use but not escape.

The agent acts through scoped tools; on gated tools, limits and approvals are enforced server-side. The generic x402.pay_url tool is not cap-gated; withhold the x402:pay scope if you rely on caps.

Parent bounds

An agent can never exceed its principal, and a principal never exceeds the account.

Approval on overflow

On gated routes, spends above a cap return approval_required instead of failing silently.

Scoped access

MCP access is scoped per agent; OAuth is available for MCP clients.

Full history

Holds and captures are recorded, including capture-at-actual for browser checkouts.

FAQ

Questions developers ask

What is an AI agent wallet?

A balance, ledger and set of spending rules that belong to a single AI agent, so it can pay for things without holding company-wide credentials.

Can an agent top itself up?

No. Funds are allocated down from the account and principal. The agent can request approval for a spend but cannot move money into its own wallet.

Is the agent wallet a crypto wallet?

It is primarily a ledger balance. Agents can also have on-chain identity and USDC capability; see stablecoin wallets for agents.

Who can use AgentWallet today?

Access is invite-only while we onboard teams. Request access from any page; sign-up is enabled per email or domain once you are approved.

Do you guarantee availability in my country or a specific settlement time?

No. Supported rails, currencies and timing depend on the underlying banking, card and payout partners for your account. We confirm what is available for your account during onboarding rather than promising it upfront.

Explore the stack

AI agent financial infrastructure

Every page in this set covers one layer. Start at the hub for the full map.

Financial infrastructure hubThe whole stack, one mapAI agent walletA balance and identity per agentProgrammable walletsWallets you drive from codeAgent paymentsCards, payouts, x402, ACPVirtual cardA card per agent, policy-boundStablecoin walletsUSDC on Base for agentsSpending controlsCaps, approvals, card rulesAgent payment APIREST, MCP, webhooks

Give your first agent a wallet.

Request access to create principals, agents and allocations in the dashboard or over the API.

Request access →Read the docs