Protocols & news

ACP in 2026: what the Agentic Commerce Protocol does now

Listen · 8 min

Narrated by an AI voice. Code examples are on the page.

Short answer

ACP, the Agentic Commerce Protocol, is an open standard for AI agents to buy from businesses. In 2026 it grew from a checkout spec into a set of building blocks: carts, product feeds, orders, payment and 3DS authentication, a discovery file and an MCP binding. It is still in beta, governed by OpenAI and Stripe with Meta on its steering committee, and most merchants will meet it through a platform such as Stripe rather than by building it.

Key takeaways

  • The latest dated ACP release is 2026-04-17, still in beta.
  • It now covers carts, feeds, orders, discovery and MCP.
  • Meta joined OpenAI and Stripe on ACP's steering committee.

What is ACP in 2026?

ACP, the Agentic Commerce Protocol, is an open standard that lets an AI agent buy from a business on a shopper's behalf. Its GitHub repository describes it as "an interaction model and open standard for connecting buyers, their AI agents, and businesses to complete purchases seamlessly."

It launched in September 2025 alongside ChatGPT's Instant Checkout. In March 2026 OpenAI said that feature is moving to apps, but the protocol kept growing. The repository says the specification "is currently in beta." It is open source under the Apache 2.0 license.

For the history of the launch and the March 2026 change, see what happened to ChatGPT Instant Checkout. This article covers what the Agentic Commerce Protocol does today.

What can ACP do now?

ACP now covers most of a shopping journey, not just the final payment. Stripe's documentation lists its building blocks as agentic checkout, cart and feed, delegate payment, delegate authentication, and orders and webhooks.

In plain terms, as described in the specification and its changelog:

  • Checkout. The agent creates, updates and completes a checkout session with your system. Your system returns the items, totals and messages.
  • Carts. The agent can build a basket before checkout. The changelog notes that "Carts are scoped to a single seller" and that cart totals "are estimates".
  • Product feeds. Merchants push catalog data to the agent's platform. The changelog calls this "a push model: merchants push product catalog metadata and product records to Agents."
  • Delegated payment. The agent passes a payment token, not a card number. The payment spec says the token "MUST ONLY be usable within the provided Allowance (reason, max_amount, currency, expiry)."
  • Delegated authentication. A 3DS2 card check that the agent can run with the authentication provider the merchant names.
  • Orders. After purchase, the agent can track fulfilment, shipping events, refunds and other adjustments. The changelog's examples include "Where's my order?" and "Did I get a refund?"
  • Discovery. A public file at /.well-known/acp.json that tells agents a site supports ACP and what it can do.
  • MCP. An optional way to run ACP checkout as MCP tools, as well as a regular web API.

A store that implements all of this lets an agent find a product, buy it and answer follow-up questions without opening a browser.

What changed in the April 2026 version?

The 2026-04-17 release added several new parts of the protocol at once. The repository marks it as the latest stable version and says the previous version, 2026-01-30, is deprecated.

It added carts, the feed API, native orders, delegated 3DS authentication, the discovery file and the MCP binding. It also changed item quantities from whole numbers to decimals "to support B2B commerce (e.g. items sold by weight or other fractional units)", which the changelog marks as a breaking change.

Earlier 2026 versions laid the groundwork. They added capability negotiation, extensions, discounts and payment handlers, and an open authentication provider model with Adyen listed as a provider.

At the time of writing, 2026-04-17 is still the newest dated release. Work since then sits in the repository's unreleased folder, so check the changelog before you build.

Who runs ACP now?

OpenAI and Stripe still lead ACP, and Meta has joined them. The README says "ACP is jointly governed by OpenAI and Stripe as Founding Maintainers, with a clear path toward broader community governance."

Decisions go through a Technical Steering Committee. The governance document says it "has up to 7 seats," and that seats are appointed by the Founding Maintainers. Its current members table lists three: OpenAI, Stripe and Meta. A commit dated April 24, 2026 added Meta to the committee and to the maintainers list.

Stripe's own documentation now describes ACP as "an open standard created by Stripe, OpenAI, and Meta." The README lists "Neutral foundation stewardship as ecosystem matures" as a future step. No foundation has been named.

Does ChatGPT still use ACP?

Not in a way merchants see. In March 2026 an OpenAI spokesperson told Digital Commerce 360 that "Instant Checkout is moving to Apps," and that OpenAI was "prioritizing making ChatGPT search and product discovery great, with ACP serving as the infrastructure."

