Making the API Evangelist Network Agent-Readable

I spent last night applying my agent-readiness playbook, first written and applied to apis.io, and now across twenty-two subdomains of the API Evangelist network. The result is end-to-end agent-readable infrastructure built on RFCs rather than vendor conventions, sitting in front of a network of static Jekyll sites that humans browse the same way they always have. This is part of my ongoing work to answer to the question: what does an agent-readable site actually look like, end to end?