SYSTEM Cited by 3 sources

Cloudflare BotBase

BotBase is Cloudflare's searchable database of all tracked bots and agents, launched as a feature of Enterprise Bot Management in July 2026. It provides a comprehensive directory view of the entire Cloudflare bots catalog with per-bot behavioral classification, content-use levels, and verification status.

Architecture

BotBase represents each bot as an entity annotated with:

• One or more behaviors from the 10-category taxonomy: Search, Agent, Training, Transact, Data Collection, Security Testing, SEO, Ads Verification, Social/Link Preview, Feed Fetching, Monitoring & Operations.
• Content-use level: immediate, reference, or full — describing what the bot retains and reshares.
• Verified status: whether the operator has demonstrated honest self-representation and non-abusive behavior.
• Detection ID: a copyable identifier for use in customer Security rules.

Key Properties

• Dynamic dashboard view — first time Cloudflare exposes the full bot directory live on the dashboard.
• Customers can filter by specific bot, copy detection IDs for WAF rules.
• Classification feeds into the new default enforcement logic: if a customer blocks "Training," all bots classified with Training behavior are blocked.
• Bots that reproduce content in full cannot achieve Verified status.
• Future expansion planned as a direct control center for managing automated traffic per-site.

Relationship to Bot Management

BotBase is the data plane for bot identity and classification; systems/cloudflare-bot-management is the enforcement plane that acts on the classifications. The new three-toggle AI traffic controls (Search/Agent/Training) query BotBase's behavioral classification to determine allow/block decisions.

Seen In

• sources/2026-07-01-cloudflare-ai-traffic-options — introduction and design rationale
• sources/2026-08-07-cloudflare-unveiling-good-and-bad-behaviors-on-the-agentic-internet — reframes BotBase as a directory of all known bots and agents, not just known-good ones (unlike the older Bots Directory). Because Cloudflare tracks and validates behavior for known-good actors, it can detect when those expectations aren't met — an actor that "abuses the trust it has earned" is demoted to unverified. Situates BotBase within the Risk vs Trust ecosystem as the reputation/ identity substrate.
• sources/2026-09-29-cloudflare-adaptive-application-security-for-the-ai-era-how-cloudflare — the "govern access and agent behavior" stage: Botbase is the verified identity layer across all agentic traffic, and Cloudflare is "making registration more accessible to smaller and custom agents" so identity extends beyond the major platforms. Registration lets legitimate bots/agents declare who they are while owners retain control over whether/how they access; the trust half is kept separate from per-interaction risk.