Deutsch
Agentic commerce

Agentic commerce

Also known as: agentic shopping

Agentic commerce describes purchases in which an AI agent acts on a person’s behalf to find, compare, and buy products, up to and including payment. The person sets the goal and limits, such as budget, brand, or delivery date, and approves the purchase. The agent handles the steps in between through interfaces to merchants and payment providers.

At a glance

Type
purchase handled by an AI agent on a person's behalf
Open protocols
ACP (OpenAI, Stripe), AP2 (Google), UCP (Google with retailers)
Since
2025 (AP2 on Sep 16, 2025, ACP on Sep 29, 2025)
Used in
AI Mode in Google Search and the Gemini app (checkout via UCP)

Last checked:

How does agentic commerce work?

An agent has to do three things a shopper normally does on a website. It needs machine-readable product data with price and availability, it has to build a cart with the merchant, and it must trigger a payment that the merchant can trust as the customer’s real intent. Since 2025, several open protocols have appeared for these steps:

  • Agentic Commerce Protocol (ACP): released by Stripe and OpenAI on September 29, 2025, open source under Apache 2.0. Merchants keep control of the customer relationship and the transaction, and payment credentials are passed as a token. At launch it powered Instant Checkout in ChatGPT, starting with US Etsy sellers. According to reports, OpenAI scaled Instant Checkout back in March 2026 and now routes shoppers to merchants’ own checkout (TechCrunch, March 24, 2026).
  • Agent Payments Protocol (AP2): announced by Google on September 16, 2025, together with more than 60 payment and technology companies. It uses cryptographically signed “mandates” to prove what the user authorized, and it extends the Agent2Agent (A2A) protocol.
  • Universal Commerce Protocol (UCP): introduced by Google in January 2026, developed with Shopify, Etsy, Wayfair, Target, and Walmart. It covers the journey from discovery to checkout and order management, is compatible with AP2, and can be integrated through APIs, A2A, or MCP.
AI agent protocols compared
ProtocolPublisherConnectsStatus and version
MCP (Model Context Protocol)by Anthropic, since 2025-12-09 at the Agentic AI Foundation (Linux Foundation)AI applications with servers that provide data, tools and promptscurrent version 2026-07-28
A2A (Agent2Agent)by Google, donated to the Linux Foundation; joining the Agentic AI Foundation announced on 2026-08-27AI agents from different vendors with each otherspecification 1.0 (release v1.0.1 of 2026-05-28)
ACP (Agentic Commerce Protocol)OpenAI and Stripebuyers and their AI agents with businesses and payment providersbeta, current version 2026-04-17
AP2 (Agent Payments Protocol)Google; standardisation continues in FIDO Alliance working groupsAI agents, merchants and payment providers for payments on behalf of usersv0.2 (release of 2026-04-28)
UCP (Universal Commerce Protocol)Google with commerce partners (incl. Shopify, Etsy, Wayfair, Target, Walmart)platforms and AI agents with businesses (profile at /.well-known/ucp)stable, version 2026-08-25
WebMCPW3C Web Machine Learning Community Group (editors from Microsoft and Google)websites with AI agents in the browserdraft (Draft Community Group Report of 2026-10-02), not a W3C standard; origin trial in Chrome from version 149
NLWebMicrosoft (announced 2025-05-19), open source under the MIT licencewebsites (Schema.org and RSS content) with users and AI agents; every instance is an MCP serveropen-source project without a published version number

Versions and status as stated in each specification or on the publisher's site, checked on 8 October 2026. These protocols change quickly. MCP, ACP and UCP use date-based versions (YYYY-MM-DD), A2A and AP2 use version numbers. Sources: Model Context Protocol: Specification 2026-07-28; Model Context Protocol: Versioning; Anthropic: Donating the Model Context Protocol and establishing the Agentic AI Foundation (2025-12-09); A2A Protocol: Specification; A2A: A new chapter for A2A, joining the Agentic AI Foundation (2026-08-27); A2A releases (GitHub); Agentic Commerce Protocol (GitHub); AP2: Agent Payments Protocol; AP2 releases (GitHub); Universal Commerce Protocol: Specification overview (2026-08-25); Universal Commerce Protocol; WebMCP: Draft Community Group Report (W3C Web Machine Learning CG); Chrome for Developers: WebMCP (updated 2026-10-07); Microsoft: Introducing NLWeb (2025-05-19); NLWeb (GitHub). Last checked: .

