Mistral AI's AI agents and crawlers

AI assistants

Fetches pages for a person, in real time, while they use an AI assistant. Almost always allow it. Blocking it means the assistant can't read your pages when a customer asks about you, so it answers from somewhere else.

• MistralAI-User: Fetches a page when someone using Mistral's Le Chat asks for it. It acts for one person, in real time.

AI and search crawlers

Indexes pages so a search engine or AI search tool can find, cite and link to them. Allow it, unless you deliberately want to stay out of that search engine. Blocking it removes you from its results and answers.

• MistralAI-Index: Mistral AI's crawler for indexing pages its products can search.

AI training crawlers

Collects public pages that may be used to train AI models. A real business choice. Lean towards blocking if your content is the product (publishing, research, courses); lean towards allowing if your pages exist to sell something else.

• MistralAI-Training: Mistral AI's crawler for collecting data that may be used to train its models.

Robots.txt for every Mistral AI agent

To keep Mistral AI's training crawlers out but still let its assistants, search and agents in:

User-agent: MistralAI-Training
Disallow: /

To block every Mistral AI agent that reads robots.txt. This also keeps out the ones acting for your customers and the ones that send you visitors, so think twice:

User-agent: MistralAI-User
User-agent: MistralAI-Index
User-agent: MistralAI-Training
Disallow: /

Robots.txt is a request, not a lock, and some agents that act for a person in real time may not read it. A decision guide for blocking or allowing AI crawlers.

How to tell if it's really Mistral AI

Our registry doesn't verify Mistral AI's agents against published IP ranges, so treat a request that uses one of their names as a claim, not proof. Ghost Agent Lab reports these requests as unverified rather than guessing.