Safe Official docs AI & LLM Bots

MistralAI-User/1.0

Q: What is the official user-agent string for MistralAI-User/1.0?

The official user-agent string for MistralAI-User/1.0 is: MistralAI-User . This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from MistralAI-User/1.0 by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Q: Is MistralAI-User/1.0 safe?

Yes. MistralAI-User/1.0 is a documented bot: Mistral AI publishes a page that names it and explains what it does.

Q: How do I block MistralAI-User/1.0 in robots.txt?

Add the following lines to your /robots.txt file: User-agent: MistralAI-User Disallow: / This instructs MistralAI-User/1.0 not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/ ). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt .

Q: How do I verify if MistralAI-User/1.0 is crawling my site?

Search your web server access logs for the string MistralAI-User (case-insensitive grep: grep -i "MistralAI-User" /var/log/nginx/access.log ). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For MistralAI-User/1.0 specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).

Operated by Mistral AI

Scout's quick take

MistralAI-User (MistralAI-User/1.0) visits a page only when a person asks Mistral AI's assistant to open it. It is not a background crawler.

# Block only if you really mean to
User-agent: MistralAI-User
Disallow: /

Open the AI crawler checker Build a full robots.txt

Quick Facts

User-Agent:: MistralAI-User
Category:: AI & LLM Bots
Operator:: Mistral AI
Safety:: Safe
Blocking Impact:: Low - No SEO ranking impact
SEO Impact Score:: 2/10
Official docs:: docs.mistral.ai

Confirmed by the operator

Mistral AI names MistralAI-User on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is MistralAI-User/1.0?

MistralAI-User fetches pages for user actions in Mistral's assistant (Vibe) and links the source in the answer.

Mistral states it is "not used for crawling the web in any automatic fashion, nor to crawl content for generative AI training". Training is MistralAI-Training. It identifies itself with the token MistralAI-User. Mistral AI documents it at docs.mistral.ai.

What happens if you block MistralAI-User/1.0?

Blocking it stops Mistral's assistant from reading your pages when users ask. No effect on Google or Bing.

Consider blocking based on your content strategy.

Want to see whether MistralAI-User/1.0 actually visits you? Read how do I monitor AI bot traffic to my website?

How to block MistralAI-User/1.0 with robots.txt

<code>User-agent: MistralAI-User</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: MistralAI-User
Disallow: /

Allow all (robots.txt)

User-agent: MistralAI-User
Allow: /

Block private only (robots.txt)

User-agent: MistralAI-User
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block MistralAI-User/1.0
if ($http_user_agent ~* "MistralAI\-User") {
    return 403 "Bot blocked";
}

Apache .htaccess

# Apache: Hard-block MistralAI-User/1.0
SetEnvIfNoCase User-Agent "MistralAI\-User" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is MistralAI-User/1.0 safe to allow?

Yes. MistralAI-User/1.0 is a documented bot: Mistral AI publishes a page that names it and explains what it does.

What does MistralAI-User/1.0 do?

From Mistral AI's own documentation.

MistralAI-User fetches pages for user actions in Mistral's assistant (Vibe) and links the source in the answer.
Not used to train AI models, according to the operator
Blocking it stops Mistral's assistant from reading your pages when users ask. No effect on Google or Bing.

MistralAI-User/1.0 in context

MistralAI-User/1.0 is a user-triggered agent operated by Mistral AI. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about MistralAI-User/1.0 rests on what you want from Mistral AI, not on its behaviour. How we rate safety and impact.

How site owners treat MistralAI-User/1.0

Our robots.txt study of the Tranco top 10,000 did not track MistralAI-User as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

MistralAI-User/1.0's operator says it follows robots.txt, so a correctly written MistralAI-User/1.0 group is enough to control it.

Mistral AI crawlers and close alternatives

MistralAI-User/1.0 is one of 4 Mistral AI crawlers in our database. A User-agent: MistralAI-User group controls MistralAI-User/1.0 only; the other Mistral AI tokens below need their own lines.

MistralAI-User: this crawler (Tier 2)
MistralAI-Index: Mistral Search Index, builds a search or answer index (Tier 2)
MistralAI-Training: Mistral Training, collects pages to train AI models (Tier 2)
MistralAI-User-1.0: Mistral AI v1, fetches a page when a person asks an assistant or app to open it (Tier 2)

To give MistralAI-User/1.0 the same answer as its siblings, stack User-agent: MistralAI-User with their lines above one set of rules; to treat MistralAI-User/1.0 differently, give it its own group.

