# dreaming.press: agentic web grade A

Score 51 (coverage 40 + breadth 6 + conformance 5); 4 standards observed across 4 of 9 steps; checked 2026-10-18T23:45:27Z. This grades the agent-facing files published at dreaming.press, not the organisation's products.

## Manifests

| Manifest | Path | Result | Errors | Warnings |
| --- | --- | --- | --- | --- |
| Agentic Resource Discovery | /.well-known/ard.json | absent |  |  |
| AI Catalog well-known file | /.well-known/ai-catalog.json | absent |  |  |
| MCP Server Cards (SEP-2127) | /.well-known/mcp.json | errors | $schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json); name must be reverse-DNS with exactly one slash, e.g. com.example/weather | Content-Type is application/json; charset=utf-8; SEP-2127 says serve application/mcp-server-card+json; pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[]; description is over 100 characters; remotes missing: a card with no remotes gives clients nothing to connect to; tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key); no Access-Control-Allow-Origin: * (required for browser clients) |
| Agent2Agent Protocol | /.well-known/agent-card.json | errors | 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 |  |  |
| AGENTS.md | /AGENTS.md | absent |  |  |
| api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs | /.well-known/api-catalog | absent |  |  |
| AI Crawler User-Agent Tokens in robots.txt | /robots.txt | valid |  | 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 |  |  |
| auth.md | /auth.md | absent |  |  |

## Standards observed

- Agent2Agent Protocol: https://dreaming.press/.well-known/agent-card.json (https://agenticweb.wiki/protocols/a2a/)
- llms.txt: https://dreaming.press/llms.txt (https://agenticweb.wiki/protocols/llms-txt/)
- AI Crawler User-Agent Tokens in robots.txt: https://dreaming.press/robots.txt (https://agenticweb.wiki/protocols/ai-crawler-tokens-robots/)
- agents.txt: https://dreaming.press/agents.txt (https://agenticweb.wiki/protocols/agents-txt/)

## Cheapest next steps

1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (https://agenticweb.wiki/protocols/ard/)
2. AGENTS.md: instructions for coding agents working on or with the site (https://agenticweb.wiki/protocols/agents-md/)
3. api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (https://agenticweb.wiki/protocols/api-catalog-rfc9727/)

## Rubric

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

JSON: https://agenticweb.wiki/check/dreaming.press/index.json · badge: https://agenticweb.wiki/badge/dreaming.press.svg