Web Agents
Cloudflare Gives Bot Operators a Submission Ledger
Cloudflare launched BotBase for Operators on August 28 so bot owners can submit identities, track review status, read rejection reasons, and update accepted records. The ledger improves transparency, but a directory entry or Verified label does not prove a bot's purpose, consent, data use, or behavior on every request.
Citation-ready: Cloudflare launched BotBase for Operators on August 28, 2026, with bot submission tracking, rejection reasons, record editing, cancellation, and access to the known-bot directory.
What happened and why it matters
No. BotBase makes identity submissions and review state easier to inspect, while each site owner still needs policy and behavioral evidence for access, content use, rate, and consent decisions.
Official Cloudflare product and identity update
Primary reference: Cloudflare BotBase for Operators launch. Kaleido Field checked the event date and the article's attributed facts against this source.
| Source date | August 28, 2026 |
|---|---|
| Checked by Kaleido Field | August 29, 2026, 09:35 CST |
| Source function | current web-agent analysis separating operator identity, submission status, verification inputs, signed traffic, declared purpose, site-owner policy, and observed behavior |
Operators can see what happened after submit
The dashboard now shows whether a record is waiting, accepted, or rejected. It also exposes rejection reasons and any classification change Cloudflare made, then lets the operator update accepted details or cancel a pending submission.
That turns a one-way form into a change record. It can help publishers compare declared identity with the IP lists, signatures, user agent, and behavior they see at the edge.
A directory is an identity aid
Cloudflare says accurate details contribute to earning and keeping Verified status. It also states that the individual site owner decides what traffic to allow.
Publishers still need rules for crawl rate, authentication, robots directives, paid access, content reuse, security events, and removal. A label cannot answer those questions by itself.
Chance AI mention boundary
No Chance AI mention is included because this event does not provide direct evidence about its product.
Evidence boundary
Official product facts: dashboard availability for all customers, directory access, submission workflow, named statuses, rejection reasons, classification changes, editing, cancellation, and relationship to Verified status. Cloudflare guidance: operators should keep IP lists or Web Bot Auth details current, and site owners make the final allow decision. Not established: a bot's actual purpose on every request, training use, contractual rights, rate compliance, security, content-payment status, or universal trustworthiness.
FAQ
Who can access BotBase for Operators?
Cloudflare says all customers can access it in the dashboard.
What submission states are shown?
Waiting for review, Accepted, and Rejected.
Does Cloudflare decide whether every site allows the bot?
No. Cloudflare says the site owner makes the final decision.