What wallet does an AI agent need for x402?
Short answer
Any wallet that can sign from code and holds the token the seller accepts, usually USDC. The simplest is a private key loaded by a library. Safer options are managed wallets, where a provider holds the key and enforces spending rules, and wallets that connect to an assistant through MCP with a budget. The choice is mostly about who holds the key and what limits apply.
What the wallet has to do
An x402 payment is a signature. The agent's wallet must be able to:
- Sign without a person clicking a button. A browser extension that pops up a confirmation window does not work for an unattended agent.
- Hold the right token on the right network. Most sellers ask for USDC. The official quickstart lists the requirement as a wallet with USDC on an EVM or Solana network.
- Sign the right kind of message. On EVM networks that is a typed message (EIP-712). On Solana it is a transaction.
The wallet does not normally need the network's own coin for fees. See fees and gas.
The main kinds
| Kind | Who holds the key | Limits | Fits |
|---|---|---|---|
| A private key in the agent's environment | You | Only the wallet's balance | Tests, and small budgets you can afford to lose |
| A managed or embedded wallet | A provider, on your behalf | Rules set through the provider: amounts, recipients, approvals | Production agents |
| A wallet connected through MCP | A provider | A budget you approve | Assistants such as Claude that call tools for you |
| A command-line wallet | You, on your machine | You approve each use, or set a policy | Developers working in a terminal |
| A control layer above the wallet | Varies | Per-agent budgets, policy checks, an audit trail | Teams running many agents |
The x402 FAQ names programmatic wallets such as the CDP Wallet API, viem and ethers for EVM networks, and @solana/kit for Solana.
Specific products of each kind, with links to their own documentation, are in the wallets section of the directory.
What to look for
- A spending ceiling. Per request and per day. An agent will pay any price it is told to unless something stops it.
- Who can move the money. With a raw key, anyone who reads the key can. With a managed wallet, the provider's rules apply first.
- Network coverage. A wallet that only works on EVM networks cannot pay a seller that only takes Solana, and the reverse.
- Scheme coverage. Almost every endpoint uses the
exactscheme. If you needuptoorbatch-settlement, check the wallet and client support them. See payment schemes. - A record of what was paid. You will want to see where the money went.
Funding it
The wallet needs tokens before the agent can pay. Send USDC to the wallet's address on the network your sellers accept. Start with a small amount. The balance is the most the agent can lose.
To find out which network a seller wants before you fund anything, paste its endpoint into the 402 checker.
A safe starting setup
- Create a wallet used only for this agent.
- Put a few dollars of USDC in it.
- Set a maximum price per request in the client.
- Try it on a test network first. See testing x402 without real money.
- Read is x402 safe? before raising the budget.
No wallet at all?
Some services can be used without one. See using x402 services without a crypto wallet.
Sources
- x402 FAQ
- Quickstart for buyers, x402 documentation
- Coinbase agentic wallet documentation
- Turnkey, agentic payments
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.