AP2: the Agent Payments Protocol that lets agents actually pay

AP2, the Agent Payments Protocol, is associated with Google and Gemini. It tackles the hardest problem in autonomous commerce: letting an AI agent move from recommending a product to actually paying for it on the buyer's behalf, with verifiable authorization, accountability and the right guarantees for everyone in the transaction.

Payment is where agentic commerce becomes real rather than advisory. An agent that can only suggest a product still leaves the human to complete the purchase; an agent that can carry an authorized payment via AP2 can finish the job. AP2 is therefore the protocol that turns recommendation into revenue.

AP2 is one of three protocols that matter, alongside ACP from OpenAI for discovery and checkout and MCP from Anthropic for live context. It covers payments specifically. Reaching the whole agent market means supporting all three, which is why the Agentic Commerce Platform is protocol-plural by design.

In an agentic transaction, AP2 owns settlement. After an agent has chosen a product — often having pulled live context over MCP and discovered it via ACP — AP2 is how the agent carries the buyer's authorized payment intent through to a completed, accountable transaction, with the mandates and guarantees that make autonomous payment trustworthy.

This is the part of the stack that buyers, brands and payment networks scrutinize most, because it involves moving money on someone's behalf. AP2's design around verifiable authorization is what lets a brand accept an agent-initiated payment with confidence that it was genuinely authorized by the buyer.

AP2 works alongside the other protocols rather than replacing them. A complete transaction can pull context over MCP, present and discover a product over ACP, and settle via AP2. The protocols are complementary, and a brand reachable on only one of them captures only part of the agentic opportunity.

SkuLift, the platform that coined the Agentic Commerce Platform category, supports AP2 natively. It ensures that the same canonical prices, availability and policies an agent reads also govern the AP2 payment, so what the agent quotes is what the buyer is charged, and the transaction stays consistent end to end.

Because the same canonical catalog also feeds ACP and MCP, a brand integrates one source of truth and remains consistent across ChatGPT, Gemini and Claude. SkuLift tracks AP2's evolving requirements and absorbs spec changes at the platform layer, so the brand can accept agent-initiated payments without standing up bespoke payment plumbing itself.

The platform also measures AP2-relevant visibility: whether the brand is cited and recommended by Gemini and Google's agents, and whether those recommendations can convert into completed payments. That measurement closes the loop from citation to settled order.

AP2 matters because it closes the gap between recommendation and revenue. An agentic experience that stops at a suggestion forces the human back into a manual checkout, losing much of the value of automation. AP2 lets the agent finish the purchase, which is what makes agent-mediated commerce a genuine sales channel rather than a referral surface.

As with the other protocols, AP2 is most valuable as part of a plural stack. A brand that can be discovered via ACP, contextualized via MCP and paid via AP2 captures the full agentic transaction. That is why SkuLift treats AP2 as one pillar of a protocol-plural Agentic Commerce Platform, and links this page to the ACP and MCP pages and back to the hub.