AI assistant fetcher
MistralAI-User
Fetchers that load a page live because a person asked an AI assistant about it.
Last updated
At a glance
| Category | AI assistant fetcher |
|---|---|
| User agent match | contains "mistralai-user" |
| Executes JavaScript | No |
| Respects robots.txt | Generally yes |
| Identity verifiable | No, the name is only a claim |
| IVT class | GIVT (general invalid traffic: declared automation) |
What MistralAI-User is
MistralAI-User fetches a page at the moment a person asks an AI assistant about it. It is closer to a proxy for a human reader than to a crawler on a schedule: each visit is one page loaded because one person wanted its content right then. It does not execute JavaScript.
Can the name be trusted?
There is no published way to verify MistralAI-User: the operator provides no IP ranges and no reverse DNS scheme, so the name in the user agent is only a claim. Any script can send it. TrueVisit still names the traffic, and weighs the claim against behavioral signals instead of trusting it.
Should you block it?
Think twice before blocking MistralAI-User: each of its requests is a person actively asking an assistant about your page. Blocking it makes your content unquotable in that conversation, which is the opposite of what most publishers want. Block it only if you have decided you want nothing to do with AI assistants at all.
For enforcement rather than a polite request, the Cloudflare blocking guide generates copy-paste WAF rules from this same signature list, with guardrails that keep verified search engines safe.
How TrueVisit reports it
Visits from MistralAI-User appear in your bot report under this exact name, never as an anonymous percentage, and every verdict stores the reason it was reached. Because this client never executes JavaScript, a browser-only tracker cannot see it at all; it is visible through server-side collection, which is how the visits reach your report.