AI crawlers · Mistral

MistralAI-User

MistralAI-User is a crawler operated by Mistral, and it fetches your page while a person waits for an answer — the fact that decides everything else on this page.

What does MistralAI-User actually do?

MistralAI-User is Le Chat opening a page because somebody's question needs it. Note where the registry's documentation link points: Mistral's general developer docs, not a crawler reference. The operational detail other vendors publish - address ranges, hostname suffixes, a verification procedure you can implement - is simply not there to be implemented.

So there is nothing to check a request against. Anything carrying this user-agent is a claim with no supporting evidence available anywhere, which means both the allow decision and the block decision rest entirely on a header. If your rules treat verified agents differently from unverified ones, this agent lands in the second group by default and stays there.

That matters less than it would for a bulk crawler, because the pattern is small and specific rather than sustained. The real question is not bandwidth. It is whether you want a consumer assistant able to read your pages at the moment a question is asked, and robots.txt is the only lever anyone has published for saying no.

It is worth being precise about what kind of silence this is. OpenAI, Perplexity and Meta have each published that their user-triggered fetchers may not be bound by robots.txt; Mistral has published nothing either way. So the file is the only lever available and nobody has said whether it works. That is a weaker position than an explicit exemption, because an exemption at least tells you to go and enforce the rule somewhere else.

CrawlClick files MistralAI-User as a query time crawl. What the three crawl purposes mean.

Mistral runs one agent in this registry, which makes MistralAI-User the whole of the decision. Vendors that split the work across several tokens let a publisher decline one job and keep another; Mistral publishes no second name here, so there is nothing to separate. Whatever you settle on for MistralAI-User governs every use Mistral makes of your pages until another token appears — which is a coarser instrument than it looks, and worth weighing before the query time label decides it for you.

Should I block MistralAI-User?

It is left out of robots.txt because the name is unfamiliar, which is an allow decision made by omission rather than on purpose.

To block it anyway, add this to robots.txt (how the rules resolve):

User-agent: MistralAI-User
Disallow: /

Replace Disallow: / with Allow: / to permit it explicitly. A crawler that ignores robots.txt is not blocked by it either way — that is what verification and edge rules are for.

How do I verify MistralAI-User is genuine?

Mistral publishes no way to check this one, so a request claiming to be MistralAI-User cannot be confirmed. Treat it as unverified and never bill anything against it.

The verification procedure explains why a reverse lookup has to be forward-confirmed, and why a published range list has to be re-fetched rather than pinned.

How do I find MistralAI-User in my logs?

Match the user-agent against "mistralai-user", case-insensitively. Every MistralAI-User fetch had somebody waiting on it, so this count maps onto real questions being asked about your pages rather than onto crawl budget.

Crawl-to-referral gap defines the ratio, and the rate-limiting guide covers what to do when the volume itself is the problem.

Registry last reviewed 2026-09-13.