cafe24.com agentic web readiness
B Manifest validity: 100% (1/1 valid, 0 errors, 1 warning) · Surface score 30 (coverage 20 + breadth 0 + conformance 10). 2 standards observed across 2 of 9 steps; 1 manifest present, 0 errors, 1 warning. Checked 2026-10-23 13:27:54 UTC via www.cafe24.com. This grades the agent-facing files published at cafe24.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | absent HTTP 404 | |
AI Catalog well-known file/.well-known/ai-catalog.json | absent HTTP 404 | |
MCP Server Cards (SEP-2127)/mcp/server-card | absent HTTP 404 | |
Agent2Agent Protocol/.well-known/agent-card.json | absent HTTP 404 | |
llms.txt/llms.txt | valid | |
AGENTS.md/AGENTS.md | absent HTTP 404 | |
Agent Skills/.well-known/agent-skills/index.json | absent HTTP 404 | |
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs/.well-known/api-catalog | absent HTTP 404 | |
AI Crawler User-Agent Tokens in robots.txt/robots.txt | soft-404 HTML |
|
security.txt (RFC 9116)/.well-known/security.txt | absent HTTP 404 | |
auth.md/auth.md | absent HTTP 404 | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- llms.txt: Cafe24, 223 links
- OAuth protected resource
https://eckorea24.cafe24api.com/api/mcp, authorization servers: https://eckorea24.cafe24api.com
Standards observed
- llms.txt https://cafe24.com/llms.txt
- OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://cafe24.com/.well-known/oauth-protected-resource
Cheapest next steps
- AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve
- Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
- AGENTS.md: instructions for coding agents working on or with the site
Agent pre-flight & practical readiness
Preferred mode: llms_txt. GET /llms.txt and follow the links it names. That index is the page list an agent should read.
Fetch: GET https://cafe24.com/llms.txt GET /llms.txt and follow its links.
Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 56392, JSON-LD Organization.
AI crawler posture: unspecified · Assistant access: OpenAI unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.
Readiness subscores: reach 0/20, readability 22/30, capabilities 6/35, conformance 10/15, total 38/100, grade C.
How the grade is made
+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.
JSON · Markdown · probe rules