Agentic Commerce Protocols Explained: ACP vs UCP vs MCP for WooCommerce, Shopify and Magento

On a light warm grey ground, three app tiles on the left are labelled ChatGPT, AI Mode and Copilot. Lines run from them into a slate pipe labelled MCP. Two contract cards stand on the pipe: an orange one headed ACP and a slate one headed UCP, each with small cart, list and card icons. From the right end of the pipe a line runs to a shop front with an orange striped awning and a shopping bag in the window. Below the shop sits a dark payment card with a lock.

In short: ACP, UCP and MCP are not rivals: MCP lets AI applications call tools, while ACP (OpenAI and Stripe) and UCP (Google and Shopify) are the commerce protocols. In October 2026, Shopify runs UCP on every store, WooCommerce core supports neither and Adobe Commerce has committed to both.

Three acronyms turn up in almost every conversation about selling through AI assistants: ACP, UCP and MCP. They are usually presented as rivals, as if a store had to pick one. They are not three answers to the same question. MCP is a general way for an AI application to call tools, and it knows nothing about carts or payments. ACP and UCP are commerce protocols: they define what a checkout session is, what an agent may change in it and how payment details reach the merchant. Each of those is then implemented, in part and on its own timetable, by companies such as OpenAI, Google, Shopify and Stripe.

This guide separates those layers, sets out where each protocol stands in October 2026 according to its own specification and its vendors' documents, and then says what that means for a WooCommerce, Shopify or Magento store. How products get into ChatGPT and Google's AI features in the first place is covered in the iLogr guide "Getting a Store into ChatGPT and AI Overviews". This article is about what happens when an agent wants to act.

What is the difference between ACP, UCP and MCP?

Three words get used loosely in this area, and most of the confusion comes from mixing them up.

A transport carries messages between two pieces of software. HTTP with JSON, usually called REST, is one. MCP is another: its specification defines JSON-RPC 2.0 messages between hosts (the AI applications), the clients inside them and servers, which offer tools, resources and prompts.[1] An MCP tool does whatever its author decides: look up an order, publish a post, query a database. The MCP specification defines no cart, checkout or payment operations. The nearest it comes is a mode that sends the user to an external web page for "auth flows, payment processing, and other sensitive or secure operations", so that those never pass through the AI client.[2]

A commerce protocol is a contract about meaning. It says that a checkout session has line items, totals, fulfilment options and a status; which party may change which field; when an order must be created; and how a payment credential is handed over. ACP and UCP are both of this kind, and both can travel over more than one transport, MCP included.

An implementation is one company's working endpoints and rules: which version of a protocol it accepts, which parts it supports, who may call it and in which countries. ChatGPT, Google AI Mode, Shopify's servers and Stripe's Agentic Commerce Suite are implementations. They decide what a merchant can actually do, and each lags or extends the specification in its own way.

So "ACP vs UCP vs MCP" compares two contracts with a pipe. A more useful pair of questions is: which agents do I want to sell through, and what does each of them actually call?

Three layers, not three rivals: where ACP, UCP and MCP sit, as of October 2026. Implementations, what a merchant can actually use: ChatGPT, Google AI Mode and Gemini, Shopify, and Stripe Agentic Commerce Suite. Commerce protocols, contracts about meaning: ACP, from OpenAI and Stripe, covers checkout, carts, product feeds, orders and delegated payment; UCP, from Google and Shopify, covers checkout, cart, catalogue, order and identity linking. Payment: delegated payment tokens, such as Stripe's Shared Payment Token, and AP2 mandates, an optional UCP extension. Transports: REST and MCP carry both protocols; Agent2Agent and embedded carry UCP. MCP defines no carts, checkouts or payments. A band at the foot says an MCP server alone is not a sales channel; it needs a commerce protocol that an agent you sell through actually calls.
Where ACP, UCP and MCP sit, as of October 2026. The protocols move by dated release; the implementations move separately.

What is the Agentic Commerce Protocol (ACP)?

ACP, the Agentic Commerce Protocol, launched on 29 September 2025 together with Instant Checkout in ChatGPT. OpenAI co-developed it with Stripe, and Stripe describes it as open source under the Apache 2.0 licence.[3][4] The first release had two parts. The Agentic Checkout specification is implemented by the merchant, so that an agent can create, update, complete and cancel checkout sessions on the merchant's own systems. The Delegate Payment specification lets the buyer's payment details reach the merchant's payment provider as a token.[5] Stripe's Shared Payment Token was the first implementation of that payment side, and Stripe says each token is scoped to one merchant and one cart total.[6][7] OpenAI is not the merchant of record; the merchant is.[8]

