If you ship e-commerce or B2B catalog software, "agentic commerce" isn't a marketing buzzword you can ignore this cycle — it's a real integration surface. OpenAI's Agentic Commerce Protocol (co-built with Stripe) and Google's Agent Payments Protocol (AP2) both define how an AI agent can read your product catalog and complete a checkout without a human clicking through your UI.
From an engineering standpoint, the work breaks into three layers: machine-readable product data (clean schema.org/Product JSON-LD, kept in sync — not a one-time export), a feed an agent platform can actually pull from, and an order/payment endpoint that speaks one of these protocols against your existing payment gateway and inventory system. AP2's "mandate" model is worth studying closely if you're building the payment layer — it's a cryptographically signed authorization object, not a stored card number handed to a bot, which changes your fraud and consent handling meaningfully.
For Indian teams, there's a useful shortcut: if your catalog is already ONDC-integrated, you've done a good chunk of this groundwork already, since ONDC solves the same "any buyer agent, any seller catalog" problem at the network level.
We wrote up the fuller breakdown — including realistic cost tiers for Indian teams building this — here: Agentic Commerce Readiness: How Indian Businesses Get Discovered and Bought by AI Shopping Agents in 2026.
Curious what other dev teams are seeing — is anyone here already running ACP or AP2 in production, or still in sandbox?
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.