Agent Surface Auditor checks to ensure your site is ready for Agents Scans visit (must be)

Most discussions about "optimizing for agents" still sound too abstract. In practice, agent-facing failures are usually plain engineering problems: one machine-readable document links to one canonical path another links to an older or duplicated public path your sitemap forgets the important execution docs your OpenAPI file is reachable, but buried behind inconsistent references your best instructions are written for humans, not for machine execution That is why we built a standalone Agent Surface Auditor . It checks: discovery files like robots.txt , sitemap.xml , llms.txt , and llms-full.txt project-specific docs defined by config, such as execution docs or OpenAPI files execution surfaces for MCP, API docs, OpenAPI, or CLI content quality signals including heading structure, readability, and semantic HTML canonical drift between repo state and public output One thing we learned quickly: the interesting issues are rarely exotic. They are usually: stale public links multiple canonical