Anthropic Open-Sources a Commerce Agents Blueprint for Claude
Anthropic has launched an open-source blueprint for building commerce agents with Claude. It includes shopping and merchant agent implementations, demos across retail, travel, telecom, and ticketing, guardrails, and a Claude Code plugin.
Anthropic has open-sourced Claude Commerce Agents, a blueprint for building shopping and merchant agents. The release includes reference implementations across retail, travel, telecom, and ticketing, plus a Claude Code plugin to help an engineering team start from the blueprint. (ClaudeDevs on X; Anthropic announcement; Commerce Agents repository)
Anthropic describes the project as a way to get a commerce agent running in days using the harnesses, patterns, and guardrails included in the blueprint. It is available today, with live demos for each vertical and an engineering deep-dive for teams evaluating the architecture. (Anthropic announcement)
Two reference agents, not just a prompt pack
The repository contains working implementations of two distinct agent types:
- Shopping agent: runs inside an app or website and connects to catalog, cart, checkout, customer preferences, and order history. Payment remains with the existing checkout or an agentic payments provider chosen by the implementer.
- Merchant agent: helps store operators answer questions about sales, inventory, pricing, and promotions. It can flag inventory problems, recommend discounts, and draft marketing campaigns from the store's own data.
Anthropic says the shopping agent's guardrails constrain prices and products to actual catalog data and avoid manipulative upsell patterns. The merchant agent requires human approval before a proactively suggested change goes live, so the store operator retains the final say. (Anthropic announcement)
Build on Claude's existing agent surfaces
The blueprint's implementations can be built with the Messages API, the Agent SDK, or Claude Managed Agents, which Anthropic labels beta. Developers can use Claude Code to customize the agents for their catalogs, policies, brand, and backend rather than assembling the scaffolding from scratch. (Anthropic announcement; Commerce Agents repository)
Anthropic says the code deploys where teams already build with Claude:
- Claude API
- Amazon Bedrock
- Microsoft Foundry
- Google Cloud Vertex AI
The announcement also names Accenture, Mastercard, and Visa as ecosystem or solutions partners working with Anthropic on commerce-agent adoption. Those partnerships do not change the fact that teams still need to connect their own catalogs, policies, checkout, and business data. (Anthropic announcement)
A practical starting path
Anthropic's getting-started sequence is:
- Fork
anthropics/commerce-agents. - Read the engineering deep-dive on the architecture, latency, cost techniques, and evaluation practices.
- Try the vertical demos.
- Use Claude Code and the included plugin to adapt the agent to the team's catalog, policies, and backend.
- Choose the deployment surface and connect the business systems that the agent must query or update.
The project is a blueprint rather than a turnkey storefront. The shopping agent leaves payment to the implementer's existing checkout or payments provider, and the merchant agent operates on the store's own data. Teams still own the integrations, approval rules, security review, and production operations. (Anthropic announcement; Commerce Agents repository)
What the release signals for agent builders
Commerce agents need more than a model call: they need catalog and inventory tools, policy constraints, user context, approval gates, and an interface that can explain what the agent is doing. Anthropic's blueprint packages those pieces as reusable implementations and skills rather than leaving every team to design them independently. (Anthropic announcement)
That makes the release useful even for teams that are not building a retailer-facing chatbot. The same structure—domain tools, guardrails, human approval, and a deployable agent workflow—can serve as a reference for other systems where an agent must act on business data without making unreviewed changes. The announcement does not claim that the blueprint is a universal template for every industry, so teams should treat that broader use as an architectural starting point, not a guarantee.
Sources
- ClaudeDevs on X, “We're open-sourcing Claude Commerce Agents,” September 2, 2026: https://x.com/ClaudeDevs/status/2095233745167282602
- Anthropic, “Building commerce agents with Claude”: https://claude.com/blog/claude-for-commerce-agents
- Anthropic, “Commerce Agents” repository: https://github.com/anthropics/commerce-agents
- Anthropic, “A guide to the anatomy of effective commerce agents”: https://claude.com/blog/the-anatomy-of-effective-commerce-agents
Read next
Keep building the workspace playbookClaude Platform Makes Computer Use, Browser Use, Skills, and Files Generally Available
Anthropic says computer use, browser use, the Skills API, and the Files API are now generally available on the Claude Platform, combining multi-action software control with versioned skills and reusable files for production agents.
Claude Platform's 'ant' CLI Brings the Full Claude API to Your Terminal
Anthropic's Claude Platform documents 'ant', a command-line tool that exposes every Claude API resource as a subcommand. It sends Messages requests, browses responses, version-controls agents and environments, and runs a self-hosted Managed Agents worker, with Claude Code able to drive it natively.
Claude Managed Agents Add Memory Stores, Domain Controls, and a Redesigned Console
Anthropic's Claude Managed Agents updates let self-hosted sandbox sessions attach memory stores, restrict web_search and web_fetch with allowed_domains or blocked_domains, and inspect multi-agent sessions in a redesigned Claude Console viewer.
Frequently Asked Questions
What did Anthropic release?
Anthropic launched an open-source Commerce Agents blueprint with working shopping and merchant agent implementations, patterns, harnesses, guardrails, vertical demos, and a Claude Code plugin.
Which commerce scenarios are included?
The blueprint includes reference implementations and demos for retail, travel, telecom, and ticketing platforms. The shopping agent handles catalog, cart, checkout, preferences, and order-history integration points, while the merchant agent works with sales, inventory, pricing, and promotions data.
Where can Commerce Agents run?
Anthropic says the code can deploy where teams already build with Claude, including the Claude API, Amazon Bedrock, Microsoft Foundry, and Google Cloud Vertex AI.
How can a developer get started?
Anthropic directs developers to fork the `anthropics/commerce-agents` repository, review its engineering deep-dive, try the vertical demos, and use the included Claude Code plugin to customize an agent against their own backend.