Coinbase Agentic Wallets: Bounded Payment Access for AI Agents

Your research agent needs a paid data API. You want it to make a $1 purchase without giving it a key that can freely transfer all your funds. Coinbase Agentic Wallets aims to let agents use on-chain funds with spending boundaries.

Evidence: Based on Coinbase’s public documentation reviewed October 28, 2026. This scenario is illustrative; we did not create a wallet or make a payment. Verify current capabilities, fees, regions and terms.

What is offered?

Coinbase describes a set of tools for agents to hold, spend, trade and earn stablecoins, with a command-line and Agent Skills path and an MCP path for compatible clients. Their capabilities differ. See the official overview.

Entry point	Intended user	Documented capabilities
CLI and skills	Developers building or running agents in code	Authenticate, send, trade and pay for x402 services
MCP and companion wallet app	MCP-compatible agent clients	Discover and pay for x402 services; the overview says this path does not provide send and trade

CLI is a command-line entry point; skills guide agent tool use; MCP lets compatible clients call external tools. None is itself an independent payment network.

flowchart LR U[User sets task and permissions] --> A[Agent discovers paid data] A --> X[x402 returns payment requirements] X --> W[Wallet checks and prepares payment] W --> V[Payment verification and settlement] V --> D[Provider delivers data] D --> R[Agent records and reports]

This is conceptual. A wallet that can pay does not guarantee data quality, merchant performance or automatic refunds. The x402 V2 overview describes discovery extensions; verify each endpoint’s price, network and delivery terms.

Who controls funds and permissions?

Coinbase’s product page describes per-transaction and session spending limits, private keys retained in secure Coinbase infrastructure and not directly exposed to agent prompts or models, and transaction screening. These are provider claims, not independent tests or guarantees against loss.

Distinguish where keys live from who may approve actions. Accounts, sessions and administrative permissions that call the wallet also need protection. Ask:

Do limits cover every operation, asset and network? How are sessions reset and cumulative limits calculated?
Who can change limits or recover an account? Can the agent change rules?
What happens to prior signatures, contract approvals or broadcast transactions after revocation?
What do the agent and user see when screening rejects a transaction?

Verify against the chosen integration.

Do not conflate every CDP wallet

Coinbase also has CDP Wallet APIs. Its documentation describes an API Key Wallet controlled by a developer’s server with keys protected in a CDP trusted execution environment. That does not make its user experience or permissions identical to Agentic Wallets CLI or MCP. Check account types, authentication, networks and fees separately.

Dimension	What the sources describe	Verify before use
Use case	Agent stablecoin use and x402	Whether the target service accepts the asset and network
Entry points	Different CLI/skills and MCP capabilities	Client and version compatibility
Spending controls	Provider describes transaction and session limits	Coverage, defaults, change and revocation
Costs	“Gasless” does not prove every cost is zero	Network and service fees, conversion spread and pricing
Availability	Documentation at review date	Location, identity checks and eligibility

An agent buying x402 APIs may warrant evaluating MCP; for broader on-chain workflows, examine CLI. Card shopping, cross-method orchestration and accounting integrations require separate verification.

A trial could record setup and a successful call, then separately test overspending, insufficient funds, timeouts and revocation, noting assets, network, costs, time and status. This article has not performed those tests. See also Circle’s product analysis.