AI shopping agents and WooCommerce: let the real ones in, keep the fakes out

A guide for store owners. Updated October 17, 2026. The standards here are still drafts and change often; the links at the end have the latest.

People have started sending AI assistants to shop for them: find a product, compare prices, fill in the checkout. To your store, that assistant looks a lot like a bot. It browses fast, it runs in a cloud data center, and it doesn't move a mouse. Bot defenses built to stop scripts can turn it away, and that's a lost sale.

It works the other way too. As soon as stores wave AI agents through, bad bots start pretending to be one. So the question isn't "should I let AI agents in?" It's "how do I know this one is real?"

Why the usual ways don't work

• The user agent. Every request says what software sent it, but that's just text. A card-testing script can say it's ChatGPT as easily as anything else.
• Lists of addresses. Agents run on big cloud networks shared with everyone else, including bot operators, and the addresses change.
• A CAPTCHA. It stops the agent you wanted, and the bots you didn't want increasingly solve them.

The answer: a signature on every request

Web Bot Auth gives an agent a cryptographic ID card. The company running the agent, such as OpenAI for ChatGPT's agent, keeps a private key and publishes the matching public key on its own website, at /.well-known/http-message-signatures-directory. The agent signs each request it sends using the HTTP Message Signatures standard (RFC 9421), with three extra headers:

• Signature-Agent: who's sending it, as a web address, like "https://chatgpt.com".
• Signature-Input: which parts of the request are signed, when the signature was made and when it expires, and which key signed it.
• Signature: the signature itself.

Your site fetches the operator's public keys and checks the signature. A bot can copy the headers, but it can't make a valid signature without the operator's private key, so a fake falls apart the moment it's checked. And because each signature says when it expires, a copied one soon stops working.

Where the standard is

Cloudflare started Web Bot Auth, and the IETF has a working group for it: on September 1, 2026 it adopted the protocol as a working-group draft (HTTP Message Signatures for automated traffic). It's still a draft, not a finished standard, so details can change. It's already in use: OpenAI signs its agent's requests this way, and Cloudflare and Akamai both recognise signed agents.

Payments are building on it too. Visa's Trusted Agent Protocol and Mastercard's Agent Pay both use Web Bot Auth to identify agents, with their own markers for "browsing" and "paying" and their own key directories, and American Express has said it will use it as well.

What a store should do now

1. Decide which agents you want. Most stores want shopping agents. Some don't want AI crawlers copying their product pages; those are a separate question, and a signature tells you which is which.
2. Check what your firewall does with them. If your site is behind Cloudflare or Akamai, look at their bot settings: both can tell signed agents apart, so a verified shopping agent doesn't have to be blocked along with the bots. Our free AI agent check shows what your store does with an agent that can't prove who it is.
3. Never trust the user agent alone. A request that says "ChatGPT" without a valid signature is a bot like any other. Treat it that way, above all at checkout.
4. Make your shop easy to read. Agents read pages like a careful customer: clear product names, prices, stock, sizes, shipping costs and return rules in plain text. WooCommerce adds product details for machines to product pages by itself; keep it that way, and don't hide prices behind a login.
5. Keep your payment checks on. A verified agent proves which company runs the agent, not whose card it's using. Your payment provider's fraud checks still matter.

How Ropeline Pro handles AI shoppers

Ropeline Pro has a setting called Let verified AI agents (like ChatGPT agent) shop without limits, on from the start:

• It checks each signed request's Web Bot Auth signature against the operator's published keys, which it keeps for an hour. The signature has to be fresh and has to cover the Signature-Agent header, so it can't be lifted onto a different claim.
• It trusts chatgpt.com out of the box; a developer can add other operators with the ropeline_trusted_agents filter.
• A verified agent skips the limits that stop bots: checkout tries, attack mode, the network list, the signup limit and the form limit. Each visit to checkout shows up in your activity log, and the weekly report counts them.
• A verified agent whose payments keep failing still gets paused, like anyone else.
• A request that claims to come from a trusted operator but whose signature doesn't check out is a bot in disguise: its checkout is refused, and the activity log says why. (In the first-week learning mode, Ropeline only records it.)

Ropeline checks Web Bot Auth's own signatures. It doesn't yet check Visa's or Mastercard's versions, which use their own markers and key directories.

Questions

Can I see AI agents visiting my store?

Not in WooCommerce on its own. With Ropeline Pro, verified agents show up in the activity log when they load pages and when they reach checkout, with the operator that signed them. So do bots pretending to be a trusted agent, with what gave them away.

What about agents that don't sign their requests?

They're treated like any other visitor. Most get through, because Ropeline only stops what looks like a bot: too many tries, failed payments, forms filled in faster than anyone can type. A signature just means a real agent doesn't have to worry about those limits.

Is this the same as robots.txt?

No. robots.txt asks crawlers politely which pages to skip, and anyone can ignore it. A signature proves who's asking. They work together: robots.txt for what you'd like, signatures to know who to believe.

Further reading: the IETF's Web Bot Auth working group (datatracker.ietf.org/wg/webbotauth), Cloudflare's posts on Web Bot Auth and on agentic commerce with Visa and Mastercard, and OpenAI's help article on allowing ChatGPT's agent.