Kimi-User
Kimi-User is blocked by 253 sites in the October 2026 survey, or 4.1% of readable files. The community reference lists its operator as Moonshot AI that fetches web content on behalf of users interacting with Kimi.
Who runs Kimi-User?
| Fact | Kimi-User reference entry |
|---|---|
| Operator | “Moonshot AI that fetches web content on behalf of users interacting with Kimi” |
| Purpose | “AI Assistants” |
| Does Kimi-User obey robots.txt? | “Unclear at this time.” |
| Frequency | “Unclear at this time.” |
| Cloudflare managed list for Kimi-User | No |
These facts quote the stored community ai.robots.txt reference.
“Kimi-User is a web crawler operated by Moonshot AI that fetches web content on behalf of users interacting with Kimi. When a user asks Kimi to summarize an article or ans…”
The stated role here is an AI assistant. An owner may allow a search crawler to list a page or an assistant to retrieve it for someone, yet decline to supply the text for training.
How many sites block it?
The 253 files blocking the whole site account for 4.1% of 6,171 readable robots.txt files. We found its name in 30 User-agent lists, a 0.5% share. Without a whole-site Disallow: / block, 5,918 files remain.
Among 552 readable files from the top 1,000 sites, we found 4 files naming it, a 0.7% share, with 44 files blocking the whole site. Blocking is more common among the leading sites, at 8.0%. Outside this group, 5,619 files contribute 209 blocks, or 3.7%.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| Kimi-User, all ranks | 30 | 0.5% | 253 | 4.1% |
| Kimi-User, top 1,000 | 4 | 0.7% | 44 | 8.0% |
| Kimi-User, remaining ranks | 26 | 0.5% | 209 | 3.7% |
A general User-agent: * ban contributes to this total whenever it applies to this crawler. Of 253 blocks, 227 come only from that general rule, without naming this crawler. Looking just at named files gives 26 blocks and 4 without a whole-site block. For 6,141 readable files, we found no mention by name. We ignore capitalization and repeated names.
Has that changed since August?
Between August and October, 15 sites that had blocked it stopped and 21 started, so 6 more of the same 5,889 sites block it. A further 201 blocked it in both months, and 5,652 did so in neither. Keeping the sites the same lets us count changes in their rules.
August’s full sample had 231 blocks among 6,236 readable files. October’s was 253 among 6,171. Those monthly totals also reflect which files we could read on each visit.
| August to October | Files |
|---|---|
| Started blocking | 21 |
| Stopped blocking | 15 |
| Blocked in both | 201 |
| Blocked in neither | 5,652 |
| Net change | +6 |
How to block or allow it
Put these in robots.txt at the site root. Per the robots.txt standard, a group naming Kimi-User takes precedence over User-agent: *.
Block the whole site
User-agent: Kimi-User
Disallow: /Allow access
User-agent: Kimi-User
Allow: /It's the 137th most-named crawler of the 171 we counted in the crawler index.
Which other crawlers does this operator run?
How we counted
For Kimi-User, the survey covered 10,000 top Tranco sites, collected on 19 October 2026. Files had an 8-second timeout and a 262,144-byte limit. Only available files we could read enter the percentages. Collection and repeat readings used scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
What does naming this crawler tell me?
The 30 files that mention its name do not all record a whole-site ban. Those without one total 4.
Are leading sites different?
For naming rules, 0.7% of the leading sample mentions it, compared with 0.5% overall. Whole-site blocking is 8.0% at leading ranks and 4.1% across the full sample.
How does the nearby crawler compare?
The nearby OpenAI entry reports 30 files that name it and 32 whole-site blocks, 0.5% of readable files. Here, 30 files mention the name and 253 block access, or 4.1%.