APOSTL
User-requested fetch

Kimi-User

Retrieves pages in response to Kimi user actions.

Operated by Moonshot AI
See your agent traffic
PurposeUser-requested fetch
HTTP identifierKimi-User
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

A fetch may follow a request to read or summarize a specific page.

Requested URLs
Response codes
Redirect chains

Your next move

Check the requested document and the response returned during the user’s task.

The technical details

Markdown
How to identify it

Look for the Kimi-User identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Match the source IP against the current Kimi-published list for this specific crawler, linked from its crawler policy.

Access and robots.txt

Kimi states that robots.txt may not directly apply to user-triggered actions. Do not assume the training crawler’s policy applies to Kimi-User.

Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See Kimi-User in context

See their requests. Find the pages that matter.

See your agent traffic

KEEP EXPLORING

Different bots, different intent

Moonshot AI

KimiBot

Collects content that may train Kimi foundation models.

AI training

OpenAI

ChatGPT-User

Fetches pages for user actions in ChatGPT and custom GPTs.

User-requested fetch