The Agentic Commerce Protocol, Explained

Most AI protocols so far have been about information. An agent reads your docs, queries your data, answers a question. The Agentic Commerce Protocol is about something the others deliberately avoided: money changing hands. It defines how an AI agent can actually complete a purchase on a person’s behalf, not just find the product and hand back a link.

As of August 2026, ACP is an open standard co-developed by OpenAI and Stripe, released under the Apache 2.0 license, with an initial release in September 2025 and a later stable spec revision dated 2026-04-17. The primary sources are the ACP specification repository and Stripe’s writeup, developing an open standard for agentic commerce. Here is what it is trying to standardize and why that is harder than it sounds.

Buying Is The Hard Verb

Finding a product is a read. Buying it is a write, and an irreversible one that moves money, so the bar is different. An agent that summarizes a page wrong wastes a minute. An agent that checks out wrong spends real money on the wrong thing. That gap is why commerce needed its own protocol rather than borrowing a data one.

The useful way to see it: search makes a product findable, an answer engine makes its details extractable, but only a commerce protocol lets an agent complete the transaction. ACP is aimed squarely at that last verb, complete, and it treats trust, authorization, and payment as first-class problems rather than afterthoughts.

The Building Blocks It Defines

ACP is not one monolithic thing. As of August 2026 it defines a set of building blocks that fit together, and it is worth knowing them by name because vendors will start using the terms.

Agentic checkout is the flow itself: the defined steps by which an agent moves from a chosen item to a completed order.

Cart is the shared representation of what is being bought, so the agent, the merchant, and the payment side all agree on the contents and totals.

Product feed is how a merchant exposes what it sells in a form an agent can read reliably, rather than the agent scraping a page and guessing.

Payment delegation is the mechanism that lets a payment proceed on the buyer’s behalf without the agent holding raw card details, keeping sensitive credentials out of the agent’s hands.

Delegated authentication is how the buyer’s authority to act is passed through in a controlled way, so the purchase is provably authorized rather than assumed.

Read together, those pieces are an attempt to make “an agent bought this for me” auditable: who authorized it, what was in the cart, and how the payment was allowed to go through.

It Is Built To Interoperate, Not To Replace

ACP is designed to interoperate with the Model Context Protocol rather than compete with it. That distinction matters. MCP connects a model to tools and data; ACP handles the transaction. An agent can use MCP to gather what it needs and ACP to close the purchase, and because both are open, neither locks you to a single vendor’s stack.

The Apache 2.0 license is part of the point. It is a permissive open-source license, so merchants and platforms can adopt and extend the spec without a proprietary gatekeeper deciding who gets to build. We put ACP next to the other agent protocols, including MCP and A2A, in the agent protocol landscape, which is the map to read if you are trying to see how these fit together.

What It Means If You Sell Something

If agents start buying on behalf of customers, your product information stops being read only by humans skimming a page. It gets consumed by software that will not forgive ambiguity. A price that is clear to a person but buried in a graphic, a stock status that lives only in JavaScript, a variant that is obvious visually but unlabeled in the markup: each becomes a reason an agent picks a competitor whose feed is clean.

Before:

Our new Pro plan is now available at a great price with tons of flexible options, and shipping is usually pretty quick for most orders depending on where you are.

After:

The Pro plan costs 7 euros per month or 60 euros per year. It includes every feature in Free plus priority support. Orders to EU addresses ship within two business days; other regions vary.

The second version is one an agent can parse into a cart line without guessing, and a human can act on without emailing to ask.

A Wrivio Context for product and pricing copy an agent will read could say:

Rewrite this product description so price, plan name, what is included, and any conditions are each stated in plain, unambiguous sentences. Keep every name, price, date, figure, and commitment exactly as written. Do not add prices, features, discounts, or shipping claims that are not in the original.

Press Ctrl+Shift+Space, paste the description, and check the diff. Watch for the model rounding a price or inventing a shipping promise, because a made-up commitment on a page an agent transacts against is a promise you did not make. For the wider preparation checklist, see preparing your content for AI agents that buy.

Where It Actually Stands

Be honest about maturity. As of August 2026 ACP is an open specification with a stable revision dated 2026-04-17, backed by two serious names, but agent-driven checkout is early, and how widely buyers and merchants adopt it is still unfolding. Treat it as a standard worth understanding and preparing for, not as a settled part of how everyone shops. The safe move is to make your product and pricing pages unambiguous now, because clean, machine-readable product information helps human buyers too, whatever the adoption curve does.

Common Questions

What is the Agentic Commerce Protocol?

ACP is an open standard for agent-initiated checkout, co-developed by OpenAI and Stripe and released under the Apache 2.0 license, that defines how an AI agent can complete a purchase on a buyer’s behalf.

Who created ACP and under what license?

It was co-developed by OpenAI and Stripe and released under Apache 2.0, with an initial release in September 2025 and a later stable spec revision dated 2026-04-17.

What are the main building blocks of ACP?

As of August 2026 the spec defines agentic checkout, a cart, a product feed, payment delegation, and delegated authentication, which together let an authorized purchase proceed without the agent holding raw card details.

Does ACP replace MCP?

No. ACP is designed to interoperate with the Model Context Protocol: MCP connects a model to tools and data, while ACP handles the transaction, so an agent can use both.

Download Wrivio for Windows to rewrite your product and pricing pages into unambiguous lines an agent can parse and a customer can trust.