agentwallet.ai
PROTOCOL STACK · LIVE IN PRODUCTION

Three protocols. One wallet.
Route-specific payment authorization.

AgentWallet is the only wallet that ships AP2, x402, and ACP in production. Your agent gets a verified human principal binding, a programmable stablecoin rail, and a merchant-scoped card token — from one endpoint, in one API call.

Get a wallet for your agentRead the protocol docs →

THE PROBLEM

The agent economy needs three things at once.

An autonomous agent doesn't pay one way. It pays APIs, merchants, and other agents — each with different infrastructure, different trust assumptions, different settlement rails. Three protocols have emerged to handle the three flows. Most platforms ship one. We ship all three.

THE PROTOCOLS

One implementation per spec. Availability depends on the configured integration.

AP2 — Google's Agent Payments Protocol
Verifiable proof that a human authorized the agent.
Best for: Procurement agents, B2B payouts, anything that needs human-traceable authorization for a non-human transaction.

AP2 describes signed intent, cart and payment mandates. AgentWallet has signing and verification code for supported flows; this is not a claim that every transaction is signed by a verified human or independently certified as spec-complete.

What AgentWallet ships
  • ✓ECDSA keypair provisioned per agent at signup
  • ✓Public key endpoint for verifier resolution
  • ✓MCP signing tools: agent_sign_intent_mandate, agent_sign_cart_mandate, agent_get_payment_mandate
  • ✓Inbound payment endpoint with full mandate-chain verification
  • ✓Beneficiary resolver, audit trail, key revocation, idempotency hardening
  • ✓AP2 v0.1 spec — fully delivered
x402 — Coinbase's HTTP-native payment protocol
Pay-per-request APIs, with stablecoins, in one round trip.
Best for: API-to-API payments, inference token billing, micro-settlements down to fractions of a cent.

x402 is the protocol where an API returns HTTP 402 Payment Required with a price, and the client attaches a stablecoin payment to its retry. No subscription. No invoice. No human in the loop. Built by Coinbase, already battle-tested across 50M+ transactions.

What AgentWallet ships
  • ✓Native x402 client and server support
  • ✓USDC settlement on Base via Coinbase CDP
  • ✓Gas sponsored — agents never need to hold ETH
  • ✓Per-agent caps enforced at the wallet layer, not the application layer
  • ✓Works with any LLM or framework that can speak HTTP
ACP — Stripe's Agentic Commerce Protocol
A one-time-use card token, scoped to one merchant, one cart.
Best for: E-commerce checkouts, SaaS subscriptions, anywhere the merchant only accepts cards.

Compatible ACP checkout paths can use Shared Payment Tokens or supported stored-card credentials. Merchant support and credential handling depend on the configured path; tokenization does not make leakage or replay universally impossible.

What AgentWallet ships
  • ✓SPT issuance service in production
  • ✓VGS forward-proxy architecture — real PANs never enter the model context
  • ✓Card controls depend on the configured provider and execution path
  • ✓Direct ACP PSP registration with OpenAI in progress; Stripe acts as the intermediate PSP today
  • ✓Works at every merchant that accepts provider-issued card

THE STACK

Three protocols, side by side.

AP2x402ACP
Built byGoogle + CoinbaseCoinbaseStripe + OpenAI
SettlementAny railUSDC on BaseConfigured card program
Best forAuthorization & auditAPI micropaymentsWeb checkout
Trust modelSigned mandatesHTTP-nativeTokenized card
Live on AgentWallet✓ v0.1✓ Production✓ Production

WHY THE COMBINATION MATTERS

No single protocol covers the agent economy.

01

Authorization without rails is theatre.

AP2 proves the agent had permission. But AP2 doesn't move money — it signs intent. You still need a settlement layer underneath.

02

Rails without authorization are liability.

x402 moves money in one HTTP round trip. But if the agent goes rogue, you have no cryptographic record of what the human actually approved. You need AP2 on top.

03

Crypto rails don't reach every merchant.

Agentic Commerce Protocol supports checkout with compatible merchants. Payment credentials, merchant support and policy checks depend on the configured checkout path; it is not acceptance at every card merchant.

One wallet shipping all three is the only way an agent can transact across the full economy — protocol-agnostic, rail-agnostic, merchant-agnostic.

WHO ELSE IMPLEMENTS THESE?

What other platforms ship.

PlatformAP2x402ACP
AgentWallet✓✓✓
Coinbase Agentic Wallets—✓—
Stripe Link for agents——✓
Crossmint—partial—
Cobo Agentic Walletpartial (custody only)——
Ramp Agent Cards———

Last updated May 2026. We update this table as competitors ship. See the full breakdown on the comparison page.

THE TECHNICAL FLOW

What a single transaction looks like.

Scenario: Your procurement agent buys $4,200 of cloud compute from a vendor.

  1. Step 01
    Intent (AP2)

    An illustrative mandate can express an agent spending envelope. Verify signer identity, schema and enforcement in the implemented integration.

  2. Step 02
    Cart (AP2)

    The agent finds the offer, builds a cart, and signs a CartMandate referencing the parent IntentMandate.

  3. Step 03
    Settlement (x402 or ACP)

    If the vendor accepts USDC → x402 handshake, settlement on Base, gas sponsored. If the vendor accepts only cards → ACP SPT issued, scoped to this merchant + this cart, used once, auto-destructs.

  4. Step 04
    Receipt

    Supported mandate flows sign payment authorization and record relevant activity. On-chain anchoring and universal verifiability are not promised.

Illustrative flow, not a measured timing or approval guarantee.

FAQ

Common questions.

Is AP2 production-ready?+

Review the implemented AP2 signing and verification interfaces against your integration requirements. This page does not claim full specification conformance.

Do I have to use all three?+

No. Most agents start with one. The point is that you don't have to switch platforms when your use case grows. A procurement agent might start on AP2 + ACP and add x402 when it begins paying for APIs. Same wallet, same principal, same audit log.

What's the difference between ACP and Stripe Issuing?+

Stripe Issuing is the underlying card-issuance primitive. ACP (Agentic Commerce Protocol) is the standard for using those cards in agent-to-merchant flows — specifically, the Shared Payment Token format. AgentWallet uses Stripe as the intermediate PSP today while our direct ACP PSP registration with OpenAI is in progress.

Why USDC on Base for x402?+

USDC signing uses CDP when configured; code also includes a sealed-local-key development/test fallback. x402 network support depends on the configured route; verify Base or Base Sepolia configuration before use.

How are spending limits enforced across protocols?+

Supported spend-gated routes check per-transaction, daily and monthly caps and can require approval. Generic x402.pay_url has an optional per-call maximum, not the mandate-bound spend gate.

Get a wallet that speaks every protocol.

Create an agent and provision the resources enabled for your account through their supported flows. Provisioning time depends on the resource and provider.

Create your first agent walletRead the API docs →