How to tell verified agents from unknown bots

In short

Decide whether agents that prove who operates them are treated differently from automation that only claims a name, and ask your CDN or bot vendor to do it. A name in a request can be copied by anyone. Signatures and registration let you welcome a customer's agent without opening the door to every script.

The decision

Decide whether you will treat agents that prove who operates them differently from automation that only claims a name, and ask your CDN or bot vendor to do it.

Who decides: Security, with the head of ecommerce or digital.

The options

  1. Verify by signature and treat verified agents as customersOperators including OpenAI, Google and AWS sign their agents' requests; your CDN can check the signature. Cloudflare: The Internet has a second audience (30 Sep 2026), read 4 Nov 2026.
  2. Require registration, as Zocdoc doesYou know who each agent is and can set rules per agent; fewer agents will bother. Zocdoc for Agents (markdown), read 4 Nov 2026.
  3. Treat all automation the sameSimple, but a real customer's agent is blocked along with scrapers. Cloudflare: the agentic internet, WebMCP example (6 Aug 2026), read 4 Nov 2026.

What we found

How to decide

  • Ask your bot vendor whether it checks signed requests and a verified-bot list today.
  • Decide what a verified agent may do: read, add to basket, check out. Treat each as its own permission.
  • If you run a network or a marketplace, consider registration, which gives you a named human contact for each agent.

Where this shows up

  • Self-check question 16Can your team tell verified bots and agents (for example through Web Bot Auth signatures or a verified bot directory) apart from unknown automation?
  • The healthcare guideAppointment booking through Zocdoc, Gemini and Amazon Health AI, with patient consent rules.
  • The financial services guideComparison and quote apps inside ChatGPT that hand off to the firm's own site.
  • The publishing guideSeparate controls for training, search and live fetches, and what Cloudflare changed in 2026.

Sources

  1. Cloudflare: The Internet has a second audience (30 Sep 2026) (blog.cloudflare.com/agentic-web), read 4 Nov 2026.
  2. Zocdoc for Agents (markdown) (zocdoc.com/business/welcome-agents.md), read 4 Nov 2026.
  3. Cloudflare: the agentic internet, WebMCP example (6 Aug 2026) (blog.cloudflare.com/the-agentic-internet), read 4 Nov 2026.
  4. Retail Gazette: Amazon blocks Meta's Muse (22 Sep 2026) (retailgazette.co.uk/blog/2026/09/amazon-blocks-metas-new-ai-shopping-agent-from-its-website), read 4 Nov 2026. Reported by trade press.
  5. IETF draft: Web Bot Auth architecture (datatracker.ietf.org/doc/draft-meunier-web-bot-auth-architecture), read 4 Nov 2026.

Last reviewed