BotBase for Operators: A clearer path to joining Cloudflare's directory of bots and agents

Summary

Cloudflare launched BotBase for Operators to give bot operators a clearer way to submit, monitor, update, and cancel bot-directory submissions from the dashboard. The new area includes a bots directory, submission form, and history tab with Waiting for review, Accepted, and Rejected statuses, including rejection reasons and classification changes. Its intake model records what a bot does, how it uses content, and whether it is direct or intermediary, while allowing multiple behaviors and Content Signals declarations. Reviews now use automated checks for duplicates, user-agent specificity, and verification through IP lists, reverse DNS, or Web Bot Auth, routing exceptions to staff. The launch focuses on visibility, with ownership, observability, and conversation identified as future goals.

Takeaways

1. 1

   Submission history provides status and details for bots submitted from an account, including actionable rejection reasons and explanations of classification changes.

2. 2

   The intake form captures three dimensions: the bot’s behaviors, its content-use requirements through the Content Signals model, and whether it is operated directly or as an intermediary.

3. 3

   Automated review checks duplicates, user-agent specificity, and claimed verification methods; submissions that need closer examination are routed to Cloudflare staff with a flagged reason.