User-requested fetch

MistralAI-User

Retrieves pages for user questions in Vibe.

See your agent traffic
PurposeUser-requested fetch
HTTP identifierMistralAI-User
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

A page fetch may support a user’s current question.

Requested URLs
Response codes
Redirect chains

Your next move

Check the requested page and any redirects that could interrupt retrieval.

The technical details

Markdown
How to identify it

Look for the MistralAI-User identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Compare the source IP with the current MistralAI-User IP list linked from Mistral’s crawler documentation.

Access and robots.txt

The operator documents robots.txt rules for this identifier.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: MistralAI-User
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See MistralAI-User in context

See their requests. Find the pages that matter.

See your agent traffic