Agents Are Coming to Shop. Can They Read Your Menu?

Three protocols. Three tech giants. One question: who owns the buy button when your customer is an AI?

Last week, three separate announcements landed within days of each other: Amazon launched an MCP server for its ads platform. Google and Walmart rolled out the Universal Commerce Protocol. OpenAI and Stripe shipped the Agentic Commerce Protocol.

Three protocols. Three different visions for how AI agents discover, evaluate, and purchase things on behalf of humans. And if you’re an indie builder selling anything — digital products, templates, SaaS, services — this is the week the future of your checkout started being decided without you in the room.

Three Protocols, Three Power Grabs

MCP (Model Context Protocol) — Anthropic’s open standard, now adopted far beyond Claude. MCP standardizes how AI agents connect to external data and tools. It’s the plumbing: your agent discovers what’s available, authenticates, and executes. Amazon building an MCP server for advertising — not inventing their own protocol — is the clearest signal yet that MCP won the “how agents talk to services” layer.

ACP (Agentic Commerce Protocol) — OpenAI + Stripe’s answer to “how do agents pay for things?” Currently optimized for single-item purchases inside ChatGPT and Copilot. The payment flows through Stripe, the experience never leaves the chat window. It’s slick. It’s also a walled garden.

UCP (Universal Commerce Protocol) — Google, Walmart, and Target’s play. The most ambitious: standardize the entire shopping lifecycle. Discovery, comparison, checkout, tracking, returns. Publish your product catalog once, any UCP-compliant agent can find and sell it. Google wants to be the DNS of commerce.

Why This Matters Right Now

The browser wars gave us a decade of “works best in Chrome” badges. The protocol wars are about to give us “optimized for Claude” or “buy via ChatGPT” checkout experiences.

But here’s the part nobody’s saying out loud: these protocols aren’t competing for human customers. They’re competing for agent customers.

When Anthropic’s Claude agent goes shopping for its user, it speaks MCP. When ChatGPT’s agent handles a purchase, it uses ACP through Stripe. When a Google-ecosystem agent compares products, it queries UCP.

The agent your customer uses determines which protocol reaches your checkout. And you, the merchant, had no say in the matter.

This is the new platform risk. It’s not “which app store takes 30%.” It’s “which AI assistant’s protocol stack can even see your product.”

What Agents Actually See

Here’s where the protocols converge on something useful for indie builders: regardless of which protocol an agent speaks, it still needs to understand what you sell.

An agent evaluating your product doesn’t see your hero image. Doesn’t feel the emotional resonance of your brand story. Doesn’t notice the clever microcopy on your checkout button. It parses your structured data, evaluates your entity authority, checks your machine-readable trust signals, and either recommends you or skips you — in milliseconds, without ever rendering your CSS.

Every protocol needs the same raw material: clear, structured, machine-readable information about what you offer, what it costs, and how to get it.

MCP needs tool definitions and endpoints. ACP needs product metadata flowing through Stripe. UCP needs standardized catalog entries. But underneath all three, the question is identical: can an agent figure out what you sell?

If the answer is no, it doesn’t matter which protocol wins. You’re invisible to all of them.

The Indie Builder’s Playbook

You don’t need to implement three protocols. You need to make your product legible to any agent that comes looking.

1. Machine-readable product information is table stakes. JSON-LD structured data on your landing pages. Clear pricing visible on the page (not hidden behind “contact us” or “book a demo”). An llms.txt file at your domain root explaining what you sell and how to buy it. This is the minimum viable product surface for agentic commerce.

2. MCP is the only protocol worth watching right now. It has the broadest adoption, the most diverse ecosystem, and it’s not locked to one AI provider. Amazon building on MCP tells you where the gravity is. If you build one machine-readable integration for your product, make it an MCP endpoint. Any MCP-compatible agent can use it — and that’s the largest and fastest-growing pool.

3. ACP and UCP are enterprise plays for now. ACP is ChatGPT-only and Stripe-only. UCP is ambitious but early and Google-centric. Both will matter eventually. Neither matters for a solo builder in March 2026. Watch them. Don’t build for them yet.

4. Think in product catalogs, not marketing pages. Whether it’s a simple products.json or a full MCP server, the exercise of making your offerings machine-parseable pays off regardless of which protocol wins. Describe your product the way a database would: name, description, price, features, availability, purchase URL. That structured data is the common substrate underneath every protocol.

5. Front-load your value proposition. When an agent reads your landing page to decide whether to recommend you, 44% of LLM citations come from the first 30% of a page’s text. Your opening paragraph isn’t an intro — it’s your pitch to every agent that will ever evaluate you. Write it as a standalone statement of what this is and why it matters.

The Real Race

The protocol war isn’t really about protocols. It’s about who mediates the transaction between an AI agent and a merchant.

Anthropic wants it to be the MCP ecosystem (open, extensible, they benefit from Claude adoption). OpenAI wants it inside ChatGPT (they take a cut via Stripe integration). Google wants it everywhere (they take a cut via discovery and ads).

Sound familiar? It should. Search → social → agents. The customer acquisition channel changes, the power dynamics don’t. Whoever controls the protocol controls the recommendation.

But here’s the thing about platform wars: the merchants who survive them are never the ones who bet everything on one platform. They’re the ones who made their product so clearly described, so easy to find, so unambiguous in what it offers, that every platform could surface it.

The indie builder’s advantage hasn’t changed: be small, be fast, be findable. The agents are coming to shop. Make sure they can read your menu.

---