Your Docs Are Now AI Infrastructure (Treat Them Like It)

Your documentation has three audiences now. Customers reading the docs site. Support agents drafting replies. And AI tools, Cursor, Claude Code, Codex, answering questions about your product on behalf of developers who never visit your site at all. That last one changes everything. The same docs that used to be a static reference are now the grounding layer for every AI feature your developers touch, including ones you didn't build. If your docs are messy, outdated, or missing the answers users actually need, every agent querying them inherits the problem and your product takes the hit. In this lightning talk, we'll show how kapa.ai operates as the knowledge engine behind production AI deployments at companies like Sentry, Netlify, Monday.com, and n8n, processing millions of developer questions per month. We'll walk through real analytics revealing the "dark matter" of documentation like which topics generate the most uncertainty, which pages quietly underperform, and how unanswered questions cluster into a prioritized backlog for content and product teams. The takeaway: stop guessing what to document. Let your users, and the agents querying on their behalf, tell you. With concrete benchmarks: 20-40% support ticket deflection, hundreds of developer-days saved per year, and a path to treating docs as the grounded foundation every AI feature in your product needs.