Stripe's technical field guide for agentic commerce explains the concrete infrastructure changes businesses need to make to be discovered, parsed, and transacted with by AI shopping agents — from robots.txt configuration to ACP-compliant checkout endpoints.
Infrastructure readiness assessment from Stripe's technical field guide. Most businesses have the product data — the gap is in how it's exposed to agents.
A human browsing your website can handle ambiguity: they can infer product availability from contextual cues, manually navigate checkout flows, and work around CAPTCHAs or login friction. An AI agent cannot. When an agent sent by a user to purchase a product hits your website, it needs machine-readable product data, a clear path through your checkout flow, and real-time confirmation that the item is in stock right now. If any of those conditions fail, the agent abandons the task — and your potential sale — silently.
Stripe's field guide addresses this with a three-layer framing: Discovery (can agents find and parse your products?), Access (can agents authenticate and act on behalf of buyers?), and Transaction (can agents complete a purchase through a structured API?). Most businesses in 2026 have partial coverage at best: their product catalog exists but is formatted for human browsing, not machine consumption; their checkout flow assumes a human in the loop; and their authentication systems don't support buyer-delegated agent access.
The first thing to audit is your robots.txt configuration. Many businesses have blanket crawler restrictions that were designed to protect against scraping but inadvertently block legitimate AI shopping agents. The key is to differentiate between verified commerce agents and generic scrapers. Stripe's guide identifies the main agent user agents to explicitly allow: GPTBot (OpenAI), ClaudeBot (Anthropic), and Google-Extended, among others, with the full list available in each provider's official crawler documentation.
Beyond robots.txt, agents need structured product data. The current norm — HTML pages designed for visual parsing by humans — forces agents to attempt fragile DOM scraping. The recommended path is to expose your product catalog through a dedicated ACP endpoint: a near-real-time feed of product details, pricing, and availability that agents can query programmatically. Stripe's Agentic Commerce Suite lets businesses upload their product catalog directly and syndicate it across multiple AI agents from a single source of truth, eliminating the fragmentation that comes from maintaining separate catalog formats for each platform.
The Agentic Commerce Protocol (ACP) is the open standard at the center of Stripe's approach. Co-developed with OpenAI and released in September 2025, ACP provides a RESTful interface (and an MCP server implementation) that agents can use to browse products, place orders, and handle payment authorization without requiring a human to interact with a checkout UI. A business that implements ACP endpoints becomes natively accessible to any AI agent built on the protocol.
Stripe's field guide is explicit about one practical reality: the protocol landscape is still evolving. Google has its own Universal Commerce Protocol (UCP), and other standards are emerging. The recommendation is therefore to build on a protocol-agnostic commerce layer — specifically Stripe's Agentic Commerce Suite — that handles multi-protocol translation automatically, rather than betting your roadmap on any single spec. A business using the Suite can support ACP, Google UCP, and future protocols without rebuilding their product catalog or payment integration each time.
Check your current configuration against known commerce agent user agents. Ensure GPTBot, ClaudeBot, and Google-Extended are explicitly permitted — without exposing sensitive admin routes to generic crawlers.
Deploy an optimized product catalog feed with standardized schema. Include real-time pricing, inventory levels, and variant data. Static exports break agent workflows that need millisecond-accurate availability.
Add ACP-compliant purchase, cart, and payment handler endpoints. These enable agents to complete transactions programmatically without requiring a human to navigate your existing checkout UI.
Implement scoped token support so agents can authenticate on behalf of buyers without holding full account credentials. Limits the blast radius if an agent session is compromised.
Stripe's Agentic Commerce Suite handles protocol translation, letting sellers operate across ACP, Google UCP, and future standards without rebuilding integrations.
Stripe. (2026). How to prepare for agentic commerce: A technical field guide. Stripe Guides. stripe.com/guides/how-to-prepare-for-agentic-commerce-technical-field-guide