agenticresources.dev agentic web readiness

B Score 38 (coverage 20 + breadth 3 + conformance 15). 3 standards observed across 2 of 9 steps; 3 manifests present, 0 errors, 2 warnings. Checked 2026-10-18 23:42:59 UTC. This grades the agent-facing files published at agenticresources.dev, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/agenticresources.dev.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverARD, AI Catalog well-known file 02 Identifynothing observed 03 Permit 04 Readnothing observed 05 Actnothing observed 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	valid HTTP 200
AI Catalog well-known file `/.well-known/ai-catalog.json`	valid HTTP 200
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`	absent HTTP 404
AGENTS.md `/AGENTS.md`	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`	valid HTTP 200	no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (allowed) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404

What an agent can call

robots.txt AI policy: unlisted crawlers allowed; Agentmap https://agenticresources.dev/.well-known/ard.json

Standards observed

Agentic Resource Discovery https://agenticresources.dev/.well-known/ard.json
AI Catalog well-known file https://agenticresources.dev/.well-known/ai-catalog.json
AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

llms.txt: one Markdown index file; the most widely read agent-facing file
AGENTS.md: instructions for coding agents working on or with the site
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description

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). A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. 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