Agent readiness report

Is autozone.com ready for AI agents?

AI agent readiness report · platform: Unknown · checked 2026-11-08 · log in to re-run
22%
Not agent-ready
autozone.com · 7 standards read
autozone.com has 2 of 7 readable agent standards in place; missing A2a, Anp, Ucp, Ap2, Openapi. 2 could not be read because the site refused our request (Mcp, Webmcp), so they are not counted.
Not agent-readyUnknown2/7 readable verified
Agent standards verified2/7
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
0/18 AI crawlers reached the homepage (18 blocked)0%
Ranks above 56% of 285 sites checked (corpus avg 21/100)56%

Assessment

2 of 7 readable agent-readiness checks verified (2 could not be read: the site refused our request). Our request with an ordinary browser user-agent was refused too, so the crawler results describe our checker being blocked, not rules about AI crawlers. See per-protocol drawers for evidence and fix-it files.

Per-protocol results

Mcpcould not read /mcp (403) - the site refused our request, so this is not a findingCould not read
Webmcpcould not read the homepage HTML, so page-source markers could not be checkedCould not read
A2ano /.well-known/agent.json or /.well-known/agent-card.jsonNot found
Anpno /.well-known/agent-descriptions and no did:wba identity at /.well-known/did.jsonNot found
Ucpno /.well-known/ucpNot found
Ap2no /.well-known/ucp, so no AP2 declaration (AP2 is declared as a UCP capability)Not found
Openapino /openapi.json, /api/openapi.json, or /.well-known/openapi.jsonNot found
Llms Txt/llms.txt present, 9 sectionsVerified
WikidataWikidata entity Q4826087 (AutoZone)Verified

.well-known files

.well-known/mcp.jsonnot found404
Mcp Well Known Altnot found404
/mcp endpointcould not read403
Ai Plugin Legacynot found404
.well-known/agent.jsonnot found404
.well-known/agent-card.jsonnot found404
Anp Discoverynot found404
Anp Didnot found404
Openapi Well Knownnot found404
Openapi Rootnot found404
Openapi Api513 bytes200
Ucp Profilenot found404
Llms Txt6230 bytes200
Llms Full Txtnot found404
robots.txt3952 bytes200
sitemap.xmlcould not read403

AI crawler audit

0 of 18 AI user-agents reached the homepage.
Our request with an ordinary browser user-agent was refused as well (HTTP 403 before, 403 after). This site was blocking our checker, so read these counts as "could not check", not as rules about AI crawlers.
9 of 18 were tested with the operator's published user-agent string and the rest with the bare token, since no published string was found. A request that only names a user-agent does not prove the real crawler would be treated the same.

Fix these first

  1. Let our checker read your site: 2 of our checks could not be read (MCP, WebMCP), so they are left out of your score. Serve /.well-known/*, /llms.txt and /robots.txt to automated requests without a block or a redirect, then run the check again.
  2. UCP: Publish a UCP profile at /.well-known/ucp so AI agents can find your catalog, cart and checkout. Shopify serves one for every store; on other platforms it takes an app or a developer.
  3. OpenAPI: If you have a public API, publish its OpenAPI description at /.well-known/openapi.json so agents can plan calls to it.
  4. A2A: Publish an A2A agent card at /.well-known/agent.json if you run an agent that other agents can hand tasks to.
  5. AP2: AP2 (agent payments) usually arrives through your checkout or payment provider. Ask them whether and when they support it.
Run it again for today's result, then sign up free for one fix file per gap. Not yours? Put your own store in.

What this means for autozone.com

On autozone.com (Unknown), 2 of 7 readable agent standards are in place: Llms Txt, Wikidata. Missing: A2a, Anp, Ucp, Ap2, Openapi.

Without JavaScript, your brand name does not appear in the raw HTML, so crawlers that do not run JS see an empty shell.

autozone.com scores higher than 56% of the 285 sites checked here so far; the average readiness score is 21/100.

Make autozone.com agent-ready

Start with the highest-impact gap: A2a. Publish a working MCP endpoint at /.well-known/mcp.json (the initialize handshake must succeed, not just return 200), add an A2A agent card, and keep the crawler path clean.

Frequently asked questions

Are these real probes or AI guesses?

Real probes. We fetch the actual files, run a real MCP initialize handshake, and validate A2A cards against their schema. No model decides the result.

Does autozone.com need every standard to pass?

No. Start with the highest-impact gap above, then add the rest. Most sites win the most by shipping a working MCP endpoint and keeping the crawler path clean.

Check your own site free

Run the same protocol probes on any URL, then sign up free for the copy-paste fix-it files and the full 20-crawler audit.

Run a free check

Agent readiness on Unknown

We have checked 46 other sites on Unknown. The Unknown hub aggregates protocol verification rates and average readiness scores across every Unknown site checked here.

Is Unknown ready for AI agents?