The specification has grown since. ACP uses dated versions, and the latest stable one, 2026-04-17, added carts, a product feed API, order updates, delegated authentication and an MCP binding. The repository still describes the protocol as beta.[5][9] The MCP binding exposes the same five checkout operations as MCP tools; in the specification's own words, "MCP is a second transport binding for ACP, alongside REST."[10] The feed API runs the other way from checkout: agents host it, and merchants push their catalogue to them.[9] The same release added a discovery document at /.well-known/acp.json, for checking what a merchant supports before a session starts, although its design document is still marked as a proposal.[9][11]

OpenAI and Stripe run the protocol as founding maintainers. A technical steering committee makes decisions, its seats are appointed by the two founders, and they keep a limited veto. Meta joined the committee in April 2026. Moving to a neutral foundation is described as a long-term goal, with no date.[12][13]

The bigger change is in how OpenAI uses ACP. In March 2026 OpenAI said the first version of Instant Checkout "did not offer the level of flexibility that we aspire to provide". It let merchants use their own checkout, said it was expanding ACP to support product discovery, and added that merchants who want deeper integrations "continue to have the option to develop ChatGPT apps".[14] Its merchant page now says ACP supports product discovery through shared product data, and that purchases are completed on merchant-owned websites or apps.[15] OpenAI's developer documentation has not fully caught up. Its checkout specification still describes checkout flows inside ChatGPT, and says the specification will support MCP servers "In the future", although the protocol's repository released an MCP binding in April.[16] For most merchants in October 2026, the documented route is product discovery through ACP, followed by the merchant's own checkout. Other OpenAI pages still describe checkout inside ChatGPT. Its Help Center says Instant Checkout may be offered for some eligible products and merchants, and its plugin documentation, covered below, describes in-chat checkout with its own access conditions. None of these pages says which merchants can use which route.[17][15][18]

ACP also reaches beyond ChatGPT through Stripe. Stripe says it connects Microsoft's Copilot Checkout to sellers through ACP, and its Agentic Commerce Suite launched in December 2025 with a hosted ACP endpoint for sellers.[19][20]

What is the Universal Commerce Protocol (UCP)?

UCP, the Universal Commerce Protocol, was announced on 11 January 2026. Google says it was co-developed with Shopify, Etsy, Wayfair, Target and Walmart. Shopify describes it as co-developed by Shopify and Google, and the governance document names those two as the founding organisations.[21][22][23] It is open source under the Apache 2.0 licence.[24] Google and Shopify hold permanent seats on its governing council, Stripe joined the council in April 2026, and Google holds the proxy vote for open seats until December 2028.[23][25]

UCP is organised into capabilities, such as Checkout, Order and Identity Linking, and extensions that add features such as discounts and fulfilment to them.[26] Cart, and catalogue search and lookup, arrived in the 2026-04-08 release.[27] UCP defines four ways to carry these operations: REST, MCP, Google's Agent2Agent protocol, and an embedded mode for integrations in which the merchant's own interface is shown inside the agent's surface.[26][28]

Negotiation is built in. A business publishes a profile at /.well-known/ucp that lists its protocol version, its services and its payment handlers. An agent publishes a profile of its own and sends its address with every request, in a UCP-Agent header over HTTP or in a meta field over MCP. The business then works out which capabilities and extensions both sides support and responds with that intersection.[28] Versions are dated, and the latest release is 2026-08-25.[28][29]

Payment is a layer of its own. UCP describes itself as fully compatible with the Agent Payments Protocol (AP2), Google's protocol for signed mandates that prove what the user authorised, and treats it as an optional extension to checkout.[30] Google donated AP2 to the FIDO Alliance in April 2026.[31]

Two implementations matter to merchants. Google uses UCP for checkout in AI Mode in Google Search and the Gemini app. Merchants join a waitlist, and Google must approve an integration before it goes live. Google's guide adds that not every feature in the specification is available on its surfaces.[32] At the time of writing, its native checkout guide documents UCP versions 2026-04-08 and 2026-01-23, not 2026-08-25.[33] The other implementation is Shopify, where every store is already a UCP business, as described below.

Where does MCP fit in agentic commerce?

MCP, the Model Context Protocol, was created by Anthropic and donated to the Linux Foundation's new Agentic AI Foundation in December 2025.[34] Its current version, 2026-07-28, made the protocol stateless and removed the old initialisation handshake and session header.[35] Descriptions of MCP written before mid-2026 may describe the older design.

MCP turns up in agentic commerce in three different roles, and they are easy to confuse.

  1. As a transport for a commerce protocol. UCP defines how its operations map to MCP tools, and so, since April 2026, does ACP. A UCP checkout carried over MCP is still a UCP checkout: the tool names, fields and rules come from UCP.[26][10]
  2. As the base for apps inside an assistant. OpenAI built its Apps SDK on MCP, and its developer site now files that work under plugins, which combine skills, MCP servers and optional interfaces.[36][37] For physical goods sold through those plugins, the recommended and generally available checkout sends users to the developer's own website. The same page also describes checkout inside ChatGPT with payment methods the buyer has already saved with the merchant, and a beta of ChatGPT's own payment sheet for select marketplace partners.[18]
  3. As a store-management tool. WooCommerce's MCP integration, and most MCP modules for Magento, let an AI assistant work on the store: find products, edit them, update orders. WooCommerce says plainly that its MCP integration helps AI assistants manage a store, "not check out shoppers".[38] That is useful work, covered in the iLogr guide to WordPress MCP servers with least-privilege abilities, but it does not make a store sellable in ChatGPT or Gemini.

So "we have an MCP server" answers a different question from "can an agent buy from us?". The first is about plumbing. The second needs a commerce protocol, spoken by an agent you care about.

How do ACP and UCP compare?

The two commerce protocols cover overlapping ground with different emphases. Neither specification mentions the other, and no vendor has announced a merger. Stripe supports both for sellers, and Adobe has committed to both.[39][40]

Item ACP UCP
Announced 29 September 2025 11 January 2026
Stewards OpenAI and Stripe, with Meta on the steering committee Google and Shopify, with Stripe on the governing council
Latest version 2026-04-17, still beta 2026-08-25
Transports REST and MCP REST, MCP, Agent2Agent and embedded
Merchant discovery /.well-known/acp.json, still a proposal /.well-known/ucp
Product data Merchants push feeds to agents Agents search the merchant's catalogue
Payment Delegated payment tokens, such as Stripe's Shared Payment Token Payment handlers, with AP2 mandates as an option
Main live use Product discovery in ChatGPT Checkout in Google AI Mode and Gemini, and on Shopify stores

Treat the last row as a snapshot. Both specifications move by dated release, and the implementations move separately from them.

How does UCP work on Shopify?

Shopify is the clearest example of a platform implementing a protocol for every store at once, and it shows how the layers fit together.

Discovery. Every Shopify storefront publishes a UCP business profile at /.well-known/ucp, and since 4 September 2026 those profiles advertise version 2026-08-25.[41] The storefront's default /agents.md file gives agents the same discovery and MCP endpoints.[42]

Operations over MCP. Each store has one UCP endpoint, at /api/ucp/mcp. Catalogue search, carts, checkout and orders all sit there, as tool sets that Shopify calls Storefront Catalog MCP, Cart MCP, Checkout MCP and Order MCP. A separate global Catalog endpoint searches across Shopify merchants.[43][44] Every request must carry the address of the agent's profile in its meta field, and the tools a store returns depend on the capabilities that profile advertises.[45] This is UCP's per-request negotiation in practice: catalogue search needs no store-specific API key, because the agent identifies itself on every call.

Trust tiers. Shopify sorts agents by how they identify themselves. Anonymous agents get the lowest rate limits, agents that sign their requests get more, and agents holding a token from Shopify's Dev Dashboard get the most. A token alone is not enough to finish a sale: completing a checkout also needs permission to complete purchases, and reading orders needs the read_global_api_orders scope and covers only orders placed through that agent.[46] Shopify's pages disagree on one point: the rate-limit page lets anonymous agents build and edit checkouts, while the Cart MCP and Checkout MCP pages say checkout needs authentication or a signed request.[46][47][48] An agent builder should assume the stricter reading.

