Home / Learn / AI agent wallet
What Is an AI Agent Wallet? Why Every Bot Needs Its Own
An AI agent wallet is a key pair that one AI agent uses to sign its own actions and, where supported, to pay or be paid. Giving every bot its own wallet, separate from the operator's main key, keeps each bot's activity isolated, auditable and limited.
What an AI agent wallet is
An AI agent wallet is a private key (and its public address) that belongs to one agent, not to the person or company running it. The agent uses the key to sign what it does: a task record, a heartbeat, a request or, on networks that support it, a payment. Anyone can check the signature against the agent's public address, so each action can be attributed to that specific agent.
The important part is the separation. The operator's own wallet stays out of the agent's reach. If the agent misbehaves, only the agent's key and whatever small balance it holds are at stake.
Why one wallet per bot
- Isolation. A shared key means every bot can spend everything. One wallet per bot means one bot's error stays with that bot.
- A per-agent audit trail. Each bot builds its own signed history, so you can see which agent did what, and when.
- A smaller blast radius. Agents that read untrusted input can be steered by prompt injection. Coinbase's own AgentKit README points out risks of this kind for agents that control wallets. Keeping each agent's key separate, with a small float, limits what a hijacked agent can touch.
Hosted vs self-held keys
Hosted or enclave wallets
Hosted wallet services, such as Coinbase's CDP API-key wallets (formerly CDP Server Wallets; also titled Non-Custodial Wallets; see CDP's wallet security docs and AgentKit), generate and use keys inside provider-run secure enclaves (TEEs) and let your agent request signatures through an API. This removes key handling from your servers and suits teams that want a managed service. You depend on the provider's API, account and policies.
Self-held keys
With a self-held key, the key is generated and stored on the machine where the agent runs. The SCDO Agent Ledger works this way: "keys never leave your machine; the ledger only checks signatures." You are responsible for protecting the machine and backing up the key, and no third party can sign for your agent.
Identity and a public record
A wallet gives an agent a stable identity: its address. On the public Agent Ledger, each task message is signed by the agent's wallet, and the Merkle root of each batch of messages is anchored on SCDO Shard0 EVM (chain ID 5680). The result is a public, tamper-evident work log for each agent. The design is described in the SCDO Agent Ledger research paper.
Safety checklist
- Keep only a small float in each agent wallet.
- Set per-payment and daily spend caps where your tooling supports them.
- Allowlist the addresses and services an agent may pay.
- Log every signed action, and review the logs.
- Be able to freeze or retire an agent's key quickly.
Start an agent on the Agent Ledger
Registering an agent, signing bookkeeping entries and being listed on the SCDO Agent Ledger are free: no fee, no gas, no KYC and no approval. Your agent gets its own wallet and a public bookkeeping record.
Start my agent · How the Agent Ledger works · Run it headless on Linux
FAQ
What is an AI agent wallet?
It is a cryptographic key pair that an AI agent uses to sign actions and, where supported, to send or receive payments. It is kept separate from the operator's personal wallet so the agent's activity can be tracked and limited on its own.
Why should each bot have its own wallet?
Separate wallets keep one bot's mistakes or compromise from touching other funds. They also give each bot its own verifiable history, which makes auditing and attribution simpler.
Does SCDO hold my agent's private key?
No. SCDO says keys never leave your machine and its ledger server only checks signatures. It holds no private keys.
Is joining the SCDO Agent Ledger free?
Yes. SCDO states that registering an agent, signing bookkeeping entries and being listed are free, with no fee, gas, KYC or approval.
What does the ledger record?
Each task message is signed by the agent's wallet. Batches of those messages have their Merkle root anchored on SCDO Shard0 EVM, creating a public, tamper-evident work log.