Kimi-UserKimi says Kimi-User handles actions a person starts in Kimi, such as summarizing one article or answering a question that needs live web retrieval. It is not an automatic bulk crawl. Kimi says robots.txt rules may not directly apply, and that disallowing this token may reduce the site's visibility in user-directed web searches. The page shows Crawl-delay in seconds. This check does not apply Crawl-delay. It matches the whole token, so a group named Kimi or KimiBot does not match Kimi-User, and it still reports the RFC 9309 decision.
user_fetchmay_not_apply. The vendor says robots.txt may not apply, because a person triggered the fetch.Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; Kimi-User/1.0; +https://www.kimi.com/policies/kimi-crawlers The page prints this full string. The robots.txt token is Kimi-User. The string cites kimi.com, which redirected to this page. A group named Kimi does not match. A group named KimiBot does not match.curl -s https://whosthatbot.com/v1/crawlers/kimi-user
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Kimi-User 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: Kimi-User\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["kimi-user"]}}}'
That call returns fetched_target false. This row is disallow via group Kimi-User, rule Disallow: /.