MistralAI-User
Mistral's fetcher for Le Chat: retrieves pages when users ask the assistant about live web content.
MistralAI-User/1.0Official documentation: docs.mistral.ai
What MistralAI-User does
MistralAI-User fetches specific pages in response to user queries in Mistral's Le Chat assistant. Mistral documents the user agent and states it honors robots.txt directives.
Why it visits your site
On-demand answers with citations; single-page fetches driven by user questions.
The bigger picture: AI user agents
User-agent fetchers are not crawlers in any meaningful sense: each request happens because a specific person asked an assistant about a specific page, right now. The pattern in your logs is the opposite of a crawl - single pages, irregular timing, no systematic walk of your archive. It is closer to a human visit with an unusual browser than to bot traffic, and treating its volume as an engagement signal - which of your pages do people ask AI about? - is more useful than treating it as load.
This category is also where the robots.txt social contract gets genuinely contested. Some operators apply robots rules to these fetches anyway; at least one documents that it does not, on the argument that an agent acting on a user's explicit request is the user's browser, not a robot. Wherever that debate settles, the practical takeaway for site owners is that policy files govern this category unevenly, and server-side visibility is how you know what is actually happening.
Should you block it?
Low volume, user-driven, and documented. Most sites gain nothing by blocking it.
Block via robots.txt
Add these lines to the robots.txt at your site root to ask MistralAI-User to stay away:
User-agent: MistralAI-User Disallow: /
Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.
How to see MistralAI-User traffic on your site
You have three windows onto it, each with a catch. Raw hosting access logs contain every MistralAI-User request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because MistralAI-User doesn't run scripts.
Viz's answer is the request log: filter to MistralAI-User and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.