Escalation. A token does not by itself mean the checkout finishes inside the agent. For most partners referring checkout sessions from Catalog, Shopify's checkout tools return a requires_escalation status with a continue_url, and under general access the buyer completes the purchase on the merchant's own checkout through that URL.[48] The merchant always remains the merchant of record.[49]

Migration. Shopify's older Storefront MCP served catalogue and cart tools at /api/mcp. During 2026 those moved to the UCP endpoint, and only the store policy and FAQ tool remains at the old address.[50][51][52] Since 17 June 2026, developers no longer apply for access: they register an agent profile in the Dev Dashboard and call the public endpoint.[53]

The merchant's side. None of this needs code from the store owner. Shopify's agentic storefronts are active by default for eligible stores and are managed under Sales channels, then Agentic. The Help Center does not say which protocol carries which channel. It describes ChatGPT as a "discovery-focused referrer platform", with buyers completing purchases on the store's own checkout, and offers Shopify-powered direct checkout inside Google AI Mode and Gemini, Microsoft Copilot and Meta's surfaces, each with its own eligibility rules, mostly around selling to the United States.[54][55][56] Shopify said in January that UCP would power the integration with AI Mode and Gemini.[22]

What a public store actually serves. In a test, we read the /.well-known/ucp profile of three well-known public Shopify storefronts, with no key or login. Each returned JSON with version 2026-08-25 at the top, the older versions 2026-04-08 and 2026-01-23 listed as supported, and an MCP endpoint at /api/ucp/mcp. That endpoint sat on the store's own myshopify.com address, not on its custom domain. The capability lists were not identical: one store also advertised location search and lookup, and the other two did not. Each profile also listed a 2026-04-08 service with the embedded transport, and linked a separate profile for that older version. A profile shows what a store advertises, not that every call behind it works, but it is the fastest way to see which versions and capabilities a platform really claims.

One Shopify checkout over UCP, step by step, from Shopify's developer documentation. Step 1, read the store's profile at /.well-known/ucp: every Shopify store publishes one, advertising UCP 2026-08-25. Step 2, call the store's UCP endpoint at /api/ucp/mcp: each request carries the agent's profile URL in its meta field, and the tools returned depend on that profile. Step 3, search the catalogue and build a cart with Storefront Catalog MCP and Cart MCP: catalogue search needs no store-specific API key. Step 4, create the checkout with Checkout MCP: plan for authentication or a signed request, because Shopify's pages disagree on anonymous access. Step 5, hand the buyer to the store: Shopify returns requires_escalation with a continue_url, and for most partners referring sessions from Catalog the buyer completes the purchase on the merchant's own checkout. A note says that completing checkout inside the agent needs a Dev Dashboard token with permission to complete purchases. A band at the foot says the merchant always remains the merchant of record.
One Shopify checkout over UCP, from Shopify’s developer documentation as read on 6 October 2026.

Does WooCommerce support ACP or UCP?

WooCommerce core does not implement ACP or UCP, and the one experiment it shipped has now been removed.

WooCommerce 10.4, released in December 2025, added experimental Agentic Commerce checkout session routes and webhooks, off by default.[57][58] On 27 August 2026 WooCommerce merged a change that removes them, because they are "no longer being used and add extra effort to maintain".[59] The removal shipped in WooCommerce 11.2, released on 7 October 2026, with no replacement endpoint.[58][60] Anything built against those experimental routes needs to be retired.

WooCommerce now points merchants to three other routes:

  • ACP, through Stripe. WooCommerce's route to ACP is the Agentic Commerce Suite in the Stripe extension, which sends a product feed through Stripe to AI agents. The extension has carried agentic commerce code since its 10.5.0 release in March 2026. WooCommerce's own pages disagree on its status: one says it is rolling out to US businesses now, another lists it as coming soon. Stores running WooPayments cannot use it yet.[38][61][62]
  • UCP. WooCommerce lists UCP as coming soon, and describes it as "Still being built".[61][38] Its public issue tracker shows the UCP work happening in a separate plugin, woocommerce-ai, which was not publicly available when we checked and is not part of WooCommerce core.[63]
  • MCP. WooCommerce MCP, in beta since 10.3, and the canonical abilities added in 10.9 are for managing the store, as described above.[64][65] The iLogr article "WooCommerce MCP After 10.9: Moving AI Agents to the Built-in Abilities" explains how to move an agent to those abilities without widening its access.

So a WooCommerce store that wants agents to complete purchases has no core option today. It can use the Stripe route where it is available, or concentrate on discovery and keep its own checkout, which is where OpenAI's merchant page says ChatGPT purchases are completed.[15]

Do Magento and Adobe Commerce support ACP or UCP?

Adobe said in February 2026 that Adobe Commerce is "moving towards supporting UCP and ACP", by making catalogues, prices and inventory machine-readable for AI surfaces such as Gemini and ChatGPT.[40] At Adobe Summit in April 2026 it repeated that commitment and introduced a Commerce MCP server, described as covering catalogue, cart, pricing, inventory, checkout and orders.[66] On Experience League the Commerce MCP overview is still badged "Coming Soon". Separately, Adobe documents early-access support for custom product types as part of the Commerce Storefront MCP, through a module for Adobe Commerce 2.4.4 and later; that page does not show the full Storefront MCP as available.[67][68] The Adobe Commerce 2.4.9 release notes do not mention UCP, ACP or MCP.[69]

Neither Adobe announcement mentions Magento Open Source. For Open Source stores, third-party modules are filling the gap; one from the Mage-OS community, for example, publishes a UCP business profile at /.well-known/ucp.[70] Treat any such module carefully. A profile that advertises a capability is a claim. It means something only if the endpoints behind it follow the specification, and if the agents you want to sell through accept that version. For Google, that also means passing Google's own approval.[32]

Which protocol should a store support?

For most merchants, the platform makes the protocol choice. The real choice is which agents to sell through, and each answer leads to a different place.

  • ChatGPT: ACP, which OpenAI now uses mainly for product data, with checkout on the merchant's own site as the documented default. Shopify and Etsy catalogues are already integrated; other merchants apply to OpenAI and join a waitlist, or send data through providers such as Stripe and Salesforce. Shopping is live for users in the United States.[15][14]
  • Google AI Mode and Gemini: UCP. Eligible Shopify stores reach these surfaces through agentic storefronts, but direct checkout is still rolling out. Shopify requires the store to be based in the United States and to sell to US customers, and shows direct checkout only to customers in the United States. Other merchants join Google's waitlist, obtain Google's approval and build to a version Google supports. Google also documents a cart path that hands the buyer's cart back to the merchant's website.[56][32]
  • Microsoft Copilot: through Stripe, which uses ACP, or through Shopify's direct checkout.[19][54]
  • Any AI assistant using your store's own tools: an MCP server. It is useful, but it is not a sales channel on its own.

Developers building endpoints rather than using a platform have three further rules. First, build to the version the target agent accepts, not the newest one: at the time of writing, Google documents 2026-04-08, while Shopify advertises 2026-08-25.[33][41] Second, resemblance is not conformance. JSON that looks like a UCP or ACP response is not support for the protocol until negotiation, status changes and payment handling behave as the specification requires. Third, read the implementation's own rules, which add requirements of their own: Shopify, for example, requires an idempotency key on calls that complete or cancel a checkout.[48]

What should you ask a vendor who sells agentic-commerce support?

Because the protocols move by dated release and each agent accepts its own versions, a vendor's claim of "UCP support" or "ACP support" says little until it is made specific. Five questions turn it into something you can check:

  • Which protocol and which dated version do you implement? Google documents 2026-04-08 for native checkout, while Shopify advertises 2026-08-25.[33][41]
  • Which agents call it today? Google must approve a UCP integration before it goes live, and OpenAI describes ChatGPT shopping as live for users in the United States.[32][15]
  • Can you show a completed test order, not only a profile? A profile at /.well-known/ucp is a claim, as noted above. An order that passes through negotiation, status changes and payment is evidence.
  • Where does the buyer pay, and who is the merchant of record? On Shopify the merchant stays the merchant of record, and general-access checkouts hand the buyer to the merchant's own checkout.[48][49]
  • What happens when the protocol version changes? Ask who maintains the integration, what it costs and how long an older version keeps working. The three profiles described above also listed two older versions as supported.

A vendor who answers these plainly is worth a conversation. One who only repeats the acronyms is describing a roadmap, not a service.

