ipapi.gr

Bot signals — AI crawler & agent

Amazon Amzn-User IP addresses

Amazon user-triggered AI retrieval egress.

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 Amazon Amzn-User?

Checks the address against what Amazon Amzn-User publishes, the same evidence behind risk.is_ai.

01 — Verification

How IPAPI.GR verifies Amazon Amzn-User.

Only from what Amazon Amzn-User 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 Amazon Amzn-User 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 Amazon Amzn-User 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 — Questions

About Amazon Amzn-User.

Where does Amazon Amzn-User publish its IP addresses?

Amazon Amzn-User publishes its addresses at https://developer.amazon.com/amazonbot/live-ip-addresses/. IPAPI.GR reads that publication directly, not a third-party copy.

How often is the Amazon Amzn-User 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 Amazon Amzn-User 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 Amazon Amzn-User 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