Which protocol covers what? Agent protocols as of 2026-10-08Map of protocols for AI agents in four layers, as of 8 October 2026. Agent to tools and data: MCP, by Anthropic, at the Agentic AI Foundation since December 2025, version 2026-07-28. Agent to agent: A2A, donated by Google to the Linux Foundation, specification 1.0; it includes the Agent Card, a JSON description at /.well-known/agent-card.json. Agent to website: WebMCP, a draft of the W3C Web Machine Learning Community Group and not a W3C standard, in which a web page provides tools in the browser; NLWeb by Microsoft, open source, where every instance is also an MCP server. Agent to merchant, checkout and payment: ACP by OpenAI and Stripe (beta) with a checkout API and Delegate Payment; UCP by Google with commerce partners (stable) with checkout and payment handlers, plus AP2 mandates as an optional extension; AP2 by Google (v0.2) with a checkout mandate and a payment mandate. Cross-links: ACP and UCP can also be used via MCP, UCP also via A2A; AP2 is an extension for A2A and MCP.PROTOCOL · PUBLISHER · STATUSAs of 2026-10-08Agent ↔ tools, dataMCPModel Context ProtocolAnthropic; at theAgentic AI Foundation(Linux Foundation) since2025-12-09Version 2026-07-28Based on specifications andpublisher sites, checkedon 2026-10-08.↳ = link to otherprotocols.Grey: draft or beta.Agent ↔ agentA2A · Agent2AgentGoogle, donated to the LinuxFoundation; joining the AgenticAI Foundation announced on2026-08-27Specification 1.0(v1.0.1 of 2026-05-28)Agent CardJSON description of an agent:skills, endpoint, auth/.well-known/agent-card.jsonPart of the A2A specificationAgent ↔ websiteWebMCPW3C Web Machine Learning CommunityGroup (editors: Microsoft, Google)Draft of 2026-10-02, not a W3Cstandard; Chrome origin trial from 149↳ the web page provides tools in thebrowser, much like an MCP serverNLWebMicrosoft (announced 2025-05-19),open source under the MIT licence,no published version number;uses the site’s Schema.org and RSS↳ every NLWeb instance is alsoan MCP serverAgent ↔ merchant: checkout, payment, linksACPbeta, 2026-04-17Agentic Commerce ProtocolOpenAI and StripeAgentic Checkout: create,update and complete sessionsDelegate Payment: paymenttokens passed via the agent↳ REST; MCP binding sinceversion 2026-04-17UCPstable, 2026-08-25Universal Commerce ProtocolGoogle with commercepartnersCheckout capability: create,update, completePayment handlers; AP2 mandatesas an optional extension↳ REST, MCP, A2A,Embedded ProtocolAP2v0.2 (2026-04-28)Agent Payments ProtocolGoogle; standardisation inFIDO working groupsCheckout mandate: recordsitems and purchase detailsPayment mandate: authorises apayment with an instrument↳ extension for A2A and MCP;usable in UCP
Map of agent protocols as of 2026-10-08: which connection each protocol covers, who publishes it and what its status is. In commerce, ACP, UCP and AP2 overlap, and several protocols build on MCP or A2A. Versions change quickly. Sources: Model Context Protocol: Specification 2026-07-28; A2A Protocol: Specification (Agent Card, relationship to MCP); W3C Web Machine Learning CG: WebMCP (Draft Community Group Report); NLWeb (GitHub, Microsoft); Agentic Commerce Protocol (GitHub, OpenAI and Stripe); Universal Commerce Protocol: Specification overview; AP2: Agent Payments Protocol.

What does agentic commerce mean for online stores and SEO?

An agent can only work with what it can retrieve. That puts the focus on complete, current product information in machine-readable form, delivered through product feeds, structured data, or one of the protocol interfaces. Google names AI Mode in Google Search and the Gemini app as the first places where UCP-based purchases run. Under UCP, the merchant remains the merchant of record.

Example

A user tells an assistant: “Order waterproof trail running shoes in size 8, under $150, delivered by Friday.” The agent queries product data from several stores, filters by size, price, and shipping time, and suggests two pairs. After the user confirms one, the agent creates the cart with that merchant and pays with a token limited to this merchant and amount. The merchant ships the order and stays the seller.

Common mistakes

  • Missing checkout attribute in the product feed. Google’s UCP checkout requires the native_commerce attribute set to TRUE. If it is missing or FALSE, Google treats the product as not eligible for checkout.
  • Incomplete return policy. Merchant Center needs the return cost, the return window, and a link to the full policy. These details appear on the checkout screen.
  • No customer support contact. At least one contact method (website, email, or phone) is required. Google uses it for the “Contact Merchant” link on the order confirmation page.

Frequently asked questions

What are agentic payments? Payments that an AI agent initiates for a user. Protocols like AP2 add proof that the user approved the specific purchase, so the merchant and payment provider can tell an authorized agent from fraud.

Is agentic commerce the same as conversational commerce? According to reports, conversational commerce means shopping through a chat interface where the person still takes each step. In agentic commerce, the agent carries out the steps itself and the person approves the result.

Sources

  1. Developing an open standard for agentic commerce – Stripe Blog (Sep 29, 2025)stripe.com
  2. Announcing Agent Payments Protocol (AP2) – Google Cloud Blog (Sep 16, 2025)cloud.google.com
  3. Under the Hood: Universal Commerce Protocol (UCP) – Google Developers Blog (Jan 11, 2026)developers.googleblog.com
  4. OpenAI's plans to make ChatGPT more like Amazon aren't going so well – TechCrunch (Mar 24, 2026, secondary)techcrunch.com
  5. Universal Commerce Protocol: Specification overview (2026-08-25)ucp.dev
  6. Prepare your Merchant Center account – Google for Developers (UCP)developers.google.com
  7. About the Universal Commerce Protocol (UCP) and UCP-powered checkout feature on Google – Merchant Center Helpsupport.google.com
  8. AP2: Agent Payments Protocolap2-protocol.org

Last updated: