Checkout Handoff, Not Instant Checkout: Claude Commerce Agents vs ACP and Google UCP
Robauto Team · Published · Last updated
Anthropic’s Claude Commerce Agents (Sep 2026) hand off to merchant checkout; OpenAI Instant Checkout and Google UCP buy on AI surfaces. Brands need owned agents and inbound ACP/UCP readiness.
Agentic commerce is not one checkout model. As of September 2026, brands face at least three public paths: merchant-owned shopping agents that hand off to existing checkout (Anthropic’s Claude Commerce Agents blueprint), in-chat Instant Checkout via OpenAI’s Agentic Commerce Protocol (ACP) with Stripe, and checkout on Google AI surfaces via the Universal Commerce Protocol (UCP). The useful framing for builders is not “pick a model vendor.” It is checkout handoff versus Instant Checkout — and often you need both a merchant-owned agent and inbound agent readiness.
Three models, not one
Anthropic’s public FAQ is explicit: Claude is an intelligence layer, not a storefront or checkout, and Anthropic is not moving into owning catalogs, supply chain, or the last mile (claude.com/solutions/commerce). On September 2, 2026, Anthropic published the commerce-agents blueprint and an engineering deep-dive so teams can fork a shopping agent and a merchant agent into their own apps (launch post; anatomy post dated September 2, 2026).
OpenAI’s Instant Checkout, announced September 29, 2025, lets U.S. ChatGPT users buy eligible products inside chat, powered by ACP co-developed with Stripe (OpenAI; Stripe newsroom). Google announced UCP on January 11, 2026, as an open standard that will power checkout on eligible Google AI Mode and Gemini surfaces while retailers remain seller of record (Google blog).
| Dimension | Anthropic Claude Commerce Agents | OpenAI Instant Checkout / ACP | Google UCP | Source |
|---|---|---|---|---|
| Where purchase completes | Merchant’s own checkout (handoff); blueprint does not charge cards | Inside ChatGPT via Instant Checkout | On Google AI surfaces (AI Mode / Gemini) for eligible retailers | commerce-agents README; OpenAI; Google |
| Protocol / shape | Open-source agent blueprint (Apache-2.0); payment left to merchant rails | Agentic Commerce Protocol (ACP) + Stripe Shared Payment Token / delegated payments | Universal Commerce Protocol; compatible with A2A, AP2, MCP | GitHub; Stripe; Google |
| Seller of record | Merchant (relationships stay with the merchant by design) | Merchant remains merchant of record; ChatGPT passes order details | Retailer remains seller of record | Claude commerce FAQ; OpenAI; Google |
| Who builds | Brand / platform forks the reference repo (Messages API, Agent SDK, or Managed Agents) | Merchants integrate ACP / Instant Checkout; Stripe simplifies agentic payments | Merchants publish UCP profile and capabilities for Google (and other) agents | Anthropic; OpenAI; Google Merchant UCP |
| Product posture | Reference implementation, not a hosted Anthropic storefront product | Live Instant Checkout surface in ChatGPT + open ACP | Open standard + Google reference implementation on Search/Gemini | FAQ; OpenAI; Google Developers |
Note on marketing metrics: Anthropic’s commerce pages state that retailers running shopping agents on Claude have seen “carts up to 35% larger” and shoppers “60% more likely to complete a purchase,” and separately cite “40% higher conversion for small businesses selling through sales agents.” Those are Anthropic marketing claims on claude.com/solutions/commerce and the launch post — not Robauto measurements. Treat them as vendor claims until you validate on your own catalog and evals.
How Claude checkout handoff works
The anthropics/commerce-agents repository is licensed Apache-2.0 and described as a reference implementation that is not maintained as a product and does not accept contributions. The README’s safety contract is blunt: nothing places an order, charges a card, or changes a live listing — checkout renders the cart for the host to complete, and merchant writes are staged until a person approves them.
Two engineering details matter for brands:
- Checkout hands off. The checkout card links to the merchant’s checkout route or a platform hosted checkout URL. The backend returns the URL and the host renders it; the model never sees the checkout URL (README · “Checkout hands off”).
- Cart provenance and caps live in the harness. Anthropic’s anatomy post states that write/render paths accept only server-issued IDs, transaction caps are enforced on resulting state, and on the consumer side the backend interface the agent calls has no charge method — the model stages; a person or policy applies (anatomy · Safety).
Shopify’s public examples make the same handoff concrete against a real store: a non-empty cart is staged as a UCP checkout and the customer finishes via continue_url; complete_checkout is never called because that call places the order and takes payment (Shopify/claude-for-commerce-examples). Sign-in tokens and Admin tokens stay server-side and never reach the model.
Launch-page partners quoted by Anthropic include Shopify, Visa, Mastercard, Accenture, Klaviyo, Wix, Intuit, Square, Priceline, and others — useful as ecosystem signals, not as proof of any single conversion number (launch post; solutions page).
What brands should ship for each path
| Path | Ship this first | Why | Source |
|---|---|---|---|
| Claude / merchant-owned agent | Forkable shopping + merchant agent skills wired to your catalog, cart, and policy systems; keep payment on your checkout | You own the conversation surface and the relationship; payment stays on rails you already operate | Anthropic blueprint |
| OpenAI Instant Checkout | ACP-compatible checkout endpoints; Stripe agentic payments or Shared Payment Token / Delegated Payments Spec | Purchase completes in ChatGPT while you remain merchant of record | OpenAI; agenticcommerce.dev |
| Google UCP | Publish /.well-known/ucp profile and checkout capabilities for AI Mode / Gemini |
Eligible retailers can complete purchase on Google AI surfaces without leaving the research flow | UCP overview; Merchant UCP guide |
Constructive takeaway: a merchant-owned Claude agent answers “how do we help shoppers inside our app?” Instant Checkout and UCP answer “how do we sell when discovery happens on someone else’s AI surface?” Most durable brands will eventually need both classes of work.
Inbound readiness: the Robauto Agent Scan lens
Building your own shopping agent does not automatically make you discoverable or buyable by inbound agents. Robauto’s Agent Scan scores public discovery files across Signal Basics, Technical Groundwork, Agent Integration, and Agentic Commerce (ACP, UCP, AP2, x402, MPP, and related checks).
Live re-fetch on September 23, 2026 (America/Denver):
| Metric | Value | Source |
|---|---|---|
| anthropic.com Agent Scan score | 18 / 100 (label: Early) | robauto.ai/scan?url=anthropic.com |
| Agentic Commerce tier | 0 / 5 (ACP, UCP, AP2, x402, MPP all fail on the public homepage checks) | Same scan |
| Signal Basics | 4 / 6 | Same scan |
| Technical Groundwork / Agent Integration | 0 / 4 · 0 / 10 | Same scan |
| Robauto network AI traffic share (90d) | 21.49% (273,803 AI agent views / 1,274,349 page views) | robauto.ai/ai-search-data |
That anthropic.com score is not a roast. Corporate marketing sites are often not the commerce surface; it simply illustrates that shipping a commerce-agent blueprint and publishing inbound ACP/UCP discovery are different jobs. Brands should treat merchant-owned agents and inbound readiness (llms.txt, agent cards, ACP/UCP/AP2/x402 where you sell) as parallel workstreams.
Agent-ready checklist (JSON)
{
"as_of": "2026-09-23",
"thesis": "checkout_handoff_and_inbound_readiness",
"paths": {
"anthropic_claude_commerce_agents": {
"official_name": "Claude for commerce / Claude Commerce Agents",
"launch": "~2026-09-02",
"repo": "https://github.com/anthropics/commerce-agents",
"license": "Apache-2.0",
"checkout": "handoff_to_merchant_checkout",
"payment_credentials_in_model": false,
"checkout_url_through_model": false,
"merchant_writes": "staged_until_human_approval",
"shopify_example": {
"repo": "https://github.com/Shopify/claude-for-commerce-examples",
"ucp_cart": "create_checkout then continue_url",
"complete_checkout_called": false
}
},
"openai_instant_checkout": {
"announced": "2025-09-29",
"protocol": "ACP",
"payment_partner": "Stripe",
"where_purchase_completes": "inside_ChatGPT",
"merchant_of_record": "merchant"
},
"google_ucp": {
"announced": "2026-01-11",
"protocol": "UCP",
"surfaces": ["AI Mode in Search", "Gemini"],
"seller_of_record": "retailer",
"discovery": "/.well-known/ucp"
}
},
"brand_checklist": [
"Ship or fork a merchant-owned shopping agent that hands off to your checkout",
"Publish llms.txt and agent cards for discovery",
"Add ACP and/or UCP discovery if you want Instant Checkout / Google AI surface buys",
"Evaluate AP2 / x402 when mandate-based or metered agent payments matter",
"Keep payment credentials and hosted checkout URLs off the model path",
"Run Robauto agent_scan and close Agentic Commerce gaps deliberately"
],
"robauto_live": {
"anthropic_com_score": 18,
"agentic_commerce": "0/5",
"ai_traffic_percentage_90d": 21.49,
"sources": [
"https://robauto.ai/scan?url=anthropic.com",
"https://robauto.ai/ai-search-data"
]
}
}
Bottom line
Checkout handoff, not Instant Checkout is the right mental model for Anthropic’s Claude Commerce Agents: an open blueprint for merchant-owned shopping and merchant ops agents that deliberately leave payment on merchant rails. Instant Checkout (ACP + Stripe) and Google UCP are complementary inbound surfaces where discovery already happens. Brands that only build one side will either own a great in-app agent with weak reach, or join platform checkouts without a durable owned conversation. Ship both: merchant-owned agents and inbound readiness.
Sources
- Claude for commerce — solutions & FAQ
- Building commerce agents with Claude (launch)
- Anatomy of effective commerce agents (Sep 2, 2026)
- anthropics/commerce-agents (Apache-2.0)
- Shopify Claude for commerce examples
- OpenAI — Buy it in ChatGPT / Instant Checkout / ACP
- Stripe newsroom — Instant Checkout & ACP
- Agentic Commerce Protocol
- Google — UCP announcement (Jan 11, 2026)
- Google Developers — Under the Hood: UCP
- UCP specification overview
- Google Merchant UCP guide
- Robauto Agent Scan — anthropic.com
- Robauto AI Search Data
Sources
- Claude for commerce — solutions & FAQ
- Building commerce agents with Claude
- Anatomy of effective commerce agents
- anthropics/commerce-agents
- Shopify Claude for commerce examples
- OpenAI Instant Checkout / ACP
- Stripe newsroom — Instant Checkout & ACP
- Agentic Commerce Protocol
- Google UCP announcement (Jan 11, 2026)
- Under the Hood: Universal Commerce Protocol
- UCP specification overview
- Google Merchant UCP guide
- Robauto Agent Scan — anthropic.com
- Robauto AI Search Data
Where can an agent get this data live?
Robauto MCP — Agent Intelligence & Brand Discovery Infrastructure. A public, stateless Streamable HTTP endpoint at https://mcp.robauto.ai/mcp, callable with no key. Setup and the full tool list are in the Robauto MCP directory.