Cloudflare Radar’s Bots Directory now uses BotBase, and shows how each bot uses what it fetches

Cloudflare has rebuilt the public Bots Directory on Cloudflare Radar so it uses BotBase, the company’s catalogue of the bots and agents it tracks. The pages have a new design that matches the Radar homepage, and each bot page now has an Identity section.

Radar’s Bots Directory now uses BotBase with a new design. APIs now expose detailed bot metadata including access levels and content use.

— Cloudflare Changelog (@CFchangelog) November 10, 2026

A 9 November changelog says the Identity section shows a bot’s access level, content use, Web Bot Auth verification and user agents. Bot operators are also searchable from Radar’s site search.

New fields in the Radar API

The same update adds fields to the Radar API’s List bots and Get bot details endpoints.

Field	What Cloudflare says it means
accessLevel	DIRECT if the bot reaches websites under its own identity; INTERMEDIARY if it acts on behalf of another agent or a person
contentUse	full if fetched content is kept and reused, for example for model training or a search index; reference if it is cited or linked back to the source; immediate if it is used once to answer a user’s request
categories	A bot can have more than one category. Groups follow BotBase, add COMMERCE, and fold some older categories into broader groups
documentationUrl and operatorWebsiteUrl	Added on bot details only

The older category and operatorUrl fields are deprecated, in favour of categories and documentationUrl.

What stays in the dashboard

BotBase is also available in the Cloudflare dashboard for Enterprise Bot Management customers, where Cloudflare describes it as a visibility plane for tracked bots. The BotBase docs, last updated on 8 October, already said that every bot tracked in BotBase, along with select metadata, is available publicly in Radar’s Bots Directory. The 9 November change is the public directory switching onto BotBase, with the new Identity section and API fields.