Docs assistants: your documentation has a top-40 chart
Every docs site has the same hit parade — auth, rate limits, pagination, that one confusing endpoint. The assistant answering them should not bill like a consultant.
Instrument any documentation assistant and a leaderboard emerges immediately: a top-40 of questions — authentication setup, rate limits, webhook retries, the endpoint everyone misreads — absorbing the overwhelming share of traffic. The docs are stable; the questions are stable; only the phrasing churns. It's the purest caching workload after support.
Crowkis turns the leaderboard into a free tier of your own: top questions become permanent sub-millisecond hits in every phrasing, gated for confidence so adjacent endpoints never cross-serve. The top-misses analytics view doubles as docs feedback — questions that keep missing are sections your documentation hasn't written yet.
Every paraphrase is a fresh bill — unless the cache understands meaning.
Docs versioning maps directly onto freshness control: pin cache entries to doc versions, invalidate on publish, and let v2 answers die the day v3 ships. The assistant stays exactly as current as the documentation, automatically, which is the entire trust contract of a docs bot.
The bottom line
Developer-experience teams justify budgets with deflection and satisfaction numbers; the dashboard hands you both, plus a savings figure. The top-40 chart was always going to exist — the only question is whether you pay royalties on every play.