AI crawler list · Mistral AI · User-triggered fetcher
MistralAI-User
Visits pages when a user asks Mistral's Vibe assistant a question and links to the source. Mistral says it is not used for automatic crawling or to collect training data, and robots.txt determines which sites it can reach.
Facts checked against Mistral AI docs on Oct 20, 2026.
Is MistralAI-User allowed on your site?
Reads your robots.txt and requests your page as each AI bot. Free, no signup.
Should you allow it?
Allow it.
If you block it: Mistral's assistant cannot visit your pages to answer users' questions.
robots.txt rules
User-agent: MistralAI-User Allow: /
User-agent: MistralAI-User Disallow: /
User-agent: MistralAI-User Disallow: /private/ Allow: /
Put each User-agent group in the robots.txt at your domain root. A bot follows the most specific group that names it and ignores the generic User-agent: * group, so repeat any shared Disallow lines inside it. Build a full file with the AI robots.txt generator.
Same company, different bots: Mistral AI
Mistral AI uses separate user agents for separate jobs. Blocking one does not block the others.
| Bot | Purpose | Obeys robots.txt | If you block it |
|---|---|---|---|
MistralAI-UserUser-triggered fetcher | Mistral Vibe (user requests) | Yes | Mistral's assistant cannot visit your pages to answer users' questions. |
MistralAI-IndexAI search index | Mistral search | Yes | Your content is not indexed for Mistral search. |
MistralAI-TrainingAI training crawler | Mistral model training | Yes | Your content is not collected for Mistral's training datasets. |
User-agent: MistralAI-User User-agent: MistralAI-Index Allow: / User-agent: MistralAI-Training Disallow: /
User agent string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; MistralAI-User/1.0; +https://docs.mistral.ai/robots)
Versions in the string can change. Match on the token MistralAI-User, and verify real traffic as shown below rather than trusting the header.
How to verify it's really MistralAI-User
Find its requests in your server logs (the path to your access log depends on your host):
grep -i "MistralAI-User" access.log
Mistral publishes IP lists for MistralAI-User and MistralAI-Index.
Published IP list: mistral.ai/mistralai-user-ips.json
Check one IP against the list (prints True or False):
curl -s https://mistral.ai/mistralai-user-ips.json | python3 -c "import sys,re,ipaddress as a; ip=a.ip_address(sys.argv[1]); print(any(ip in a.ip_network(c,strict=False) for c in re.findall(r'[0-9a-fA-F:.]+/[0-9]+', sys.stdin.read())))" 203.0.113.7
Common mistakes
- Writing a User-agent: MistralAI-User group and expecting your User-agent: * rules to still apply. A crawler follows only the most specific group that matches it and ignores the others, so repeat any shared Disallow lines inside the MistralAI-User group.
- Leaving a CDN or host "block AI bots" setting on and only checking robots.txt. Those settings block requests at the network edge. Cloudflare, for example, changed its defaults on September 15, 2026 for customers who did not opt out: bots it classifies as Training or Agent are blocked on pages that display ads, and multi-purpose crawlers that combine Search and Training are affected by the Training block.
- Trusting the user agent header alone. Anyone can send "MistralAI-User" in a request; verify the source IP as shown above before allowlisting or blocking.
FAQ
Visits pages when a user asks Mistral's Vibe assistant a question and links to the source. Mistral says it is not used for automatic crawling or to collect training data, and robots.txt determines which sites it can reach.
Yes, according to Mistral AI.
Mistral's assistant cannot visit your pages to answer users' questions.
Allow it.
Sources
- Official documentation from Mistral AI
- Published IP addresses for MistralAI-User
- Cloudflare bots changelog (AI bot policy defaults)
Related AI crawlers
ChatGPT-User · OAI-AdsBot · Claude-User · Perplexity-User · Google-CloudVertexBot · meta-externalfetcher · Amzn-User · MistralAI-Index
Facts checked against Mistral AI docs on Oct 20, 2026. Spot an error? rankroot.support@proton.me