MistralAI-User
Mistral AI · Live retrieval · robots.txt token mistralai-user
1% of 30,177 measured domains disallow mistralai-user in robots.txt at the site root. Separately, and independently of robots.txt, 17.4% of 30,187 reachable domains refuse an AI crawler user agent at the network edge on two consecutive probes from different locations - a refusal the site's own robots.txt does not declare and its owner often has not chosen.
Measured 2026-10-06 by direct request to every domain in the corpus. Method: how this is measured. Reuse under CC BY 4.0 with attribution.
Cite as: Crawl Census, "MistralAI-User blocking rate", measured 2026-10-06. https://crawlcensus.com/bot/mistralai-user
What it is definition
Fetches pages on demand so Mistral's Vibe assistant can answer a question with live, cited web content.
MistralAI-User is operated by Mistral AI and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.
Disallowing mistralai-user stops the fetch that happens when a user asks Le Chat about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.
- robots.txt token
- mistralai-user
- Operator
- Mistral AI
- Purpose
- Live retrieval
- Honors robots.txt
- yes
- Documentation
- https://docs.mistral.ai/robots/
Identity on the wire exact string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; MistralAI-User/1.0; +https://docs.mistral.ai/robots)curl -A 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; MistralAI-User/1.0; +https://docs.mistral.ai/robots)' https://example.com/Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.
How to allow it, how to block it robots.txt
User-agent: mistralai-user
Allow: /Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.
User-agent: mistralai-user
Disallow: /Disallowing mistralai-user stops the fetch that happens when a user asks Le Chat about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.
Sites that block it 60 shown
See every measured domain that blocks MistralAI-User
This list is served from a cache rebuilt just now. It is discarded the moment a rescan records a policy change for this agent, so a site that has just changed its robots.txt will drop off it within one scan rather than waiting for the cache to expire.
Compare Mistral AI
Mistral AI runs 3 agents in this registry, and they do different jobs. Blocking one says nothing about the others.
Common questions answered
Does blocking MistralAI-User remove me from Le Chat?
Partly. MistralAI-User fetches a page only when a user asks about it, so disallowing it does not delist you from Le Chat. It does mean the answer is composed without your live page, from a stale copy or a third-party summary.
How do I verify MistralAI-User requests are genuine?
Mistral AI publishes neither reverse DNS names nor address ranges for MistralAI-User, so a request carrying this user agent cannot be authenticated. The string is trivially spoofed and is routinely reused by unrelated scrapers. Treat it as a hint, rate-limit by source address, and do not grant it access you would not grant an anonymous client.
Check your own site free
See whether your robots.txt admits MistralAI-User today, and whether your edge agrees with it.