OpenAI's commerce documentation for merchants does not mention ACP at the time of writing. It covers product feeds, browser access, ChatGPT Wallet payments, Sign in with ChatGPT and plugins. For plugins, OpenAI says "Your MCP server owns availability, pricing, transaction state, and confirmation." Its example tools for carts and checkout come with a note that they "are not mandatory tool names or a universal schema."

The ACP README still points developers to OpenAI's implementation "to integrate with ChatGPT and other AI agent surfaces." If ChatGPT is your goal, follow OpenAI's current guides, which we cover in how to get your products into ChatGPT shopping.

Should your store implement ACP?

Probably not by hand. For most merchants, ACP arrives through a payment provider or commerce platform.

Stripe is the clearest example. When it launched its Agentic Commerce Suite in December 2025, Stripe said that while ACP creates industry standards, "your business still faces a heavy integration lift." With the suite, you share a catalog with Stripe, and Stripe "manages checkout and payments when an agent sells your products." It receives the agent's shared payment token and processes the payment. Stripe's guide to running your own checkout instead points to the Universal Commerce Protocol (UCP). For how the two compare, see UCP vs ACP.

Build ACP yourself only if you have a specific agent platform asking for it, and a team to keep up with a beta spec. If you do:

  1. Start from the latest dated version, not unreleased.
  2. Publish a /.well-known/acp.json file so agents can find you.
  3. Decide your own order rules before the first agent order arrives. Our guide to rules for AI agent orders covers spending limits and human review.

How Sill helps

Sill shows you which AI agents and bots visit your site and what they ask for and buy. It publishes the files agents read, such as llms.txt, an agent card and an MCP server, and keeps them current. When an agent places an order, your rules approve it, decline it, or hold it for review, and every decision is signed and recorded. ACP is built in Sill but not enabled. You can check how your site looks to agents with a free readiness scan.

Questions people ask

Is ACP the same as Instant Checkout?

No. Instant Checkout was ChatGPT's in-chat buying feature, launched on ACP in September 2025. In March 2026 OpenAI said Instant Checkout was moving to apps. ACP is the protocol, and it is still maintained.

Is ACP free to use?

The specification is open source under the Apache 2.0 license. Contributors must sign a contributor license agreement before their changes are accepted.

What is /.well-known/acp.json?

It is ACP's discovery file. The 2026-04-17 changelog says it lets agents determine ACP support, find the API address, check version compatibility and learn a seller's capabilities before starting a checkout. It needs no authentication.

Does ACP work with payment providers other than Stripe?

The ACP website says businesses that implement it can work with any AI agent or payment processor. Stripe's Shared Payment Token was the first compatible option, and later versions added a payment handler framework and Adyen as a listed provider.

Sources

  1. Agentic Commerce Protocol on GitHub · checked 17 Nov 2026
  2. ACP changelog: version 2026-04-17 · checked 17 Nov 2026
  3. ACP changelog: version 2026-01-16 · checked 17 Nov 2026
  4. ACP changelog: version 2026-01-30 · checked 17 Nov 2026
  5. Stripe: Stripe powers Instant Checkout in ChatGPT and releases Agentic Commerce Protocol · checked 17 Nov 2026
  6. ACP governance · checked 17 Nov 2026
  7. ACP commit: Add Meta as TSC member · checked 17 Nov 2026
  8. ACP: Delegate payment RFC · checked 17 Nov 2026
  9. Agentic Commerce Protocol (ACP) · checked 17 Nov 2026
  10. Stripe Docs: Agentic Commerce Protocol · checked 17 Nov 2026
  11. Stripe: Introducing the Agentic Commerce Suite · checked 17 Nov 2026
  12. Stripe Docs: How Agentic Commerce Suite works · checked 17 Nov 2026
  13. Stripe Docs: Sell products through agents · checked 17 Nov 2026
  14. OpenAI for Developers: Commerce docs · checked 17 Nov 2026
  15. OpenAI for Developers: Build a plugin · checked 17 Nov 2026
  16. Digital Commerce 360: OpenAI shifts checkout plans in its agentic commerce strategy · checked 17 Nov 2026

Written by The Sill Signals Team. Last reviewed 17 Nov 2026.

Share this articleLinkedInXBlueskyEmail

Keep reading

See which AI agents visit your site, and decide what they may do.

Scan your site free