ipapi.gr

Bot signals — AI crawler & agent

MistralAI-Index IP addresses

Mistral AI search indexing; no claim about the unlisted training fleet.

risk.is_airisk.is_crawler Ranges Reviewed
Official documentation (opens in a new tab) All AI crawlers & agents

Check an IP

Is this IP really MistralAI-Index?

Checks the address against what MistralAI-Index publishes, the same evidence behind risk.is_ai.

01 — Verification

How IPAPI.GR verifies MistralAI-Index.

Only from what MistralAI-Index publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official file for the current list.

02 — In the response

What a match looks like.

A lookup of a MistralAI-Index address sets risk.is_ai and risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.

This publication is AI crawling or retrieval traffic, so it counts as both an AI source and a crawler.

The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be MistralAI-Index but doesn't match is unverified.

GET /api/lookup/{ip}?key=PRO_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": true,
    "is_crawler": true,
    "is_scanner": false
  }
}

03 — Configuration

Allow, block or verify it yourself.

nginx + jq
# 1. Build a geo include from the official file (cron, e.g. hourly).
#    Keep the old file if the download fails or comes back empty.
curl -fsS https://mistral.ai/mistralai-index-ips.json \
  | jq -r '.prefixes[] | (.ipv4Prefix // .ipv6Prefix // empty) | "\(.) 1;"' \
  > /etc/nginx/mistralai-index-ranges.conf.new && [ -s /etc/nginx/mistralai-index-ranges.conf.new ] && mv /etc/nginx/mistralai-index-ranges.conf.new /etc/nginx/mistralai-index-ranges.conf \
  && nginx -t -q && nginx -s reload

# 2. In the http block: 1 when the client IP is in the published ranges.
geo $mistralai_index_ip {
    default 0;
    include /etc/nginx/mistralai-index-ranges.conf;
}
Built from mistral.ai/mistralai-index-ips.json, a JSON file with a prefixes array.

04 — Questions

About MistralAI-Index.

Where does MistralAI-Index publish its IP addresses?

MistralAI-Index publishes its addresses at https://mistral.ai/mistralai-index-ips.json. IPAPI.GR reads that publication directly, not a third-party copy.

How often is the MistralAI-Index list refreshed?

IPAPI.GR re-fetches it every hour. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.

Which risk flag does MistralAI-Index set?

A matching address sets risk.is_ai and risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.

From the blog

Go deeper.

Related operators

Every operator on the coverage page →

Verify MistralAI-Index on every request.

Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.

See Pro Start free