Is your shop agent-ready? · Article 2 · 2026
Agents buy through the front door
In article 1 of this series, ChatGPT put a cordless drill kit into a cart at Alternate at our request and handed back to us before payment. The agent used the same pages your customers see. This article looks at what reaches the retailer, why this route is the normal case today and what changes once agents identify themselves. It ends with a first step you can take with your own data.
What reaches the retailer
For the purchase, ChatGPT opened its own browser in the cloud. One minute and twenty seconds later the kit was in the cart (own measurement, 2 November 2026). From the shop's side, this was an ordinary visit: a browser searches for a product, opens the product page, picks a variant, puts it in the cart and opens the checkout. Then the visit ends. Address and payment method are missing, and no customer account was used. If the human completes the purchase, the retailer sees an order like any other. If not, its figures show an abandoned cart.
ChatGPT had recommended the kit at "125 to 130 euros including shipping", based on retailer prices from September. The cart then showed the price from Alternate's own checkout: 127.89 euros including shipping. So the price was right in the end. The choice of retailer, however, had been made earlier, on the old price.
Whether Alternate could recognise the agent depends on a setting. OpenAI lists its cloud browser in Cloudflare's directory as "ChatGPT agent", with public keys for signatures (own query, 2 November 2026). If the shop's CDN, the service that delivers its pages, checks that signature, it can attribute the visit to OpenAI as the operator. Without that check, the shop sees a browser. We do not know whether our visit was signed or what Alternate checks. Agents running in the user's own browser, such as Perplexity's Comet or Claude in Chrome, always look like the user.
What the retailer is missing
Even if the shop recognises the operator, it does not know the customer behind the agent. That leaves four gaps.
No identity. The agent came without a customer account. The shop cannot tell a regular customer from a business customer or a first-time visitor.
No customer price. The agent sees the price every guest sees. A framework agreement, a volume discount or a members' price stays hidden from it. In B2B, customer prices sit behind the login, and an agent without an account sees only the list price there.
No stock per location. If your shop only shows stock per branch or warehouse after a store has been selected or after login, that information never reaches the agent. A customer who wants to collect today needs exactly that.
No follow-up question. The agent chose the variant with two batteries. Nobody asked whether the customer needs two batteries. In a shop, a sales assistant would have asked. Through the user interface, the retailer cannot give the agent a question to pass on.
Why this is the normal case
Our test is a single case. Data from two security vendors suggests it is typical. In April 2026, HUMAN Security counted around 71 per cent of the observed activity of the ten largest agents as running through browser agents, mainly Perplexity's Comet and OpenAI's Atlas. At Forter, the share of browser agents in agent orders rose from 1 per cent at the end of July to 70 per cent in mid-October 2026, mostly in the US. Both are vendor studies. The volume is still small: agent purchases worldwide account for a fraction of one per cent of transactions (Accertify, 9 October 2026, also a vendor figure). There is no measurement for Germany.
The direct routes exist, but hardly for retailers with their own platform in Germany, Austria and Switzerland:
- The Universal Commerce Protocol (UCP) from Google and Shopify describes catalogue, questions and checkout as an interface. More than 19,000 shops serve a UCP profile, 58 per cent of them on Shopify and around 35 per cent on Wix (UCPChecker, 30 October 2026). In the DACH region, on 2 November, we found exactly one shop with its own platform serving such a profile.
- Google offers purchases via UCP in the US, Canada and Australia (as of 2 November 2026).
- OpenAI scaled back Instant Checkout in ChatGPT, built on the Agentic Commerce Protocol (ACP) from OpenAI and Stripe, in March 2026. OpenAI cited a lack of "flexibility" for merchants.
As long as there is no direct route, the agent uses the shop's pages. The next step uses them too: OpenAI's browser agent Dots buys with the card stored in the customer's account at the retailer, and only with the user's approval. The Pro version is not available in the EEA, Switzerland or the UK. For Europe, The Decoder reported "in a few weeks" on 28 October 2026. Where the customer has an account with a stored card, the handover before payment then falls away.
What changes once agents identify themselves
Today a login answers several questions at once: who is asking, for which customer account, and whether payment is allowed. For agents, three separate mechanisms answer these questions.
Who operates the agent? Web Bot Auth. The agent signs every request with its operator's key, and the shop or its CDN checks the signature. At the IETF, the body that sets internet standards, the mechanism is still a draft (as of 29 October 2026). Cloudflare, Akamai, HUMAN and DataDome already check it. In Cloudflare's directory, 178 of 244 entries for AI services and agents have a signature directory (own count, 2 November 2026). ChatGPT agent signs, and Google's agent does so in part. Meta's Muse, Perplexity and Anthropic's Claude-User do not sign. From 5 October to 2 November 2026, ChatGPT agent alone made 75.8 per cent of the requests that Cloudflare classifies as coming from AI assistants (own query via Cloudflare Radar). A shop that checks signatures can thus attribute most of these requests to an operator, and the rest only by behaviour.
The signature proves the operator. It says nothing about the customer. It governs access and quota. At Shopify, signed agents get a higher quota than anonymous ones and may prepare a cart and checkout. Shopify only recognises the customer through a token bound to that customer's account.
For which customer? Account linking. The customer links their account to their assistant once. After that, the agent asks with a token issued for this customer and this shop. The shop reads the customer from the token and calculates the price in its own system. Nobody has to publish a price list. The standard is OAuth 2.1, set out for agents in the authorisation specification of the Model Context Protocol (28 July 2026) and in UCP Identity Linking (version of 25 August 2026). ChatGPT, Claude, Gemini and Copilot support the flow. That closes the gaps on identity and customer price, and the shop can also show stock per warehouse for this customer. Article 10 covers this in more detail.
May it pay? The card networks. Visa launched its Trusted Agent Protocol in Europe on 2 July 2026 with more than 30 issuing banks. On 2 June 2026, Mastercard enabled all issuing banks in Europe for Agent Pay. Retailers need a connection through their payment service provider and their CDN.
The checkout as an interface. With UCP or ACP, the agent sends the cart as a data record, and the checkout's answer with price and shipping is binding. At one shop on Shopify, a single endpoint covered everything from catalogue search and questions to the merchant through to checkout and order status (own measurement, 2 November 2026). For questions to the merchant, the UCP draft has had a capability called ask since 7 October 2026, not yet in any released version. A follow-up question to the customer can go back through an interface as a data field, and the assistant shows it to the human. Article 9 covers this.
The first step is visibility
For retailers with their own platform in the DACH region, agents come through the front door today, and some already identify themselves. The work therefore starts with today's visitors and three questions:
- Who comes? Which agents call up your shop, how often and which pages. That includes search and training crawlers as well as cloud browsers that fill carts.
- With which credential? Whether the agent signs with Web Bot Auth, only names itself in the user agent, the browser's self-description, or arrives with no identifier at all. And whether your CDN checks the signature.
- What does it get? The product page with its price, a security challenge or a block. And whether that matches what you want for this operator.
Most of the answers are already in your server logs and your CDN settings. Agents in the user's own browser appear there as the user; that gap remains. The answers become a rule per operator: who gets what, and how much of it (article 6). What an agent finds on your product pages once it gets through is the subject of article 5.
What we make of it
In an Agent Channel, a cockpit shows this view continuously: requests per operator and level, and the rule that applies to each.
Sources
- Own measurement, 2 November 2026: purchase request to ChatGPT (chatgpt.com, paid account), cloud browser, cart at alternate.de, duration 1 minute 20 seconds; screenshot on file. Details in article 1. Quotes translated from German.
- HUMAN Security, State of Agentic Traffic (April 2026). Vendor study.
- Forter, network data on agent orders (13 October 2026, mostly US). Vendor study.
- Accertify, share of agent purchases in transactions (9 October 2026). Vendor figure.
- Cloudflare Radar and Cloudflare's directory of verified bots and signed agents, own API query on 2 November 2026 (requests from 5 October to 2 November 2026).
- IETF, draft-ietf-webbotauth-httpsig-protocol-01 (29 October 2026).
- Shopify, documentation on agent tiers and rate limits (shopify.dev, retrieved 3 November 2026).
- Model Context Protocol, Authorization (specification 2026-07-28); Universal Commerce Protocol, Identity Linking (version 2026-08-25); documentation from OpenAI, Anthropic, Google and Microsoft on account linking, retrieved 3 November 2026.
- Visa, launch of the Trusted Agent Protocol in Europe (2 July 2026, trade press); Mastercard, announcement on Agent Pay in Europe (2 June 2026).
- UCPChecker, number of shops with a UCP profile (30 October 2026); our own retrievals of
/.well-known/ucpat DACH retailers and at one shop on Shopify, 2 November 2026. - Universal Commerce Protocol, ask capability, in the draft since 7 October 2026 (GitHub, pull request 538).
- OpenAI, help article on Instant Checkout (as of 2 November 2026); Google, purchases via UCP in the US, Canada and Australia (as of 2 November 2026).
- The Decoder, 28 October 2026, on Dots in Europe.
We have no ties to the brands, retailers or comparison sites mentioned. We chose the products, the assistants picked the brands and retailers in their answers.
What does an agent see on your product pages?
We look at it together with you, on your own pages.