Use case · Developer and API docs
Your API reference, answering questions
Developers know what they want to do, not what you called the endpoint. PageTruth reads your API reference, guides and SDK docs and answers with the exact section — including the request example and the error codes.
The problem
Reference docs are complete and impossible to search
Your OpenAPI reference documents every field. An engineer still spends twenty minutes finding out which one controls idempotency, then asks in your community channel.
How PageTruth handles it
What changes
⌘K from any docs page
The centered search layout matches how developers already navigate docs: one shortcut, type, answer.
Code stays code
Answers keep code blocks, parameter names and status codes intact, and cite the reference section they came from.
Versioned knowledge
Keep one knowledge base per API version, or tag sources into collections, so v1 answers never leak into v2.
What to put in the knowledge base
- API reference (import by URL or sitemap)
- SDK READMEs and guides
- Changelogs and migration guides
- Error code tables
What to watch in insights
- Endpoints asked about
- Which parts of the API generate the most questions.
- Missing examples
- Questions where the reference had no example to cite.
- Version confusion
- Questions answered from a deprecated guide, so you know what to retire.
Other ways teams use it
- Support deflectionAnswer the repeat questions before they become tickets, and hand the rest to your team with context.
- In-app onboarding helpA side panel inside your product that explains the screen a new user is stuck on.
- Implementation and customer successGive B2B customers a private knowledge base for their rollout: runbooks, SOWs and training notes.
Give your customers answers, not a ticket number
Point PageTruth at your docs, publish a help center and drop the widget into your app. The free plan is enough to see it answer your own questions.