Other AI and LLM crawlers that do the same job (fetches a page when a person asks an assistant or app to open it) include ChatGPT Agent from OpenAI, ChatGPT Operator from OpenAI, ChatGPT-User from OpenAI, ChatGPT-User/2.0 from OpenAI, Claude-SearchBot from Anthropic, Claude-User from Anthropic. Deciding about MistralAI-User/1.0 is usually a decision about the whole group, so check how your file treats these too.

We first recorded MistralAI-User on March 17, 2026. Mistral AI documents it on docs.mistral.ai, and we recheck that page before each release.

Which rule MistralAI-User/1.0 actually follows

MistralAI-User/1.0 reads exactly one group in robots.txt, the most specific one that names MistralAI-User, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: MistralAI-User
Disallow: /drafts/

Find the group. MistralAI-User/1.0 looks for a group naming MistralAI-User. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to MistralAI-User/1.0, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to MistralAI-User/1.0 if the file also has a User-agent: MistralAI-User group?

No. Once a group names it, MistralAI-User/1.0 reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking MistralAI-User/1.0 remove your pages from AI answers?

Often, yes. MistralAI-User/1.0 is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: mistralai-user the same as User-agent: MistralAI-User?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow MistralAI-User/1.0? Decide by situation

Recommended setting for MistralAI-User/1.0 by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Allow it. MistralAI-User/1.0 fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI training	Blocking it does not stop training, because MistralAI-User/1.0 is a user-triggered agent. Block the operator's training crawler instead.
You run an online shop	Allow it on product and category pages, which are the pages shoppers ask assistants about.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check MistralAI-User/1.0 on your own site

Open /robots.txt on your domain and search for MistralAI-User. If it is not named, it follows User-agent: *.
List the Disallow lines in the group MistralAI-User/1.0 follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse MistralAI-User/1.0 even when robots.txt allows it, and that never shows in the file.
Run our AI crawler access test to see how MistralAI-User/1.0 and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with MistralAI-User/1.0

The errors we see most often with MistralAI-User/1.0 in the files and firewalls we test:

Assuming a robots.txt rule will stop MistralAI-User/1.0. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
Blocking MistralAI-User/1.0 as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
Counting MistralAI-User/1.0 visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check MistralAI-User/1.0 from outside after every change.

Spotting MistralAI-User/1.0 in your logs

robots.txt says what MistralAI-User/1.0 may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "MistralAI-User" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "MistralAI-User" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the MistralAI-User/1.0 user-agent, so confirm the source before acting on a match:

MistralAI-User: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable MistralAI-User/1.0 request with caution.

Frequently Asked Questions

What is the official user-agent string for MistralAI-User/1.0?

The official user-agent string for MistralAI-User/1.0 is: MistralAI-User. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from MistralAI-User/1.0 by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Is MistralAI-User/1.0 safe?

Yes. MistralAI-User/1.0 is a documented bot: Mistral AI publishes a page that names it and explains what it does.

Will blocking MistralAI-User/1.0 hurt my SEO?

Blocking it stops Mistral's assistant from reading your pages when users ask. No effect on Google or Bing.

How do I block MistralAI-User/1.0 in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: MistralAI-User
Disallow: /

This instructs MistralAI-User/1.0 not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.

Does MistralAI-User/1.0 respect robots.txt?

Yes. Mistral documents it as a robots.txt token that "governs which sites these user requests can be made to".

How do I verify if MistralAI-User/1.0 is crawling my site?

Search your web server access logs for the string MistralAI-User (case-insensitive grep: grep -i "MistralAI-User" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For MistralAI-User/1.0 specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).

What is the crawl frequency of MistralAI-User/1.0?

Crawl frequency data for MistralAI-User/1.0 is not publicly documented. Monitor your logs to understand actual visit patterns.

Can I block MistralAI-User/1.0 from specific pages only?

Yes. Instead of a global Disallow: / you can restrict MistralAI-User/1.0 to specific paths:

User-agent: MistralAI-User
Disallow: /private/
Disallow: /staging/
Allow: /

This allows MistralAI-User/1.0 everywhere except the listed paths. Path matching in robots.txt uses prefix matching - Disallow: /private/ blocks /private/page.html but NOT /public/private/.

Does blocking MistralAI-User/1.0 prevent AI training on my content?

MistralAI-User/1.0 is not used for AI training, according to Mistral AI. Mistral states it is "not used for crawling the web in any automatic fashion, nor to crawl content for generative AI training". Training is MistralAI-Training.

Is there an alternative to robots.txt to opt out of MistralAI-User/1.0?

The opt-out Mistral AI documents is robots.txt. A firewall, CDN or server rule that returns 403 for MistralAI-User enforces it. Per-bot meta tags and llms.txt are not opt-out mechanisms any major operator documents.