MistralAI-User — Mistral fetch agent
MistralAI-User is the token Mistral uses for real-time fetches that support Le Chat, its assistant. Mistral documents its agents; where a specific is not clearly covered, it is marked partially verified rather than guessed. It identifies itself with the MistralAI-User token plus a self-identifying URL.
What this means
MistralAI-User is the token Mistral uses for real-time fetches that support Le Chat, its assistant product. It appears in logs as an automated fetcher carrying the MistralAI-User token, triggered by user activity rather than a scheduled bulk crawl.
Where Mistral's public documentation is incomplete on a particular specific, this entry describes the stable identification pattern and avoids asserting details that cannot be confidently sourced.
How MistralAI-User identifies itself
MistralAI-User uses the robots.txt user-agent token MistralAI-User. Its user-agent string contains that token together with a self-identifying URL. Match on the stable token rather than a full version string.
The user agent is a claim and can be copied. Use Mistral's published guidance where authenticity matters, and do not invent IP ranges for verification.
- robots.txt token: MistralAI-User
- Real-time fetch in support of Le Chat
- User agent contains the token plus a Mistral URL
robots.txt considerations
To disallow MistralAI-User site-wide, target its token:
User-agent: MistralAI-User Disallow: /
MistralAI-User is expected to honour robots.txt as a compliant agent. robots.txt is a request, not an access-control boundary.
How it appears in analytics and logs
A request carrying the MistralAI-User token means Mistral fetched the URL in real time in support of Le Chat — a user-triggered bot fetch, not a background bulk crawl and not a human page view. Identify it by the token and treat thin specifics conservatively.
Diagnostic use case
Identify MistralAI-User in logs by its token and set robots.txt policy for Mistral's real-time fetch agent.
What WebmasterID can help detect
WebmasterID classifies MistralAI-User server-side by its token and surfaces it on the bot-intelligence and AI-visibility surfaces, so you can see Mistral's real-time fetch activity per page without parsing logs.
Common mistakes
- Asserting documented behaviour where Mistral's public docs are thin.
- Inventing IP ranges to verify MistralAI-User.
- Counting real-time fetches as human page views.
Privacy and accuracy notes
Detection uses only the request user-agent. The fetch is triggered by a person, but no visitor identity is exposed beyond a bot request. WebmasterID records it as a bot event, separate from human analytics, and never builds a visitor profile from it.
Related pages
- Real-time AI fetcher agents
Real-time AI fetcher agents — such as ChatGPT-User, Claude-User, and Perplexity-User — retrieve a specific page live when a person asks an assistant about it. They are user-triggered, not bulk crawls, and each has its own robots.txt token controlled separately from the vendor's background crawler.
- Perplexity-User — Perplexity real-time fetch
Perplexity-User is the token Perplexity uses for real-time fetches triggered by a user's question, as opposed to the PerplexityBot indexing crawler. Perplexity documents both. It identifies itself with the Perplexity-User token plus a self-identifying URL, and is a user-triggered fetch rather than a bulk crawl.
- AI visibility analytics
See which AI crawlers and assistants reach your site, recorded server-side.
Sources and verification notes
- Mistral — agents and crawler referenceToken observed in logs; some specifics are thin in public docs, so marked partially verified.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.