What does the agent readiness check test?

Real protocol probes of .well-known files (openapi.json, mcp.json, ai-plugin.json, security.txt), a live MCP initialize handshake, A2A agent-card validation, a 20-user-agent crawler audit, and a JS-parity check.

Is 1800contacts.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-10-18 · log in to re-run

Readiness

0/5

Verified (readable)

Custom

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

1/18 AI crawlers reached the homepage17 blocked

Ranks above 0% of 127 sites checkedcorpus avg 24/100

Not agent-ready

1800contacts.com has 0 of 5 readable agent standards in place; missing A2a, Anp, Ucp, Ap2, Wikidata. 4 could not be read because the site refused our request (Mcp, Webmcp, Openapi, Llms Txt), so they are not counted.

Assessment

0 of 5 readable agent-readiness checks verified (4 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 verdicts

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/did.jsonNot found

Ucpno /.well-known/agentic-commerce.json (and platform is not a UCP-shipping host)Not found

Ap2no /.well-known/ap2.jsonNot found

Openapicould not read /openapi.json (403), /api/openapi.json (403) - the site refused our request, so this is not a findingCould not read

Llms Txtcould not read /llms.txt (403) - the site refused our request, so this is not a findingCould not read

WikidataWikidata has "1-800 Contacts" (Q4545758, American contact lens retailer) with official website contacts.com, not this domain. If that is this company, its website statement does not list this domain, so it is not counted.Found, other domain

.well-known files

.well-known/mcp.json24102 bytes200

Mcp Well Known Alt24102 bytes200

/mcp endpointcould not read403

Ai Plugin Legacy24102 bytes200

.well-known/agent.json24102 bytes200

.well-known/agent-card.json24102 bytes200

Anp Did24102 bytes200

Openapi Well Known24102 bytes200

Openapi Rootcould not read403

Openapi Apicould not read403

Ucp Well Known24102 bytes200

Ap2 Well Known24102 bytes200

Llms Txtcould not read403

Llms Full Txtcould not read403

robots.txt616 bytes200

sitemap.xmlcould not read500

AI crawler audit

1 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.

What this means for 1800contacts.com

On 1800contacts.com (Custom), 0 of 5 readable agent standards are in place. Missing: A2a, Anp, Ucp, Ap2, Wikidata.

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

1800contacts.com scores higher than 0% of the 127 sites checked here so far; the average readiness score is 24/100.

Make 1800contacts.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 a verdict.

Does 1800contacts.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 Custom

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

Is Custom ready for AI agents?