Magento 2 Agentic Commerce

Agentic Commerce for Magento 2 exposes your store through the standards agents actually use. It publishes a UCP merchant profile at /.well-known/ucp, runs a generic Model Context Protocol (MCP) server for agents that connect directly, registers WebMCP tools on your storefront pages for agents working in the shopper's browser, and implements OpenAI's Agentic Commerce Protocol (ACP) for the product feed, checkout sessions, delegated payments, and webhooks. Every surface has its own on and off switch behind a single master switch, so you enable only what you want.

Agent discovery and instructions

The extension ships the files agents look for. It generates llms.txt and a byte-identical agents.md from a template you control, adds an agent discovery sitemap referenced from your main sitemap, and injects an agent block into robots.txt. Because it also serves llms.txt at the domain root and registers WebMCP tools on the page, your store is set up for Google PageSpeed Insights' Agentic Browsing checks. The instructions template uses simple variables for your store name, categories, CMS and policy pages, and featured products, so agents get accurate, up-to-date guidance on how to connect.

Agent-built carts with shopper handoff

Agents can search your catalog, inspect products, and build a cart on the shopper's behalf using the MCP cart tools. Every cart response includes a continue URL, so the shopper can pick up exactly where the agent left off. Following that link restores the agent-built cart into the shopper's browser session and lands them on the cart or checkout page, on both Luma and Hyvä, with items, quantities, and totals intact.

Agentic checkout with delegated payments

For UCP and MCP flows, shoppers always complete payment in your normal checkout. Payment inside the agent conversation is supported only through the ACP checkout sessions flow, which follows OpenAI's spec exactly, maps sessions to real Magento quotes for accurate pricing, tax, and shipping, and processes delegated payment tokens through Stripe. Orders are placed through standard Magento order management, so inventory, confirmation emails, and admin records all behave as usual.

Agent Activity analytics

A dedicated Agent Activity dashboard shows how agents interact with your store. You get KPI tiles for agent calls, unique agents, attributed orders, and attributed revenue, a funnel from discovery to search to cart to order, endpoint usage, a top agents table, and top agent queries with zero-result queries highlighted as unmet demand. A built-in test runner lets you run a read-only agent flow and see each request and response, and telemetry is captured off the response path with no buyer personal data.

Built for security, performance, and Hyvä

ACP endpoints enforce bearer token authentication, HMAC signature verification, idempotency replay protection, timestamp tolerance, and API-version checks, with rate limiting and prompt-injection hardening across agent inputs. Read APIs are served with public cache headers and Redis-backed caching for fast responses. All Hyvä theme and Hyvä Checkout support lives inside the single module, with a dependency-free WebMCP script for Hyvä and a RequireJS component for Luma.

Features of Agentic Commerce for Magento 2

• UCP merchant profile: publishes a standards-based profile at /.well-known/ucp declaring your capabilities and agent endpoints.

• Generic MCP server: exposes search_catalog, get_product, lookup_catalog, and cart tools over JSON-RPC for connected agents.

• WebMCP on-page tools: registers the same catalog tools in the shopper's browser for in-page agents.

• OpenAI ACP support: product feed, checkout sessions, delegated payments, and webhooks per the ACP spec.

• Agent instructions: template-driven llms.txt and agents.md with a live preview.

• Public JSON read API: cacheable product, category, and search endpoints for agents and tools.

• Agent cart and handoff: agent-built carts with a continue URL that restores the cart into the shopper session.

• Delegated payments via Stripe: processes ACP payment tokens through your Stripe account.

• Signed webhooks: sends order.created and order.updated events for agent-originated orders.

• Per-product controls: flags to feature a product, hide it from agents, or block agentic checkout.

• Agent Activity dashboard: funnel, KPIs, top queries, zero-result demand signals, and attributed revenue.

• Security stack: bearer auth, HMAC signatures, idempotency, rate limiting, encrypted secrets, and audit logging.

• Luma and Hyvä ready: one module supports both themes and Hyvä Checkout.

How It Works

1. Install the extension and turn on the master switch under Stores > Configuration > Meetanshi > Agentic Commerce.

2. Enable the surfaces you want: UCP profile, MCP server, JSON read API, WebMCP, agent instructions, and discovery in sitemap and robots.

3. Edit the agent instructions template and mark the products you want featured to agents.

4. For agentic checkout, enable ACP checkout sessions, set your API key, and connect Stripe for delegated payments.

5. Generate the ACP product feed on demand, by CLI, or on a cron schedule, with a static file mode for large catalogs.

6. Watch the Agent Activity dashboard to see how agents discover, search, and buy, and act on zero-result demand signals.

Agent Surfaces and Controls

Every agent-facing URL is gated by a switch, and returns 404 when its surface or the master switch is off, so you stay in control of what agents can see and do. Read surfaces (JSON API, MCP read tools, WebMCP) are read-only and never expose customer, order, or payment data. Cart tools appear only when Agent Cart is enabled, and payment is only ever taken through your own checkout or the ACP delegated payment flow. At the product level, you can feature an item in agent instructions, remove it from all agent read surfaces, or keep it readable while blocking agentic checkout.

Who Needs Agentic Commerce for Magento 2

• Merchants who want their catalog to be found and bought through AI shopping assistants
• Stores preparing for OpenAI ACP and agent-driven checkout without leaving Magento
• Brands that want to measure agent traffic, demand, and attributed revenue
• Hyvä and Adobe Commerce stores that need agent readiness in a single module
• Teams that want strict control over what agents can read, add to cart, and purchase