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 hoka.com ready for AI agents?

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

25%

Readiness

1/4

Verified (readable)

Custom

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

0/18 AI crawlers reached the homepage18 blocked

Ranks above 45% of 129 sites checkedcorpus avg 24/100

Not agent-ready

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

Assessment

1 of 4 readable agent-readiness checks verified (5 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 /.well-known/mcp (403), /mcp (403), /.well-known/ucp (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

Anpcould not read /.well-known/agent-descriptions (403) - the site refused our request, so this is not a findingCould not read

Ucpcould not read /.well-known/ucp (403) - the site refused our request, so this is not a findingCould not read

Ap2could not read /.well-known/ucp (403) - the site refused our request, so this is not a findingCould not read

Openapino /openapi.json, /api/openapi.json, or /.well-known/openapi.jsonNot found

Llms Txtno /llms.txtNot found

WikidataWikidata entity Q16908664 (Hoka)Verified

.well-known files

.well-known/mcp.jsonnot found410

Mcp Well Known Altcould not read403

/mcp endpointcould not read403

Ai Plugin Legacynot found410

.well-known/agent.jsonnot found410

.well-known/agent-card.jsonnot found410

Anp Discoverycould not read403

Anp Didnot found410

Openapi Well Knownnot found410

Openapi Rootnot found410

Openapi Apinot found410

Ucp Profilecould not read403

Llms Txtnot found410

Llms Full Txtnot found410

robots.txt9987 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, 0 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 hoka.com

On hoka.com (Custom), 1 of 4 readable agent standards are in place: Wikidata. Missing: A2a, Openapi, Llms Txt.

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

hoka.com scores higher than 45% of the 129 sites checked here so far; the average readiness score is 24/100.

Make hoka.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 hoka.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 67 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?