ACP (Agentic Commerce Protocol) – Definition
Agentic Commerce Protocol (ACP) is an open standard that defines how a shopper, their AI agent and a merchant interact so the agent can help complete a purchase on the shopper’s behalf. It was co-developed by OpenAI and Stripe, announced on 29 September 2025, and is maintained on GitHub under Apache 2.0. The design keeps the merchant as merchant of record: the agent never holds the buyer’s card number, and the merchant charges through its own payment provider.
An open interaction model between buyer, AI agent and business – launched for in-chat checkout, and since March 2026 mainly the route by which a merchant’s catalogue reaches ChatGPT product discovery.
Current version
ACP uses date-based versioning and is still labelled beta. The latest stable snapshot is 2026-04-17, which added cart, feed, orders, authentication and MCP compatibility. Previous releases: 2025-09-29 (initial), 2025-12-12 (fulfillment), 2026-01-16 (capability negotiation), 2026-01-30 (extensions, discounts, payment handlers).
What changed in March 2026
ACP launched alongside Instant Checkout in ChatGPT, live first with US Etsy sellers and later a set of Shopify brands. On 24 March 2026 OpenAI said it was moving away from a standalone in-chat checkout and extending ACP toward product discovery instead: merchants share feeds and promotions over the protocol, and the purchase completes on the merchant’s own site or app. OpenAI’s shopper help pages still mention in-chat checkout for some eligible products, so treat it as an exception rather than the normal path.
This matters for how you read older material. Guides written before March 2026 describe in-conversation checkout as the default. The specification, the feed format and the merchant-of-record design all continued. The feed itself is described in ACP product feed.
The four actors
| Actor | Role |
|---|---|
| Shopper | Authorizes the purchase and owns the payment credentials |
| AI agent | Discovers, presents and – where supported – completes the purchase. Never the merchant of record |
| Merchant | System of record: catalogue, pricing, branding, fulfillment, disputes |
| Payment provider | Processes the charge the merchant initiates |
What ACP explicitly leaves out
The specification is deliberately narrow. Out of scope: payment-provider authorization and capture semantics, returns and exchanges, tax configuration, and fraud modelling. Merchant onboarding is also not part of the protocol – each AI platform runs its own programme.
That last point is the one merchants most often miss: implementing ACP does not by itself put products in ChatGPT. The platform’s merchant programme decides that, and OpenAI says a store can also appear through ordinary crawling if OAI-SearchBot is allowed.
Two different things are called “ACP”
The Agentic Commerce Protocol covers purchases. The Agent Client Protocol – same acronym – connects AI agents to editors and command-line tools. If a page discusses IDE integrations, it is not about commerce.
ACP and UCP compared
| ACP | UCP | |
|---|---|---|
| Maintainers | OpenAI and Stripe | Google with Shopify, Etsy, Target, Walmart, Wayfair and others |
| Licence | Apache 2.0 | Open source |
| Latest stable | 2026-04-17 | 2026-08-25 |
| Primary surface | ChatGPT product discovery | Google AI surfaces, discovery and transaction |
| Discovery artefact | Product feed pushed to the platform | Profile pulled from /.well-known/ucp |
The prerequisites overlap almost entirely – complete product data, coherent prices, real availability, accessible pages – so most of the work counts twice. Full comparison: ACP vs UCP for Magento 2.
What a Magento store implements
For most merchants the practical ACP surface is the product feed and the REST endpoints around it, not a checkout integration:
- angeo/module-openai-product-feed – an ACP-conforming feed, cron-scheduled, multi-store
- angeo/module-openai-product-feed-api – bearer-authenticated REST endpoints for feeds, paginated products with variants, and promotions
Both are MIT-licensed. Walkthrough: preparing a Magento 2 store for ChatGPT Shopping.
Questions
- Can an AI agent still complete a checkout in ChatGPT using ACP?
- Mostly not. In March 2026 OpenAI moved away from standalone Instant Checkout, and purchases now normally complete on the merchant’s own site or app. OpenAI’s help pages still mention in-chat checkout for some eligible products.
- What is the current ACP version?
- 2026-04-17 is the latest stable snapshot. It added cart, feed, orders, authentication and MCP compatibility. The specification is still labelled beta.
- Does implementing ACP put my products in ChatGPT?
- Not by itself. Merchant onboarding is run by the platform, not by the protocol. OpenAI’s merchant programme decides which feeds are used, and a store can also appear through ordinary crawling if OAI-SearchBot is allowed.
- Who stays the merchant of record under ACP?
- The merchant. The agent never holds the buyer’s primary account number, and the merchant charges through its existing payment provider while keeping catalogue, pricing, branding, fulfillment and dispute handling.
- Is ACP the same as the Agent Client Protocol?
- No, they share an acronym and nothing else. The Agentic Commerce Protocol covers purchases; the Agent Client Protocol connects AI agents to editors and command-line tools.