FinWikiPublic-source finance field guide
日EN

Coinbase AgentKit & Agentic Wallets · MPC agent wallets on Base

ConfidenceLikely
Updated2026-07-03
Review by2027-01-03
Sources10Machine-translatedOriginal (JA)
#agent-economy#coinbase#agentkit#agentic-wallets#x402#base
On this page

Wiki route

This entry sits under agent-economy index as the Coinbase-specific note on agent wallets and agent payments. Read it with Coinbase CDP for the broader developer-platform substrate, x402 for the HTTP payment protocol, ERC-4337 account abstraction for agents for adjacent wallet-permission design, and Privy embedded wallets for the main embedded-wallet peer.

Key facts

  • Coinbase launched AgentKit on 2024-11-08 as a CDP framework for AI agents that need to perform onchain operations such as transfers, token swaps, and smart-contract interactions. •
  • The current coinbase/agentkit repository describes AgentKit as CDP’s toolkit for giving AI agents a crypto wallet and onchain interactions, with framework-agnostic and wallet-agnostic integration. •
  • Coinbase introduced Agentic Wallets on 2026-02-11 as wallet infrastructure built specifically for agents, distinct from the general CDP platform entry and from the open AgentKit framework. •
  • Agentic Wallets are exposed through two product surfaces: an Agentic Wallet CLI using awal commands and an Agentic Wallet MCP server / companion app for MCP-compatible agents such as Claude, Codex, and Gemini. •
  • Coinbase’s Agentic Wallet pages position x402 as the core payment standard, state that x402 had processed more than 50M transactions, and emphasize machine-to-machine payments, API paywalls, and programmatic resource access. •
  • Coinbase’s product page says Agentic Wallets support gasless trading for any token on Base; the MCP documentation also lists automatic payments on Base, Polygon, and Solana. •
  • The official 2026 CDP Wallets v2 security story is TEE / enclave isolation plus programmable policy controls, not a current MPC key-shard model: Coinbase’s CDP Wallets launch states “no MPC, no key shards,” while noting that the previous Wallet API v1 was MPC-based. •
  • “MPC agent wallets” is therefore best treated as a legacy / category shorthand or Coinbase cryptography background, while the verified Agentic Wallet launch claim is CDP Wallets + TEE isolation + session and transaction guardrails. •
  • Competitive positioning: Coinbase bundles open AgentKit actions, CDP wallet security, x402 payment discovery, and Base gas abstraction; Privy emphasizes embedded-wallet UX across apps, while Circle Wallets emphasize USDC-native wallet APIs secured by MPC or passkeys depending on product. •

Mechanism / How it works

AgentKit and Agentic Wallets are adjacent but not interchangeable. AgentKit is the open-source agent framework layer: it exposes wallet providers, action providers, and framework adapters so an AI agent can call onchain actions from LangChain, Vercel AI SDK, MCP, or another runtime. The GitHub repository is explicit that the design is both framework-agnostic and wallet-agnostic; in practice, the same agent action layer can sit on CDP wallets, smart wallets, Privy, viem, or a custom provider.

Agentic Wallets are the productized wallet surface Coinbase built for autonomous agents. The CLI path is for developers who want to install wallet skills and call awal commands from an agent workflow: authenticate, fund, send, trade, and pay for x402 services. The MCP path is for users of MCP-compatible clients who do not want to wire code: npx @coinbase/payments-mcp installs a local MCP server and companion wallet app, then the agent can discover x402 services and pay for API calls from the wallet context.

The security boundary is the wallet layer, not the prompt. Agentic Wallets inherit CDP non-custodial wallet infrastructure: requests are authenticated, policy-checked, and forwarded into a Trusted Execution Environment for private-key operations. The user or operator keeps control over session caps, per-transaction limits, transfers, and onramp flows; the LLM sees tools, not raw key material. This matters because agent wallets fail differently from human wallets: the main risk is not only key theft, but prompt-injection or tool-routing errors that try to spend outside the task boundary.

x402 is the transaction rail that makes the wallet agent-native. Instead of pre-registering for every API, an agent can receive an HTTP 402 payment requirement, authorize a small stablecoin payment, and continue the request. Agentic Wallet MCP wraps this pattern for MCP clients: the agent discovers paid services, pays with USDC on supported networks, and returns the data to the user. On Base, Coinbase adds the gas-abstraction path that keeps the agent from needing native ETH for every operation, which is especially important for low-value API and compute payments.

The “MPC” wording in the title should be read carefully. Coinbase does maintain an open MPC cryptography stack, and older CDP wallet materials reference Wallet API v1 as MPC-based. But the verified Agentic Wallet / CDP Wallets v2 architecture Coinbase documents in 2026 is enclave / TEE based and explicitly contrasts itself with MPC key shards. For factual use, this entry treats MPC as a historical comparison point and uses TEE + policy guardrails as the current product architecture.

Origin & evolution

The sequence is: AgentKit first, Agentic Wallets second. Coinbase launched AgentKit in 2024-11 as a framework for putting onchain actions inside AI agents. That launch solved the developer-tooling problem: how an agent calls transfer, swap, deploy, or smart-contract actions through a normal AI framework.

CDP Wallets then supplied the automation-grade wallet substrate. Coinbase’s 2025 CDP Wallets v2 launch reframed wallets for backend systems, bots, and agents: create and sign through scoped APIs, keep sensitive operations inside AWS Nitro Enclaves, and enforce wallet policies before signing. That is distinct from the earlier MPC-based Wallet API v1 path and is the reason an agent wallet can be described as programmable custody rather than a prompt-held hot key.

Agentic Wallets, launched on 2026-02-11, packaged those pieces for autonomous money movement. It adds the agent-facing distribution surfaces – awal CLI and MCP server – and anchors the payment use case around x402 and Base. Strategically, Coinbase is trying to own the “agent has a wallet and can pay now” default for crypto-native agents, not just the generic Web3 developer platform.

Against Privy, Coinbase’s edge is the Base + x402 + CDP integration loop; Privy’s edge is embedded-wallet distribution and Web2-style onboarding across consumer apps. Against Circle Wallets, Coinbase is less a neutral USDC wallet API and more a vertically integrated agent-commerce stack: Base execution, x402 discovery, wallet policies, and CDP telemetry in one bundle. Against Skyfire, Coinbase is open stablecoin / onchain-native infrastructure rather than a card-network closed loop.

Sources

Discovery

Keep reading

Related

Read next