Kimi-User

Kimi-User fetches a page live when someone asks the AI platform about it. Most operators use a separate user agent for each job, so you can usually allow or block one without affecting the others.

Page fetches requested by AI platform users. A verified request establishes a page read, not a citation or a human visit.

Requests from Kimi-User carry this token in their user agent string. Match the token rather than a full string, which changes as Moonshot AI updates versions.

To block Kimi-User, add this to the robots.txt at the root of your site:

Blocking it stops the assistant reading your page when a user asks for it, so the answer is built from other sources. Operators can treat user-requested fetches differently from automatic crawling; check the operator's documentation for how it applies robots.txt.

To allow it explicitly, for example after a broader rule blocks other crawlers:

Check what your robots.txt allows for Kimi-User and the other AI crawlers in this directory.

Moonshot AI publishes the IP addresses Kimi-User uses. A request that claims to be Kimi-User from any other address is not genuine.

• www.kimi.ai/policies/kimi-user.json

SurfacedBy's AI traffic tracking recognizes Kimi-User in the user agent and checks each request against Moonshot AI's published addresses. Only requests that pass count as crawls; the rest are shown separately.

Details on this page come from Moonshot AI's own documentation: www.kimi.ai/policies/kimi-crawlers.

• KimiBotTraining
• Kimi-SearchBotSearch indexing