The short version

  • MCP is a transport for AI tools. It defines no carts, checkouts or payments, and an MCP server for store management does not make a store sellable through AI agents.
  • ACP, from OpenAI and Stripe, is a commerce protocol over REST or MCP. In ChatGPT, OpenAI now prioritises product discovery and the merchant's own checkout; the in-chat checkout routes it still documents have their own access conditions.
  • UCP, from Google and Shopify, is a commerce protocol over REST, MCP, Agent2Agent or an embedded mode, with per-request agent profiles. It powers checkout in Google AI Mode and Gemini, by approval.
  • Shopify already runs UCP on every store at /api/ucp/mcp, and manages the AI channels for merchants by default.
  • WooCommerce has no core support: ACP comes through the Stripe extension where available, UCP is still being built, and the experimental core checkout routes were removed in 11.2.
  • Adobe Commerce has committed to both protocols, with its Commerce MCP still coming soon. Magento Open Source depends on third-party modules.
  • For every store, accurate product data and a working checkout of your own remain essential. OpenAI's merchant page prioritises merchant-owned checkout, and Shopify's general-access Checkout MCP flow directs buyers to the merchant's checkout through a continue_url.[15][48]

References

Numbers in square brackets in the text link to these sources.

  1. Model Context Protocol specification, version 2026-07-28: overview (opens in a new tab)Used for: what MCP is, its JSON-RPC messages, and that it defines no carts or payments.
  2. Model Context Protocol specification, version 2026-07-28: elicitation (opens in a new tab)Used for: MCP's external-page mode for payment processing and other sensitive operations.
  3. OpenAI: Buy it in ChatGPT, Instant Checkout and the Agentic Commerce Protocol (29 September 2025) (opens in a new tab)Used for: ACP's launch date and OpenAI's co-development with Stripe.
  4. Stripe: Developing an open standard for agentic commerce (29 September 2025) (opens in a new tab)Used for: Stripe's description of ACP as open source under the Apache 2.0 licence.
  5. Agentic Commerce Protocol repository: README and released versions (opens in a new tab)Used for: ACP's two original parts, Agentic Checkout and Delegate Payment, and its released versions.
  6. Stripe: Stripe powers Instant Checkout in ChatGPT and releases Agentic Commerce Protocol codeveloped with OpenAI (29 September 2025) (opens in a new tab)Used for: Shared Payment Tokens scoped to one merchant and cart total.
  7. OpenAI developer documentation: Delegated Payment Spec (opens in a new tab)Used for: delegated payment flows, and Shared Payment Token as the first compatible implementation.
  8. OpenAI developer documentation: Agentic commerce key concepts (opens in a new tab)Used for: that the merchant, not OpenAI, is the merchant of record.
  9. Agentic Commerce Protocol changelog: version 2026-04-17 (opens in a new tab)Used for: what ACP version 2026-04-17 added, and the feed API direction.
  10. Agentic Commerce Protocol: MCP transport binding (opens in a new tab)Used for: the MCP binding as a second ACP transport next to REST.
  11. Agentic Commerce Protocol RFC: discovery (opens in a new tab)Used for: the proposed /.well-known/acp.json discovery document and its proposal status.
  12. Agentic Commerce Protocol: governance (opens in a new tab)Used for: ACP's steering committee, founder appointments and the limited veto.
  13. Agentic Commerce Protocol: maintainers (opens in a new tab)Used for: Meta's seat on the steering committee.
  14. OpenAI: Powering product discovery in ChatGPT (24 March 2026) (opens in a new tab)Used for: OpenAI's March 2026 shift to product discovery and the merchant's own checkout.
  15. OpenAI: Power product discovery in ChatGPT (merchant page) (opens in a new tab)Used for: OpenAI's merchant page on discovery, merchant-owned checkout, waitlist and US availability.
  16. OpenAI developer documentation: Agentic Checkout Spec (opens in a new tab)Used for: OpenAI's checkout specification and its note that MCP support comes "In the future".
  17. OpenAI Help Center: Shopping with ChatGPT search (opens in a new tab)Used for: the Help Center wording on Instant Checkout for some eligible products and merchants.
  18. OpenAI developer documentation: Checkout API reference (plugins) (opens in a new tab)Used for: checkout routes for plugins, including the developer's own site and the beta payment sheet.
  19. Stripe: Microsoft Copilot and Stripe (8 January 2026) (opens in a new tab)Used for: Stripe's link between Microsoft Copilot Checkout and ACP.
  20. Stripe: Introducing the Agentic Commerce Suite (11 December 2025) (opens in a new tab)Used for: Stripe's Agentic Commerce Suite and its hosted ACP endpoint for sellers.
  21. Google: New tech and tools for retailers to succeed in an agentic shopping era (11 January 2026) (opens in a new tab)Used for: Google's announcement of UCP and its co-developers.
  22. Shopify: AI commerce at scale (11 January 2026) (opens in a new tab)Used for: Shopify's account of co-developing UCP and powering AI Mode and Gemini.
  23. Universal Commerce Protocol: governance (opens in a new tab)Used for: UCP governance: founding organisations, council seats and Google's proxy vote.
  24. Universal Commerce Protocol repository: README (opens in a new tab)Used for: UCP's open-source status and Apache 2.0 licence.
  25. Universal Commerce Protocol: announcements (opens in a new tab)Used for: Stripe joining the UCP governing council in April 2026.
  26. Universal Commerce Protocol: core concepts (opens in a new tab)Used for: UCP capabilities, extensions and the four transports.
  27. Universal Commerce Protocol release v2026-04-08 (opens in a new tab)Used for: cart and catalogue search arriving in UCP release 2026-04-08.
  28. Universal Commerce Protocol specification: overview (opens in a new tab)Used for: UCP profiles, negotiation, the UCP-Agent header and dated versions.
  29. Universal Commerce Protocol releases (opens in a new tab)Used for: the latest UCP release, 2026-08-25.
  30. Universal Commerce Protocol: UCP and AP2 (opens in a new tab)Used for: how UCP relates to AP2 mandates as an optional extension.
  31. Google: Google donates Agent Payments Protocol to FIDO Alliance (28 April 2026) (opens in a new tab)Used for: Google's donation of AP2 to the FIDO Alliance.
  32. Google for Developers: UCP integration guide overview (opens in a new tab)Used for: Google's approval, waitlist and feature limits for UCP checkout in AI Mode and Gemini.
  33. Google for Developers: UCP native checkout (opens in a new tab)Used for: the UCP versions Google documents for native checkout.
  34. Linux Foundation: Linux Foundation announces the formation of the Agentic AI Foundation (9 December 2025) (opens in a new tab)Used for: MCP's donation to the Agentic AI Foundation.
  35. Model Context Protocol specification, version 2026-07-28: key changes (opens in a new tab)Used for: MCP version 2026-07-28 becoming stateless and dropping the handshake and session header.
  36. OpenAI: Introducing apps in ChatGPT and the new Apps SDK (opens in a new tab)Used for: OpenAI's Apps SDK built on MCP.
  37. OpenAI developer documentation: Plugins (opens in a new tab)Used for: OpenAI's plugins, combining skills, MCP servers and optional interfaces.
  38. WooCommerce: From found to bought, getting your store ready to sell through AI (1 August 2026) (opens in a new tab)Used for: WooCommerce's guidance on selling through AI, and MCP as store management, not checkout.
  39. Stripe documentation: Agentic commerce (opens in a new tab)Used for: Stripe's support for agentic commerce on the seller side.
  40. Adobe: Adobe Commerce commits to agentic commerce standards (18 February 2026) (opens in a new tab)Used for: Adobe's commitment to support UCP and ACP in Adobe Commerce.
  41. Shopify developer changelog: Shopify storefronts now support UCP 2026-08-25 (4 September 2026) (opens in a new tab)Used for: Shopify storefronts advertising UCP 2026-08-25 from 4 September 2026.
  42. Shopify developer documentation: agents.md.liquid (opens in a new tab)Used for: the agents.md file that points agents to discovery and MCP endpoints.
  43. Shopify developer documentation: Build commerce agents with UCP (opens in a new tab)Used for: Shopify's UCP endpoint, its tool sets and the global Catalog endpoint.
  44. Shopify developer documentation: Order MCP server (opens in a new tab)Used for: the Order MCP tool set and its place in the UCP endpoint.
  45. Shopify developer documentation: Storefront Catalog MCP (opens in a new tab)Used for: catalogue search, the profile in each request and capability-based tools.
  46. Shopify developer documentation: Authentication and rate limiting for agents (opens in a new tab)Used for: Shopify's trust tiers, rate limits, token scopes and the anonymous-checkout conflict.
  47. Shopify developer documentation: Cart MCP server (opens in a new tab)Used for: the Cart MCP page and its authentication wording.
  48. Shopify developer documentation: Checkout MCP server (opens in a new tab)Used for: requires_escalation, continue_url, idempotency keys and the Checkout MCP authentication wording.
  49. Shopify developer documentation: Carts and checkout (opens in a new tab)Used for: that the merchant stays the merchant of record in Shopify checkout.
  50. Shopify developer changelog: Storefront Catalog MCP now implements UCP (22 April 2026) (opens in a new tab)Used for: Storefront Catalog MCP moving to UCP in April 2026.
  51. Shopify developer changelog: Storefront MCP cart tools are being deprecated in favour of UCP Cart MCP (24 June 2026) (opens in a new tab)Used for: the deprecation of Storefront MCP cart tools in favour of UCP Cart MCP.
  52. Shopify developer documentation: Migrate from Storefront MCP (opens in a new tab)Used for: which Storefront MCP tools remain at the old address.
  53. Shopify: Agentic commerce for every developer, the Spring '26 Edition (17 June 2026) (opens in a new tab)Used for: developers registering agent profiles in the Dev Dashboard from 17 June 2026.
  54. Shopify Help Center: Shopify's agentic storefronts (opens in a new tab)Used for: Shopify's agentic storefronts, default activation and direct checkout channels.
  55. Shopify Help Center: Selling on ChatGPT (opens in a new tab)Used for: ChatGPT as a discovery-focused referrer, with checkout on the merchant's own site.
  56. Shopify Help Center: Google AI Mode and Gemini in agentic storefronts (opens in a new tab)Used for: Google AI Mode and Gemini eligibility, US limits and the cart hand-back path.
  57. WooCommerce developer blog: WooCommerce 10.4 release post (10 December 2025) (opens in a new tab)Used for: WooCommerce 10.4 adding experimental agentic checkout routes, off by default.
  58. WooCommerce developer blog: WooCommerce 11.2.0 pre-release notes (21 September 2026) (opens in a new tab)Used for: which WooCommerce release contained and then removed the experimental routes.
  59. WooCommerce pull request 67914: Remove the experimental Agentic Checkout API (merged 27 August 2026) (opens in a new tab)Used for: why WooCommerce removed the experimental Agentic Checkout API.
  60. WooCommerce developer blog: WooCommerce 11.2.0 release notes (7 October 2026) (opens in a new tab)Used for: the WooCommerce 11.2.0 release date.
  61. WooCommerce: Agentic commerce (opens in a new tab)Used for: WooCommerce's agentic commerce page, the Stripe route and UCP listed as coming soon.
  62. WooCommerce Stripe Payment Gateway changelog, version 11.0.1 (opens in a new tab)Used for: the Stripe extension carrying agentic commerce code since 10.5.0.
  63. WooCommerce issue 65389: Unify product-export abstractions across ACP, POS Catalog, UCP, and Google Merchant Center (opens in a new tab)Used for: UCP catalogue code identified in woocommerce-ai, separate from WooCommerce core.
  64. WooCommerce developer blog: WooCommerce 10.3, COGS comes to core and MCP beta (22 October 2025) (opens in a new tab)Used for: WooCommerce MCP entering beta in version 10.3.
  65. WooCommerce developer blog: Introducing canonical WooCommerce abilities for products and orders (12 May 2026) (opens in a new tab)Used for: the canonical WooCommerce abilities added in version 10.9.
  66. Adobe: Reduce time-to-value with agentic upgrades in Adobe Commerce (20 April 2026) (opens in a new tab)Used for: Adobe Summit announcements and the Commerce MCP server description.
  67. Adobe Experience League: Commerce MCP overview (opens in a new tab)Used for: the Commerce MCP overview still badged Coming Soon.
  68. Adobe Commerce documentation source: custom product types (Commerce Storefront MCP early access) (opens in a new tab)Used for: early-access support for custom product types in Commerce Storefront MCP.
  69. Adobe Experience League: Adobe Commerce 2.4.9 release notes (opens in a new tab)Used for: that the Adobe Commerce 2.4.9 release notes do not mention UCP, ACP or MCP.
  70. Packagist: mage-os/module-agentic (opens in a new tab)Used for: a Mage-OS community module publishing a UCP business profile.

Leave a Reply

Your email address will not be published. Required fields are marked * See the privacy policy for how comments are handled.