You do not need a new wrapper protocol to make the web readable to AI agents. RFC 9110 Section 12 (HTTP Semantics: Content Negotiation) already defines how a single canonical URI serves visual HTML to a human browser and clean, token-efficient Markdown (Accept: text/markdown) to an autonomous agent.
Test proactive content negotiation against this very origin right now:
curl -sI -H "Accept: text/markdown" https://rfc9110.org
Inspect the reference harness installer with less (scroll with j and k, quit with q):
curl -fsSL https://rfc9110.org | less
When you are ready to run the local RFC 9110 verification lab in ~/rfc9110:
curl -fsSL https://rfc9110.org | bash
Accept: text/html) — receive this visual HTML document.Accept: text/markdown) — receive raw Markdown with Vary: Accept, User-Agent and zero DOM boilerplate.curl / wget) — receive the self-documenting Nix flake bootstrap script stamped to rfc9110.The book this grew out of · RFC 9111 Caching · Sun Pug · QA My AI · NPvg · Levinix · GuerillaTech · Pipulate