Botcard · All tokens

KimiBot

Kimi says KimiBot crawls content potentially used to train Kimi's foundation models. Disallowing KimiBot signals that the content should not be used for model training. The page says each listed crawler is configured independently, and it shows Crawl-delay in seconds. This check does not apply Crawl-delay. It matches the whole token, so a group named Kimi does not match KimiBot, and it still reports the RFC 9309 decision.

robots.txt token
KimiBot
Operator
Kimi
Kind
training
robots.txt
disallow_is_opt_out. The vendor says disallowing this token opts that use out.
HTTP user-agent
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; KimiBot/1.0; +https://www.kimi.com/policies/kimi-crawlers The page prints this full string. The robots.txt examples use User-agent: KimiBot, not the full string. The string cites kimi.com, which redirected to this page. A group named Kimi does not match KimiBot.
IP list
https://www.kimi.ai/policies/kimibot.json The page links this file. On 2026-10-18 the three Kimi IP URLs returned the same JSON file (creationTime 2026-05-18T10:04:07Z, four IPv4 prefixes). The page says an address in that file means the crawler is from Kimi, and that blocking those addresses can stop the crawler from reading robots.txt. Botcard does not copy the address list.
Source
Kimi Crawlers. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/kimibot

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows KimiBot on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: KimiBot\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["kimibot"]}}}'

That call returns fetched_target false. This row is disallow via group KimiBot, rule Disallow: /.