CartPassHome

Agent commerce, explained

AI assistants have started doing the shopping. This page is the plain-language version of what that means for a store — who the agents are, what the new standards do, and what’s worth doing first. We keep it current as the standards are adopted.

What’s changed

People have started asking AI assistants where to buy. The assistant answers with named stores, and increasingly goes and buys from one, working the same product pages and checkout your human customers use.

So two things now decide a sale before anyone reaches your site: whether an assistant names your store at all, and whether what it tells the shopper about your prices, shipping and returns matches what you publish. A shopper acts on the answer, whether or not your site agrees.

To your storefront, that shopper looks like a bot — because it is one. Defences built for scrapers can’t tell a buying agent from a bad one, so the default outcome is a blocked sale that no dashboard ever shows you. Blocking automation is a legitimate choice; the point is to make it a choice.

Standards are forming quickly around four jobs: proving which agent is knocking (identity), reading what you sell (discovery), completing a purchase without driving your UI (checkout), and paying with the owner’s authority (payment). You don’t have to adopt any of it today — but it pays to know which layer each headline belongs to, and what your platform is already doing on your behalf.

The standards, in one place

Web Bot Auth

Identity Adopted IETF · RFC 9421

Lets an agent cryptographically sign its requests so your site can tell a verified shopping agent from an anonymous scraper. This is the mechanism allowlists ride on.

Honoured by Shopify since May 2026. Cloudflare support rolls out from September 2026, and its agent-bot defaults change on 15 September 2026.

Your move: Ask your bot-defence provider about allowlisting verified agents — you can let trusted shoppers in without opening the door to scrapers. If Cloudflare fronts your store, check that setting before mid-September.

UCP

Discovery Rolling out Google & Shopify

A well-known endpoint (/.well-known/ucp) that describes your catalogue and cart to agents, so they can shop your store without clicking through it like a person.

Shopify auto-enrolls stores via Agentic Storefronts — if you sell on Shopify, you may already have it.

Your move: On Shopify, confirm you’re enrolled. Elsewhere, watch your platform — this arrives as a platform feature, not a DIY project.

ACP

Checkout Rolling out OpenAI & Stripe

Lets a purchase complete inside the chat: your product feed goes in, an order comes out, without the agent driving your storefront at all.

Live inside ChatGPT for enrolled merchants — the route to your products being bought without the shopper leaving the chat.

Your move: Keep a clean product feed and ask your platform about ACP support.

MCP

Checkout Emerging Anthropic · industry-wide

A general standard for AI assistants to call tools and services directly. A commerce MCP endpoint gives agents a structured way to search and buy instead of scraping.

Widely adopted for assistant tooling; commerce endpoints are still early.

Your move: If your platform offers a commerce MCP endpoint, advertise it.

AP2

Payment Emerging Google-initiated · FIDO-governed

A protocol for proving the human actually authorised the agent’s payment — a mandate that travels with the transaction.

Specification stage; support signals only.

Your move: Nothing to install yet — this will arrive through your payment provider.

Shared Payment Token

Payment Emerging Stripe, with ACP

A scoped payment credential an agent can hold instead of a card number — limited to one merchant and amount, so a leaked token is not a leaked card.

Pairs with ACP; Stripe first.

Your move: Comes via your payment provider — no merchant work yet.

Visa Intelligent Commerce & Mastercard Agent Pay

Payment Emerging Visa · Mastercard

The card networks’ programmes for recognising agent-initiated transactions, so a legitimate agent purchase isn’t scored like fraud.

Programmes announced; enrolment runs through acquirers. Visa’s was called Trusted Agent Protocol (TAP) before the rebrand, and both names are still in circulation.

Your move: Ask your acquirer whether agent-initiated transactions are recognised.

Identified vs anonymous — the split that matters

Platforms now treat cryptographically verified agents differently from anonymous bots. That means your agent-readiness is really two numbers: how you treat agents who prove who they are, and how you treat the long tail who don’t. A store can be wide open to one and walled off to the other without knowing it.

The purchase attempts in a paid panel run both ways and are reported separately. The gap between the two is the first thing worth knowing about your own store.

Where to start

Make your product data machine-readable. schema.org Product and Offer on every product page, with per-variant price and stock — the cheapest fix with the widest reach.
Keep a guest checkout, and make it findable. An agent buying for a first-time customer has no account to sign in with.
Make your variant picker work without a mouse. If it works with a keyboard it usually works for AI shoppers — and for screen readers.
Decide your door policy on purpose. Blocking all automation is a legitimate choice; the alternative is allowlisting verified agents, not switching your defences off.
Publish the cheap signals. AI directives in robots.txt, a valid sitemap, llms.txt — then the protocol endpoints as your platform ships them.
Measure it. Count who the assistants name when your shoppers ask, and compare what they say about your prices and policies with what your own pages say — then watch one try to buy.

Plain words

Agent commerce: Shopping done by software on a person’s instruction — the person decides, the agent executes.
AI shopping agent: The assistant doing the shopping: ChatGPT, Claude, Gemini, Perplexity. It answers the question and names stores; increasingly it completes the purchase too. Behind them, a long tail of smaller, unverified bots.
Share of choice: How often an assistant names a given store when shoppers ask where to buy. A count, out of a stated number of asks.
Verified (identified) agent: An agent that signs its requests so you can tell who’s knocking. The opposite is anonymous.
Bot wall: The defences — CAPTCHAs, challenges, fingerprinting — built to stop scrapers, which treat an unrecognised shopping agent exactly the same way.
Allowlist: Letting named, verified agents through your bot wall while everything anonymous still gets challenged.
Structured data: Machine-readable product facts (schema.org): price, variants, stock. What an agent can know without guessing.
Guest checkout: A way to buy without an account. An agent shopping for a first-time customer has no login.

Find out where you stand

The honest answer is a count. We ask ChatGPT, Claude, Gemini and Perplexity the questions your shoppers ask, from where your shoppers ask them, and count who gets named. Where an assistant tells a shopper something your own pages contradict, we print both.

Then, with your say-so, we send real AI shoppers through your store and watch where they stall.

See a sample result Get a panel