Agents aren’t humans (but they kinda are)
- ID
- 43456
- Status
- summarized
- Published
- 06 Nov 2026, 1:03 AM
- Fetched
- 06 Nov 2026, 2:13 AM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/trusted-agent-delegation/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 6.5
- Created
- 06 Nov 2026, 2:14 AM
- Tags
- Audience
- developersai_agent_userssaas_founders
What happened
Cloudflare's Bryan Becker argues that personal AI agents — automations a User instructs to drive a cloud browser or computer, hosted by an Operator — are a new kind of intermediary, like proxies and cloud browsers, except the Site sees the agent instead of the User. He names Meta's Muse and OpenAI's dots as examples, notes local agents like OpenClaw are out of scope, and says Sites historically could just block intermediary traffic, which stops working once agentic traffic becomes the majority. The proposed fix is the classic fraud-prevention triad — identity, reputation, accountability — so a Site can answer whether the actor is truthful about who it is, whether it is trustworthy, and who answers for the action.
Why it matters
If your product prices per seat, rate-limits per IP or session, or attributes usage to a single visitor, this post describes the failure mode directly: one agent can look like one visitor carrying many Users, so you eat the cost when it goes wrong. Decide now whether you'll require a delegation signal (who the Operator is, on whose behalf it acts) instead of defaulting to blocking, and instrument agent traffic before it becomes a meaningful share of your requests.
Discussion angle
What is the minimum viable delegation token you'd accept on your own product — and which of your current controls (per-seat pricing, IP rate limits, signup CAPTCHAs) breaks first if one Operator fronts a hundred Users?