Quick answer: MistralAI-User is the agent Mistral AI uses when a user of its Le Chat assistant asks for information that requires opening a web page. It is a user-triggered fetcher rather than a training crawler. As with other agents acting for a person, treat robots.txt as a request and use a firewall rule if you need a guaranteed block.
- Operator
- Mistral AI
- Type
- User-triggered fetcher
- robots.txt token
MistralAI-User- Follows robots.txt
- User-initiated, treat robots.txt as a request
- Used for
- Fetching pages when Le Chat users ask for information from the web
- User agent
User agent contains MistralAI-User/1.0- How to verify
- Match the user agent; traffic follows user conversations in Le Chat
What is MistralAI-User?
Le Chat can browse the web to answer questions with current information. When it does, the page requests identify as MistralAI-User.
Because the fetch is tied to a specific user request, the traffic pattern is irregular and focused on individual pages, similar to ChatGPT-User and Perplexity-User.
What happens if you block MistralAI-User?
A robots.txt Disallow for MistralAI-User states your preference. Because requests are made on behalf of users, a firewall rule on the user agent is the dependable way to stop them. Blocking means Le Chat cannot read your pages when its users ask.
Should you allow MistralAI-User?
Allow it. It reaches a European audience that many AI SEO strategies ignore, and like other user-triggered agents it only arrives when someone wants what your page offers.
Check whether MistralAI-User can reach your site
Enter your domain or a specific page. The checker reads your live robots.txt, picks the group MistralAI-User would use, and applies the longest matching rule, the same way major crawlers resolve conflicts.
robots.txt rules for MistralAI-User
Put each group in the robots.txt file at the root of your domain. User agent names are matched without regard to case, and the most specific matching group wins.
User-agent: MistralAI-User
Allow: /User-agent: MistralAI-User
Disallow: /User-agent: MistralAI-User
Disallow: /account/
Disallow: /checkout/
Allow: /The rule most people get wrong: once MistralAI-User has its own group, it ignores everything under User-agent: *. If your wildcard group disallows paths such as /admin/, repeat those lines inside the MistralAI-User group too.
Because MistralAI-User acts on behalf of a user, a robots.txt rule states your preference but does not enforce it. To enforce a block, add a firewall rule. On Cloudflare, a custom WAF rule with this expression and the Block action does it:
(http.user_agent contains "MistralAI-User")How to verify real MistralAI-User traffic
Match on the MistralAI-User token and look for the conversational pattern of short bursts on specific URLs. Continuous site-wide crawling under this name is not the documented behaviour and suggests spoofing.
To see how often it visits, count requests by user agent in your access log. On a typical Nginx server:
grep -i "MistralAI-User" /var/log/nginx/access.log | awk '{print $4}' | cut -d: -f1 | sort | uniq -cMistralAI-User compared with similar agents
| Agent | Operator | Type | Follows robots.txt |
|---|---|---|---|
| MistralAI-User | Mistral AI | User-triggered fetcher | User-initiated, treat robots.txt as a request |
| ChatGPT-User | OpenAI | User-triggered fetcher | Not guaranteed, fetches are user-initiated |
| Claude-User | Anthropic | User-triggered fetcher | Yes, per Anthropic's documentation |
| Perplexity-User | Perplexity | User-triggered fetcher | Generally no, fetches are user-initiated |
See all 20 agents side by side in the AI crawler directory.
MistralAI-User FAQ
See every AI crawler signal at once
The free AI SEO audit checks robots.txt access for 12 AI crawlers, plus llms.txt, schema, content and metadata, in a few seconds.
Run the free AI SEO audit