For ecommerce
The shopper's agent has a card now.
Assistants already compare your products before anyone visits. Now they buy, through your own checkout, for the person they work for. Punchline shows which agents shop your store, proves which ones are real, and counts the carts and orders they bring, next to the people who shop the usual way.
What changed
Agents moved from the shortlist to the checkout
On November 13 2026 OpenAI launched ChatGPT Wallet, which lets its dots agents complete purchases for a shopper, who approves each one, with a payment token in place of the card (CNBC). It works through merchants' existing checkouts, and retailers may need to set their CDN or firewall to recognize the agent's signed requests (Digital Commerce 360). Visa, Mastercard and American Express build their agent programs on the same signatures (Cloudflare), and Google's Universal Commerce Protocol adds buying in AI Mode and Gemini for select merchants (Google).
Where agents buy
What reaches your store, and what Punchline shows
| How the agent buys | What reaches your site | What Punchline shows |
|---|---|---|
| ChatGPT's dots agents, paying with ChatGPT Wallet | Signed requests (Web Bot Auth) browsing product pages, the cart and your own checkout | A verified agent, request by request, with the shopper's country, language and device type as OpenAI relays them, and the order if your server reports it |
| Agents in a cloud browser or in the shopper's own browser | A browser on your product pages, cart and checkout | Labelled by its signature, published addresses or automation traces; in the shopper's browser, joined to the shopper's visit |
| Visa, Mastercard and American Express agent programs | Signed requests that say whether the agent is browsing or paying | Recognised, with whether the agent was browsing or paying. Checking each signature against the network's keys is built and switches on when the networks publish where their keys are; until then these visits aren't counted as verified |
| Google AI Mode and Gemini (Universal Commerce Protocol) | Either a checkout on your site, or no page request at all when checkout happens on Google | The visits and orders that reach your site. Purchases completed on Google's own pages never reach it, and we don't pretend otherwise |
Don't block the buyer
Know which agents are real before your firewall decides.
Bot protection was built to stop scrapers, and an agent with a card looks like one. OpenAI warns that existing security and fraud systems can interfere with agent-led purchases (Digital Commerce 360).
Punchline checks each agent's signature or published address, calls out impostors borrowing a real agent's name, and shows which agents reached your product pages and which got an error, a redirect or an empty page. Then you allow the real ones with evidence, not a guess. Known agents
ChatGPT agent (signed) · /products/trail-runner, /cart, /checkout
Order placed for its shopper · reported by your server
why: signature verified · purchase tied to the agent's visit
Carts and orders
Count what agents bought, apart from what people bought
Send purchases from your server with the visitor's address and user agent, and each order joins the visit it came from, so "orders placed by agents" never inflates "orders placed by people". Events and goals
When an agent builds a cart but leaves the paying to its person, give it a handoff link to the cart. When the shopper opens it and buys, the order is connected to the agent that built the cart, with its value. Handoff links
Questions you can answer
Your store's agent report
| Question | Where to look |
|---|---|
| Which agents shop my store, and which products do they read? | Agents by operator, and top pages by visitor type |
| Did they get the price and stock, or an empty page? | Agent content: errors, redirects and near-empty pages, per product page |
| How many orders did agents place, and for how much? | Events: purchases by visitor type, with values |
| Which carts did agents build that shoppers finished? | Handoffs: links given, opened and converted, by agent |
| How many shoppers did assistants send me? | The AI channel: people who clicked through from ChatGPT, Perplexity, Claude, Gemini or Copilot |
| Who is scraping my prices under a famous name? | Impostors: a known agent's name from the wrong address |
Product pages agents can read
Make sure the agent sees the price
A product page that builds its price and stock in JavaScript can arrive empty to an assistant that doesn't run it. The edge install can serve agents a markdown version of the same page, made from your own HTML, and the free audit shows a page the way an assistant gets it. Serve agents markdown · Free audit
Install
Works with your store
| Platform | Install |
|---|---|
| Shopify | Cloudflare Worker for agents, the snippet in your theme, and an order webhook that counts purchases by people and by agents, no app needed |
| WooCommerce | WordPress plugin: upload a zip. Counts paid orders by people and by agents, with no API key |
| Shopify Hydrogen | One wrapper in server.ts |
| Headless on Next.js | A three-line proxy file |
| Anything on Vercel | Vercel log drain: no code |
| Anything behind Cloudflare | Cloudflare Worker |
| Your own checkout on Stripe | Stripe Checkout: a webhook, and one line where you create the session. Purchases by people and by agents |