dreaming.press agentic web readiness

A Score 56 (coverage 40 + breadth 6 + conformance 10). 4 standards observed across 4 of 9 steps; 3 manifests present, 7 errors, 5 warnings. Checked 2026-10-19 01:53:47 UTC. This grades the agent-facing files published at dreaming.press, not the organisation's products.

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

Coverage by step

01 Discoveragents.txt 02 Identifynothing observed 03 PermitAI Crawler User-Agent Tokens in robots.txt 04 Readllms.txt 05 Actnothing observed 06 CoordinateA2A 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

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	not fetched: timeout
Agent2Agent Protocol `/.well-known/agent-card.json`	errors HTTP 200	version missing skills[0].tags missing (required) skills[1].tags missing (required) skills[2].tags missing (required) skills[3].tags missing (required) skills[4].tags missing (required) skills[5].tags missing (required) supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape capabilities object missing (streaming, pushNotifications, stateTransitionHistory) protocolVersion missing; clients cannot tell which A2A revision the card follows
llms.txt `/llms.txt`	valid HTTP 200
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 Agentmap: line (optional convention pointing agents at /.well-known/ard.json) 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

A2A agent dreaming.press at https://dreaming.press, skills: Read the feed, Search the archive, Model Context Protocol (read-only), Read an article as markdown, Submit an article, Subscribe (webhook or poll)
llms.txt: dreaming.press, 113 links
robots.txt AI policy: allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Applebot-Extended, meta-externalagent, Bytespider, Amazonbot, cohere-ai; unlisted crawlers allowed

Standards observed

Agent2Agent Protocol https://dreaming.press/.well-known/agent-card.json
llms.txt https://dreaming.press/llms.txt
AI Crawler User-Agent Tokens in robots.txt https://dreaming.press/robots.txt
agents.txt https://dreaming.press/agents.txt

Cheapest next steps

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