Anthropic Publishes an Open Commerce Agent Blueprint, and Leaves Payment to the Merchant

On 2 September 2026 Anthropic published an open commerce agent blueprint: reference implementations of a shopping agent and a merchant agent built on Claude, released on GitHub with a Claude Code plugin and live demos for retail, travel, telecom and ticketing. Accenture, Mastercard and Visa are named as ecosystem partners, and Shopify has published its own implementation over UCP and Sign in with Shop. The shopping agent searches the catalogue, assembles a cart and hands it to checkout. Anthropic’s announcement says payment is left to the merchant.

Editor’s note: this page is built from Anthropic’s announcement, the linked repositories and Shopify’s public implementation, verified 4 September 2026. The performance figures quoted below are Anthropic’s own and carry no published methodology; they are attributed rather than stated as fact.

What was released

Anthropic describes the blueprint as containing “the harnesses, patterns, and guardrails an engineering team needs to get a commerce agent running in days”. It is available at github.com/anthropics/commerce-agents, and the code deploys on the Claude API, Amazon Bedrock, Microsoft Foundry or Google Cloud Vertex AI. The agents can be built using the Messages API, the Agent SDK, or Claude Managed Agents (beta).

Two reference implementations ship in the repository.

The shopping agent runs inside the merchant’s own app or website. Anthropic lists integration points for catalog, cart, checkout, customer preferences and order history. The agent searches the catalogue and assembles multi-item orders, remembers customer preferences, renders products, comparisons and the cart in the conversation rather than as plain text, builds the cart and hands it to checkout, and answers customer service questions in the same conversation, including order status, returns, exchanges and refund policy. Anthropic states the agent “features guardrails designed to constrain prices and products to actual catalog data, and avoids manipulative upsell patterns”.

The merchant agent serves store operators. It answers sales performance questions, tracks inventory and flags problems such as an item about to sell out before a promotion starts, recommends pricing and promotions from the store’s own sales history, and drafts marketing campaigns. Anthropic notes that when the agent proactively suggests a change, a person approves it before anything goes live.

The boundary is where it stops

The commercially significant sentence in Anthropic’s announcement is about the shopping agent’s integration points: the blueprint “leaves payment to you, whether that is your existing checkout or an agentic payments provider”.

Anthropic is not shipping a payment rail, a wallet, an agent credential scheme or a protocol of its own here. The agent builds the cart and hands it over. That is a deliberate boundary, and it sits Anthropic in a different position from the checkout-owning approach taken by OpenAI and Stripe with the Agentic Commerce Protocol, or by the card networks with their own agent payment products.

Two shapes of agentic commerce are visibly forming. In the first, a buyer converses with a third-party assistant and the purchase completes on that assistant’s surface. In the second, the merchant runs the agent on its own site, and keeps the customer relationship, the behavioural data and the payment relationship. This release is infrastructure for the second, and it does not foreclose the first: a merchant can adopt the blueprint and still route payment through an agentic payments provider.

The Visa quote in the announcement makes that positioning explicit. Jack Forestell, Visa’s Chief Product and Strategy Officer, describes the collaboration as “empowering merchants to deliver better customer experiences while maintaining the relationships that drive their businesses forward”. Mastercard’s Sherri Haymond frames it as “helping merchants build their own agents with Claude to drive their growth”.

Shopify’s implementation is the practical on-ramp

Shopify has published its own implementations on top of the blueprint: a storefront shopping agent over Shopify’s UCP endpoints and Sign in with Shop, and a merchant agent over the Admin API. Shopify’s VP Product Vanessa Lee describes it in Anthropic’s announcement as “a reference storefront implementation that connects them to a merchant’s store through Catalog, UCP and Shop Sign-in”.

For a Shopify merchant, this shortens the distance between the announcement and a working agent considerably. It also puts UCP, the protocol Google announced at NRF 2026 and Shopify has since implemented, on the merchant-agent path as well as the third-party-assistant path.

Both repositories are open reference code rather than supported products. Teams fork them and own what they build.

The performance claims, and how to read them

Anthropic’s announcement headline states that “retailers running shopping agents on Claude have seen carts up to 35% larger and shoppers 60% more likely to complete a purchase”. No methodology, sample, time period or baseline is published alongside those figures, and no third party has verified them. They should be read as a vendor claim rather than as measured industry data.

The named-customer quotes are more checkable in kind, and mostly concern implementation speed rather than commercial outcome. Fetch’s Ashley Nader reports both agents “running locally in well under an hour”. Zomato’s Akhil Bansal reports the setup “worked exactly as documented”. Wix’s Dror Zalika reports “a working commerce agent taking prompts within fifteen minutes”. These are participant reports in a vendor announcement, useful as a signal of how packaged the release is and not as independent benchmarks.

Why it matters for merchants

Anthropic explicitly frames the timing: available “just in time for holiday season planning”. That is the practical read. A merchant considering an agent on its own storefront for the 2026 peak season now has a starting point that is days rather than months of scaffolding, from a frontier lab, with the two largest card networks and a global systems integrator publicly attached to it.

The gating factor is unlikely to be the agent. It is whether the catalogue, policy and order data behind it can answer an agent’s questions. A shopping agent that assembles a multi-item order needs accurate structured attributes; one that answers returns questions in-conversation needs the returns policy in a form it can query rather than a PDF. That readiness work is the same work that makes a business legible to third-party assistants, which is a reason to do it once and use it on both paths.

What to watch

• Whether Anthropic stays out of payment, or whether a later release adds an agent payment capability of its own. The current boundary is a positioning choice, and positioning choices change.
• Which other commerce platforms follow Shopify in publishing a first-party implementation over the blueprint. That is the signal of whether this becomes a de facto merchant-side pattern.
• Whether Visa and Mastercard’s involvement produces anything specific beyond enablement, in particular whether either wires its own agent authentication or tokenisation into a reference path.
• Adoption evidence over the holiday period that is independent of Anthropic’s own reporting.