Agent readiness
The files, headers and endpoints that make a site discoverable and usable by AI agents.
The agent readiness checklist: 22 checks for an AI-ready website
Twenty-two checks in six groups, from robots.txt and llms.txt to API catalogs, agent skills and WebMCP. What each one tells an AI agent, which ones every site needs, and which only matter if you run APIs or sell online.Read the postMarkdown for agents: serving Markdown with content negotiation
Agents read Markdown far more cheaply than HTML. Serve a Markdown copy when a request asks for text/markdown, keep HTML the default, and link the copy from every page.Read the postMCP servers for business: when you need one and how to keep it safe
An MCP server exposes your systems to AI agents through one standard interface. It is worth building when agents need to act inside your business, not just read about it.Read the postAgent skills and the ai-catalog: telling agents how to use your site
Agent skills are short instruction files that teach an agent to do one job with your site. A discovery index lists them, and the draft ai-catalog lets registries find them.Read the postAPI catalogs and Link headers: how agents find your APIs
Two small standards tell agents where your APIs are: an HTTP Link header on the homepage, and a well-known api-catalog file that lists each API and its description.Read the postSee how your own site scores
The free agent-readiness scan checks the files, headers and endpoints this blog writes about, and tells you what to fix first.