Scan a URL
The Index › Retail › amazon.com
F

Amazonamazon.com

13/ 100 · Agentic Usability Score
WalledScanned 2026-09-22 · cloudflare-edge · method v0.1Edge: cloudflare
Muse
Meta
✕Blocked
ChatGPT Agent
OpenAI
⊘Disallowed
Claude
Anthropic
⊘Disallowed
Comet
Perplexity
⊘Disallowed
Grok Bot
xAI
⊘Disallowed
Gemini
Google
⊘Disallowed
Manus
Manus
⊘Disallowed
Instinct
Spear Street
?Untested

Score breakdown

Five pillars. Task completion is pending until the live task runner ships; the other four are rescaled to 100.
Accessrobots.txt stance + live door test
9/40
Consent & identity pathContent-Signal, published agent policy
0/10
Machine-readable surfacellms.txt, JSON-LD, landmarks, SSR
3/25
Agent protocolsUCP, MCP, A2A, OpenAPI
0/15
Task completionlive agent run: search → cart → checkout
pending

Evidence

Generated by the scanner from this run. Every line is reproducible with the open-source probe.
  • ✕robots.txt disallows 15 of 19 user-directed agents: ChatGPT-User, Claude-User, Perplexity-User, GoogleAgent-Mariner, GoogleAgent-Shopping, Manus-User, MistralAI-User, Devin…
  • ✕Homepage returns a bot interstitial (HTTP 202) to every non-browser client, agents included
  • ◐robots.txt names 100 user-agents
  • ◐Also disallows 10 of 15 training/search crawlers (not scored; agents ≠ crawlers)
  • ◐No Content-Signal in robots.txt
  • ◐No llms.txt
  • ◐No agent-protocol manifest (UCP, MCP, A2A, OpenAPI)
Identified asHTTPResult
ChatGPT-User202blocked
Claude-User202blocked
Perplexity-User202blocked
GoogleAgent-Mariner202blocked
browser (human)202interstitial

What Amazon would need to change

1Verify agents cryptographically instead of blocking them at the doorAccess · up to 23 pts

Your edge answers every non-browser client with a block or interstitial. Web Bot Auth (HTTP Message Signatures, RFC 9421) lets an agent prove who it is per request; Cloudflare, Akamai, AWS WAF and Vercel can verify it. Allow verified agents and keep challenging the rest.

# Cloudflare: Security → Bots → Verified bots → allow category "AI Agent"
# Or verify yourself: fetch the agent's key from
#   https://<signature-agent>/.well-known/http-message-signatures-directory
# and check the Signature / Signature-Input headers (tag="web-bot-auth")

2Stop disallowing identified user-directed agents in robots.txtAccess · up to 13 pts

You disallow 15 agents that act live for a person. Crawler rules (GPTBot, ClaudeBot) can stay; user-directed agents are the ones a customer sends.

User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Perplexity-User
User-agent: GoogleAgent-Mariner
User-agent: GoogleAgent-Shopping
User-agent: Manus-User
Allow: /

3Give agents a front doorProtocols · up to 12 pts

A Universal Commerce Protocol manifest for shopping, or an MCP server card for everything else. An agent that can call an API never needs to hold a customer's password.

GET /.well-known/ucp
{ "ucp": { "version": "2026-01-23",
  "services": { "dev.ucp.shopping": [{ "transport": "rest", "endpoint": "https://www.amazon.com/api/ucp/v1" }] },
  "capabilities": { "dev.ucp.shopping.checkout": [ … ] } } }

# or
GET /.well-known/mcp.json
{ "name": "Amazon", "endpoint": "https://www.amazon.com/mcp", "transport": "streamable-http" }

4Publish llms.txtSurface · up to 8 pts

A short markdown map of what the site does, where the important pages are, and how to search or check out.

/llms.txt
# Amazon
> One paragraph on what this site is for.
- [Products](/products): how to search and filter
- [Checkout](/checkout): steps and constraints

5Say your stance with a Content-SignalConsent · up to 3 pts

Two lines in robots.txt end the guessing game. ai-input covers agents reading pages on a person's behalf.

User-Agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /