---
language: en
title: "MistralAI-User"
description: "MistralAI-User identifies page accesses requested by Vibe users. Learn its purpose, how to verify its origin, and what site controls apply."
canonical: "https://tropk.ai/en/resources/glossary/mistralai-user"
last_modified: "2026-10-12T16:11:10.539Z"
---

# MistralAI-User

Reviewed on 2026-10-06.

## What it means

MistralAI-User is the identifier documented by Mistral for requests associated with user actions in Vibe. When answering a question, the service may visit a page and include a link to the source. Documentation reviewed in October 2026 distinguishes this access from automated [crawling](/en/resources/glossary/crawling) for [indexing](/en/resources/glossary/indexing) and data collection for training.

## Why it matters for marketing

For marketing, this distinction helps explain why a public page was not accessed during a Vibe interaction. A rule targeting user-requested access may affect that request even when human visitors can open the page. The decision should take into account the content the company intends to make available and the access restrictions in place.

## Example in practice

Imagine a manufacturer with a public page about filter compatibility. A user asks Vibe to access the page, but the server log shows a request identified as MistralAI-User receiving HTTP 403. After confirming the origin, the team reviews the blocking rule and decides to allow access to that page in accordance with its policy.

## How to apply or verify

To verify access to the compatibility page, infrastructure teams should compare the identifier received with Mistral’s documentation and official IP address list. They should also examine [robots.txt](/en/resources/glossary/robots-txt), CDN rules, and response logs for that address. A request made through Vibe can help observe access; its outcome should be recorded without assuming the page was successfully read.

## Important distinctions

The name in the [User-Agent header](/en/resources/glossary/user-agent) can be imitated and does not confirm the origin on its own. MistralAI-Index concerns indexing for search; MistralAI-Training collects data for training, according to the purposes stated by the operator. Allowing MistralAI-User does not mean that other bots were granted access, that the page will be cited, or that there was authorization to access private content.

## Sources and references

- [Mistral crawlers](<https://docs.mistral.ai/robots>) — Mistral AI
- [HTTP Message Signatures for automated traffic — draft-ietf-webbotauth-httpsig-protocol-00](<https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/>) — IETF

## Continue a leitura

- [Crawler purpose category](</en/resources/glossary/crawler-purpose-category>)
- [User agent](</en/resources/glossary/user-agent>)
- [robots.txt](</en/resources/glossary/robots-txt>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)