Crawlers

Kimi: user agent, robots.txt, and verification

Kimi has three documented request identities. KimiBot collects potential training material, Kimi-SearchBot builds the search index, and Kimi-User handles user-directed retrieval. Kimi is a product name, not a single crawler token.

User agent and purpose

Documented purpose: Training, search, and user retrieval.

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; KimiBot/1.0; +https://www.kimi.com/policies/kimi-crawlers

Kimi’s official crawler policy documents the example above and separate examples containing Kimi-User/1.0 and Kimi-SearchBot/1.0.

Robots.txt control

User-agent: KimiBot
Disallow: /

This example restricts the training bot only. Kimi documents separate robots controls for its search bot and support for Crawl-delay. It warns that robots rules may not directly apply to user-triggered Kimi-User requests. Publish preferences on each relevant subdomain.

Review this example in the context of your existing groups and paths. Publish it at the origin’s /robots.txt and check the actual response. A policy change can take time to be read; it does not erase earlier copies of content.

Verify origin before trusting the name

Use the bot-specific IP links from the official policy: kimibot.json, kimi-searchbot.json, and kimi-user.json. Overlapping lists establish operator network origin, not which product function caused a request. No official rDNS method is asserted here.

A User-Agent is self-reported and can be spoofed. A matching header is a claimed identity, not an authenticated bot. Use the operator’s current IP or DNS procedure for origin confidence; those checks are not cryptographic request signatures and do not authorize access to private data.

What AnalyticFast detects today

AnalyticFast does not currently classify Kimi in its named crawler aggregate. This directory entry is research, not a claim of detection support. AnalyticFast does not authenticate bot identities or perform the IP/rDNS checks described here.

A useful next check

Write three separate decisions: training permission, search discovery, and live user retrieval. Do not block a made-up User-agent: Kimi group and assume it covers all three. Validate each documented token against the latest policy.

Official sources and review date

• Official Kimi tokens, usage, robots rules, and IP list links

Last checked 2026-10-31. Verify the latest policy and network data before changing production access rules.

Back to the crawler directory.