Cowrie Research

agent-payments-protocol

3 min read

Agent Payments Protocol (AP2)

  • Name: Agent Payments Protocol (AP2)
  • URL: https://agentpaymentsprotocol.info/
  • Category: agentic commerce authorization protocol / multi-rail settlement orchestration standard
  • Tags: ethereum-ecosystem
  • Summary: AP2 standardizes mandates, approvals, and settlement proof for agent-led purchases. The point is the permission trail above payment rails, not the rail itself.
  • What it does:
    • Defines a mandate chain for agent-led purchases, including Intent Mandate, Cart Mandate, and Payment Mandate objects that create an auditable record of what the user authorized, what was actually offered, and how payment should occur
    • Specifies core payment objects such as Agent Identity, Payment Intent, and Settlement Proof, plus REST endpoints and event streams for creating intents, confirming them, releasing escrow, issuing refunds, and retrieving notarized settlement records
    • Reuses A2A for discovery, negotiation, and status updates, while treating MCP tools and agent services as billable surfaces that can be priced, purchased, and metered through AP2 flows
    • Ships with a production-oriented default integration to Coinbase’s x402 rail, including immediate capture, escrow release, milestone payments, and usage-metered flows, while explicitly presenting itself as rail-agnostic for cards, bank transfers, stablecoins, and other providers
    • Publishes an open GitHub implementation surface with SDK code, JSON schemas, sample agents, and runnable scenarios across Python, Go, Android, and a demo web client
  • Key claims:
    • The official introduction page says AP2 was announced with Google Cloud and Coinbase as the commerce layer for the agent economy, giving autonomous agents wallets, programmable settlement, and auditable proofs without requiring a human at every payment step
    • Google’s launch post frames AP2 as an open, payment-agnostic protocol that can support cards, bank transfers, stablecoins, and other methods while solving authorization, authenticity, and accountability for agent-led transactions
    • The core spec says AP2 formalizes Agent Identity, Payment Intent, Settlement Proof, and mandate schemas, with signed policy traces, compliance metadata, and event-stream delivery for downstream systems
    • The payments-rail guide says the default x402 integration is production-ready, supports immediate capture, escrow, milestone, and metered usage flows, and keeps raw private keys away from agents by putting policy evaluation and signing in the control plane
    • The quickstart and repo show AP2 is more than a position paper: the public implementation includes runnable shopping-agent, merchant-agent, credential-provider, and payment-processor demos along with SDK and schema code
    • The separate A2A x402 extension repo reinforces that AP2 is trying to be the higher-level commerce and authorization framework, while x402 remains a lower-level crypto payment rail and settlement mechanism
  • Whitepaper: No canonical standalone AP2 whitepaper or litepaper PDF surfaced in this pass. The clearest current source of truth is the official docs/spec corpus, the public GitHub repo, the Google Cloud launch post, and the companion A2A x402 extension repo; see ../../whitepapers/agent-payments-protocol-primary-sources-2026-04-29.md.
  • Sources:

Internal linkages

Graph View

Backlinks