`Amzn-User`

Amazon says Amzn-User supports user actions, such as an Alexa query that needs current information, and may fetch a live page on that person's behalf. Because a person can start the action, Amazon says it may not follow all robots.txt directives. Amazon says this token does not crawl content for generative AI model training. The same page says automated crawling by the listed user agents honors allow and disallow. This card follows the Amzn-User paragraph. The checker still reports the RFC 9309 match and does not fetch a host. Amazonbot and Amzn-SearchBot are different tokens.

robots.txt token: Amzn-User
Operator: Amazon
Kind: user_fetch
robots.txt: may_not_apply. The vendor says robots.txt may not apply, because a person triggered the fetch.
HTTP user-agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-User/0.1) Chrome/W.X.Y.Z Safari/537.36 Amazon calls this an example. Chrome/W.X.Y.Z is the placeholder printed on the page, not a version Botcard observed.
IP list: https://developer.amazon.com/amazonbot/live-ip-addresses/ The page links this URL under Amzn-User. On 2026-10-18 it returned HTTP 200, HTML titled Amazonbot Live Crawl IP addresses, and an embedded JSON object with creationTime 2025-11-04T15:57:38.092840+00:00. Botcard does not copy the address list.
Source: About AmazonBot. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/amzn-user

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Amzn-User on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Amzn-User\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["amzn-user"]}}}'

That call returns fetched_target false. This row is disallow via group Amzn-User, rule Disallow: /.