Cloudflare gives agent traffic its own identity: sites can see the user behind an agent and block just one account
Synopsis
Cloudflare puts the identity problem that personal AI agents create for websites on the table: a remotely hosted agent acts for a user, yet the site sees only the agent and struggles to recognize, serve and hold accountable the user behind it. It proposes identity, reputation and accountability as the three mechanisms that preserve the site-user relationship, and has shipped three capabilities: listing personal assistants as a separate traffic category, setting access per agent, and showing at login and sign-up which agent made the request.
Interpretation
Websites are starting to treat remotely hosted personal AI agents as an intermediary layer that needs its own identification, rather than as ordinary visitors. Previously a site could simply block intermediary traffic and require users to disable the intermediary service; once agentic traffic dominates, that stops working and the site is left deciding whether to trust the intermediary without direct information about the user. In Security Analytics, available to Cloudflare customers, personal assistants are broken out as their own traffic category, and a widget lists every agent visiting a site, its request count, the paths it hits and the errors it runs into.
The approach re-links an agent to the user it acts for, so a site can act on a specific account without penalizing other users behind the same agent. This capability rests on the early-access Account Abuse Protection, where every login and sign-up shows whether a personal agent made the request and which one. When an attacker abuses a shared agent against one account, the site can mitigate that account with a WAF rule on its Hashed User ID instead of blocking the agent for every other legitimate user behind it.
Perspective
The discussion covers remotely hosted agents, not agents on the user's own device; local agents or agents running in the user's own browser are explicitly out of scope for the main topic. The shipped capabilities are for Cloudflare customers, and Account Abuse Protection is in early access.
The material frames agent-traffic growth as a trend judgment, saying it may eclipse traditional human browsing in the near future, without a quantitative forecast. The proposed protocols and coalition are still in discussion and standards development, and the material does not state when they will land.