Skip to content

Botcard

Checks a pasted robots.txt against AI crawler user-agent tokens under RFC 9309 and reports allow or disallow for each.
Botcard: data, price, alternatives
At a glancechecked Oct 19, 2026

not read yet

Use

For
Site owners and agents deciding which AI crawlers their robots.txt should allow or block
How it runs
API
Used for
  • check whether a robots.txt file allows a given AI crawler
  • generate a robots.txt that blocks training crawlers
  • look up the vendor stance for a crawler token
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 28, 2026
  • MCP servercom.whosthatbot/botcardverified in the MCP registry
  • Stateanswers, 4 toolschecked 2026-10-28
  • Address to connectwhosthatbot.com/mcp
  • OpenAPI spec6 pathsthe spec ↗
  • MCP docswhosthatbot.com/mcpthe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Databy use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Botcard with

Pick up to two.

All 10 alternatives to Botcard →

All Data tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Botcard for?

Sign in to leave a note
Questions this page answers
  • What is Botcard?

    Checks a pasted robots.txt against AI crawler user-agent tokens under RFC 9309 and reports allow or disallow for each. It is listed in the Atlas under Data.

  • Who is Botcard for?

    Site owners and agents deciding which AI crawlers their robots.txt should allow or block

  • What are alternatives to Botcard?

    In Data, by use: Salience, VisibilityKit, IndexDecode, TrafficBud, AI search visibility.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk