Agentic commerce needs evidence behind the interface.
Agentic commerce includes software agents helping people find products and work through shopping tasks. The useful question is specific: can an agent read accurate product information, query a catalogue, prepare a cart or complete an authorized transaction?
Explore transaction-oriented publishers · Find declared MCP interfaces
Separate information from actions
| Stage | Useful evidence |
|---|---|
| Understand the business | Clear public pages, policies and an llms.txt pointing to useful material |
| Find products | Current product data and a documented search or catalogue interface |
| Prepare a purchase | Documented cart, shipping and pricing behavior with stated permissions |
| Complete a transaction | Explicit authorization, payment and confirmation flows for the actual service |
A commerce category, storefront template or “transactional” label does not prove checkout works through an agent. Our labels are inferred discovery signals; read the publisher’s documentation and check the actual interface.
Find the right starting point
Search by the publisher and task through resolve, inspect match strength and freshness, then read the linked source. Narrow the directory by country, topic or publisher-declared MCP capability. Keep location inference and directory authority separate from evidence of a working integration.
Prepare an ecommerce website
Publish accurate product and policy information, make important pages readable, and describe the site with a concise file. Audit the public signals and generate a draft. If you expose an interface, publish its endpoint and authentication requirements.
For specific integration details, use primary references such as Stripe’s agentic commerce guide and Shopify’s Storefront MCP migration guide. Shopify’s current migration guide replaces older catalog and cart tools with UCP at /api/ucp/mcp; Customer Accounts MCP has a separate scope. Follow the current publisher instructions rather than assuming an older /api/mcp integration still exposes every tool.
What a useful map should show
Record the publisher, declared interface, source URL, check time and tested scope. Keep declared, observed and successfully exercised capabilities distinct. Shared platform or file headings can help exploration, but they are not proof of commercial relationships or independent adoption.
More: WebMCP: give agents a clearer way in. · Can AI find, understand and cite your website? · Check what an MCP endpoint actually returns. · Find the right documentation before using it. · The llms.txt project · What is llms.txt? · llms.txt examples · llms.txt best practices · checker · generator