AI crawler · registry

MistralAI-User

Mistral AI · Live retrieval · robots.txt token mistralai-user

honors robots.txtMeasured across 3,958 sites with a robots.txt policy record for this agent, out of 7,068 on record.
3%
of measured sites block it
120
sites blocking
3,838
sites allowing
yes
honors robots.txt

What it is definition

Fetches pages on demand so Mistral's Vibe assistant can answer a question with live, cited web content.

MistralAI-User is operated by Mistral AI and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.

Disallowing mistralai-user stops the fetch that happens when a user asks Le Chat about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

robots.txt token
mistralai-user
Operator
Mistral AI
Purpose
Live retrieval
Honors robots.txt
yes
Documentation
https://docs.mistral.ai/robots/

Identity on the wire exact string

User-agent string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; MistralAI-User/1.0; +https://docs.mistral.ai/robots)
Verify your own edge is not refusing it
curl -A 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; MistralAI-User/1.0; +https://docs.mistral.ai/robots)' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

How to allow it, how to block it robots.txt

Allow it
User-agent: mistralai-user
Allow: /

Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.

Block it
User-agent: mistralai-user
Disallow: /

Disallowing mistralai-user stops the fetch that happens when a user asks Le Chat about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

Sites that block it 60 shown

DomainAI access scoreRank
amazon.com 33 26
tiktok.com 41 54
msn.com 34 62
amazonvideo.com 55 121
cnn.com 50 190
amazon.co.uk 33 318
amazon.de 33 377
amazon.co.jp 33 494
wired.com 74 533
usatoday.com 55 552
uol.com.br 74 571
telegraph.co.uk 45 580
amazon.fr 33 609
amazon.co.za 33 623
dailymail.co.uk 63 627
amazon.ca 33 635
elpais.com 45 647
amazon.in 34 659
cnet.com 75 662
lemonde.fr 72 671
dailymail.com 63 681
primevideo.com 55 682
amazon.it 33 706
amazon.es 33 725
bild.de 74 763
welt.de 65 800
people.com 38 801
amazon.com.au 33 812
theverge.com 68 815
nbcnews.com 63 823
amazon.com.br 33 833
lefigaro.fr 74 834
investopedia.com 38 913
theatlantic.com 68 980
theconversation.com 52 1,019
amazon.com.mx 33 1,032
spiegel.de 72 1,042
as.com 45 1,061
bfmtv.com 71 1,073
franceinfo.fr 66 1,098
ad.nl 47 1,190
nu.nl 47 1,191
furaffinity.net 41 1,223
hln.be 47 1,251
actu.fr 76 1,286
iltalehti.fi 50 1,409
newyorker.com 71 1,793
zdnet.com 61 1,831
wikihow.com 72 1,835
arstechnica.com 74 1,847
themoviedb.org 61 1,984
ign.com 64 1,993
amazon.eg 34 2,006
mashable.com 62 2,010
vox.com 66 2,189
techradar.com 83 2,215
congress.gov 33 2,293
nrk.no 61 2,325
pcmag.com 65 2,423
livescience.com 81 2,585

Compare Mistral AI

Mistral AI runs 3 agents in this registry, and they do different jobs. Blocking one says nothing about the others.

Common questions answered

Does blocking MistralAI-User remove me from Le Chat?

Partly. MistralAI-User fetches a page only when a user asks about it, so disallowing it does not delist you from Le Chat. It does mean the answer is composed without your live page, from a stale copy or a third-party summary.

How do I verify MistralAI-User requests are genuine?

Mistral AI publishes neither reverse DNS names nor address ranges for MistralAI-User, so a request carrying this user agent cannot be authenticated. The string is trivially spoofed and is routinely reused by unrelated scrapers. Treat it as a hint, rate-limit by source address, and do not grant it access you would not grant an anonymous client.

Check your own site free

See whether your robots.txt admits MistralAI-User today, and whether your edge agrees with it.