Brief
Cloudflare gives bot operators a dashboard home with submission tracking, editing and a behavior model
Cloudflare's BotBase for Operators now lets bot and agent operators manage directory submissions from a dashboard. The source gives no pricing, region or date detail, so this brief covers only the capabilities it names.
Cloudflare says BotBase for Operators gives bot operators a home in its dashboard for managing submissions to its directory of bots and agents. Three things are named as added or present: submission status tracking, submission editing, and a behavior model.
The behavior model is the detail worth noting if you run an agent or crawler. It is described as a way for operators to declare accurately how their bots use content, rather than leaving that to inference on the platform side.
Status tracking and editing change the workflow around a submission: you can see where it stands and correct it, instead of treating the listing as a one-way form. The evidence stops there. Nothing here covers cost, limits, regions or review criteria.
Our reading
For anyone shipping a crawler or agent, the directory listing is a distribution problem, and a status view plus an editable submission turns that from a black box into something with a feedback loop. The behavior model matters more than the UI: declared content use is the kind of information platforms otherwise infer, and declarations are usually what policies get enforced against. Teams that run…
What to do or watch
Check whether your bot's declared content behavior matches what it actually does before submitting, and watch whether Cloudflare says anything about how declarations are reviewed or enforced; the evidence does not yet cover that.
Source details and supporting facts
Each line is stated by the page named above it.
Stated by blog.cloudflare.com
- Bot operators now have a home in the Cloudflare dashboard to manage submissions.
- The update adds submission status tracking, submission editing, and a behavior model so operators can accurately declare how their bots use content.
Sources
- Cloudflare blogText stored 16 September 2026
How this story was checked. Written from the 1 page listed above, stored 16 September 2026; claims checked against that stored text on 16 September 2026.
What that means
- 2 of 2 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.