MistralAI-Index
Mistral AI · AI search · robots.txt: Yes
Crawls the web automatically to index content for Mistral search, which helps answer questions in Mistral's Vibe assistant.
Block MistralAI-Index
User-agent: MistralAI-Index
Disallow: /
Blocking MistralAI-Index keeps your pages out of the index behind Mistral search and Vibe’s answers. Mistral says content it crawls is not used for generative AI training of any kind; training has its own token, MistralAI-Training.
Allow MistralAI-Index
User-agent: MistralAI-Index
Allow: /
An allow group only changes anything if a broader rule would block MistralAI-Index. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks MistralAI-Index on a given path, and which line decides.
Block or allow it at the server
robots.txt asks; a server rule refuses. Every rule here matches MistralAI-Index, spelled as in the User-Agent Mistral AI documents (“compatible; MistralAI-Index/1.0;”), and matches it case-sensitively. The server answers 403.
What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user.
(Apache HTTP Server 2.4 documentation). A fake MistralAI-Index is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Mistral AI's published addresses.
Addresses in the “only the real one” rules: Mistral AI's list mistral.ai/mistralai-index-ips.json, 2 ranges, fetched 8 Oct 2026, list dated 19 Apr 2026. Operators change their lists; compare the date with the live list before you rely on it.
The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.
Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 2 block MistralAI-Index from the whole site by name, 38 block it through their User-agent: * group, and 0 name it with partial rules (some paths closed, the home page open). 0 more name it only to let it in.
2
block it by name 0.4%
38
block it through * 7.5%
0
name it, partial rules 0.0%
Percentages are of the 508 files we could read, not of all 1,000 sites.
Highest-ranked sites that block MistralAI-Index by name
- lemonde.fr rank 711
- people.com rank 822
Each links to the site's live robots.txt, which may have changed since 2026-10-09.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
Facts
- Operator
- Mistral AI
- Purpose
- AI search index
- Obeys robots.txt
- Yes. Mistral documents MistralAI-Index as one of the robots.txt tokens it uses so webmasters can manage how their sites and content interact with its AI.
- In your server logs
- The user-agent string contains "compatible; MistralAI-Index/1.0;".
- How to verify it
- Match the IP against Mistral’s published MistralAI-Index IP list.
Published list: mistral.ai/mistralai-index-ips.json — 2 IPv4 ranges when we fetched it, list dated 19 Apr 2026. Always match against the live list; operators update them. To count real and fake MistralAI-Index requests in your own server log against this list, drop the log into the log reader.
What Mistral AI says
Quoted word for word from the operator's documentation.
“MistralAI-Index is for automated crawling of the web for indexing purposes only. It indexes content for Mistral search, which helps answer user questions in Vibe.”
“Content crawled by MistralAI-Index is not used for generative AI training of any kind.”
“To help webmasters manage how their sites and content interact with AI, Mistral uses specific robots.txt tags.”
“Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; MistralAI-Index/1.0;”
“All published IP addresses: MistralAI-Index IP addresses”
Sources
- Mistral Docs: Mistral crawlers — fetched and checked 2026-09-24
- Mistral: MistralAI-Index IP addresses (mistralai-index-ips.json) — fetched and checked 2026-09-24