--- title: Agentic Commerce Readiness description: Make your store sellable to AI shopping agents. ACP and UCP protocol surfaces, an MCP server over your catalog, and product data that survives an agent comparison — built on AWS. url: https://www.factualminds.com/services/agentic-commerce-readiness/ category: agents updated: 2026-08-30 --- # Agentic Commerce Readiness > ACP, UCP and MCP surfaces for your catalog, plus product data that survives an agent's comparison. A fixed-scope engagement that ends with a shipped surface — not a strategy deck. ## Your catalog now has a second audience For twenty years, product data had one job: convince a person who was already looking at it. Photography carried the weight. Copy carried the tone. Specifications lived in a tab most people never opened. Shopping agents invert that. An agent asked to find a laptop under a weight threshold with a particular port configuration does not look at the photograph and does not read the tone. It reads attributes. A product whose weight lives in a sentence in the description rather than in a structured field is, to that agent, a product with no weight — and it does not get shortlisted. This is the whole problem in one sentence: **agents compare on attributes, not adjectives.** ## The two standards Two open protocols now govern how an agent discovers, compares and buys. The **Agentic Commerce Protocol** was created by OpenAI with Stripe and has been live in ChatGPT since September 2025, with partners including Instacart, DoorDash, Shopify and Etsy. The **Universal Commerce Protocol** launched in early 2026, led by Google alongside Shopify, Etsy and Walmart. Which one matters to you depends on where your buyers already are. What is worth understanding early is that the merchant-side work behind both is largely the same: a structured catalog, reliable identifiers, and a callable surface over your commerce data. Betting on the wrong standard is a recoverable mistake. Having a catalog no agent can parse is not a standards problem at all. ## What MCP has to do with it Model Context Protocol is the layer underneath. It is how an agent reaches your product, inventory and order data without you shipping a bespoke integration for every assistant that shows up. An MCP server over your catalog, hosted in your AWS account, gives you one surface to maintain, one place to enforce rate limits and authentication, and one audit log. It is also — and this is the part that gets underestimated — a public interface to your commercial data, which makes it an infrastructure and security design problem before it is an AI one. ## What this engagement does **Assess the surface.** Which protocol your channel mix actually justifies, and whether your platform is going to give you part of it for free. If the answer is "wait", we say so. **Audit the catalog.** Attribute completeness measured against what agents actually compare on in your category. Variant structure. Specification data currently trapped in prose. Join keys between product, inventory and pricing. The output is a backlog ranked by what blocks recommendation, not by what is easy. **Ship an MCP server.** Running in your AWS account, scoped to the reads you want exposed, with rate limiting, authentication and audit logging designed for a surface that faces the open internet. **Review the checkout path.** An agent-originated order still lands in your PCI-scoped checkout. We review the path it takes and, more importantly, where it must not be allowed to go. **Instrument what is measurable.** And name what is not. Attribution for agent-originated revenue is immature across the industry; we would rather set that expectation than sell around it. ## What this engagement is not It is not AgentCore Payments. Amazon Bedrock AgentCore Payments reached GA on August 18, 2026 and covers agent-to-API microtransactions against a session budget — an agent paying for an API call, an MCP server, or another agent. Useful, and a different layer entirely from a shopping agent buying a product on a person's behalf. It is also not the agents you run. Support, inventory, merchandising and margin agents operating inside your systems are the outbound half of agentic commerce — that is [eCommerce AI Agents on AWS](/services/ecommerce-ai-agents/). The two halves share a data foundation, which is why merchants who do the catalog work get a discount on the second project whichever order they run them in. ## Further reading We have published our thinking on this in the [eCommerce AI Agents field guide](/resources/ecommerce-ai-agents/), particularly: - [Your next customer may be an AI agent](/blog/ai-agent-as-next-customer-ecommerce-2026/) - [The AI-ready product catalog](/blog/ai-ready-product-catalog-agentic-commerce-2026/) - [Can your product data survive an AI comparison?](/blog/ai-product-comparison-optimization-ecommerce-2026/) - [Generative engine optimization for eCommerce](/blog/generative-engine-optimization-ecommerce-2026/) - [How to build an agent-ready storefront](/blog/agent-ready-ecommerce-storefront-2026/) ## Features ### Protocol Surface Assessment — ACP and UCP Which standard your channels actually need. The Agentic Commerce Protocol follows ChatGPT traffic; the Universal Commerce Protocol follows Google surfaces. Most merchants will eventually need both, and the underlying catalog work is largely shared. ### An MCP Server Over Your Catalog Model Context Protocol is how agents reach product, inventory and order data without a bespoke integration per assistant. Hosted on AWS, scoped to the reads you actually want exposed, with rate limits and audit logging. ### Product Data That Survives Comparison Agents compare on attributes, not adjectives. Missing dimensions, unstructured variants, and marketing copy where a specification should be are how a product quietly stops being shortlisted. ### Discovery and Generative Engine Optimization Staying visible when the thing choosing the SKU is a model rather than a shopper scrolling a results page — structured data, feed hygiene, and the signals that survive summarization. ### Checkout Path Review An agent-completed purchase still lands in your PCI-scoped checkout. We review the path an agent-originated order actually takes, and where it must not be allowed to go. ### Measurement Attribution for agent-originated traffic is not the same problem as attributing a click. We instrument what can be measured today and say plainly what cannot yet be. ## Why FactualMinds ### A Shipped Surface, Not an Assessment PDF The engagement ends with something callable running in your AWS account — an MCP server over your catalog, at minimum — plus the attribute backlog ranked by what actually blocks recommendation. ### We Say What Is Not Settled This is a young category with two competing standards and thin public data. Where the honest answer is "wait and instrument", we will give it. You are paying for judgement, not enthusiasm. ### The Catalog Work Compounds Structured attributes, reliable join keys and a callable surface over commerce data are the same foundations the agents you operate depend on. Nothing here is spent only on the inbound half. ### Built by AWS Infrastructure People An MCP server exposing your catalog to the open internet is an infrastructure and security problem before it is an AI one — rate limits, authentication, blast radius, and what happens under a scrape. That is our home ground. ## FAQ ### What are ACP and UCP, and do we need both? They are the two open standards for agent-driven purchasing. The Agentic Commerce Protocol was created by OpenAI with Stripe and has been live in ChatGPT since September 2025, with partners including Instacart, DoorDash, Shopify and Etsy. The Universal Commerce Protocol launched in early 2026, led by Google with Shopify, Etsy and Walmart. Which you need depends on where your buyers are — ACP follows ChatGPT traffic, UCP follows Google surfaces. Most merchants will eventually need both, and the underlying work of a clean, structured catalog with a callable checkout is largely shared between them. ### Is this the same thing as AgentCore Payments? No, and the distinction matters. Amazon Bedrock AgentCore Payments (GA August 18, 2026) covers agent-to-API microtransactions against a session budget — an agent paying for an API call, an MCP server, or another agent. It is not a consumer checkout replacement. ACP and UCP are the standards that govern a shopping agent buying a product from your store on a person behalf. Different layer, different problem. ### Our platform will handle this for us. Why engage anyone? Partly true and worth being honest about: if you are on Shopify, some of the protocol plumbing will arrive as a platform feature and you should not pay anyone to rebuild it. What no platform does for you is your catalog. Attribute completeness, variant structure, specification data that is currently prose in a description field, and the join keys between product and inventory — that is merchant-side work, it is the part that decides whether an agent shortlists you, and it is where this engagement spends most of its time. ### How do we know if it worked? Partially, and we will not pretend otherwise. You can measure catalog completeness against the attributes agents actually compare on, and you can measure whether your MCP surface returns what it should under load. Attribution for agent-originated revenue is genuinely immature across the industry right now. We instrument what is measurable, flag what is not, and revisit as the standards mature. ### Should we just wait? For the protocol surface, waiting is a defensible position and we will say so if it fits your channel mix. For the catalog work, waiting costs you nothing to start and is the long pole regardless of which standard wins — structured attributes and reliable join keys have been worth doing since long before agents existed. If you do one thing, do that. --- *Source: https://www.factualminds.com/services/agentic-commerce-readiness/*