AI assistant for your API reference
The parameter, the example, and the page it lives on
A developer knows the shape of what they want and not the name you gave it. Search needs the name; an assistant takes the description and returns the endpoint, with the page it came from.
Your reference is generated, complete and organised by resource. The question is how to paginate, the answer is one sentence on a shared conventions page, and the developer finds it after five tabs or after asking in your community.
- The API reference, crawled or pushed from CI
- OpenAPI descriptions
- SDK readmes and code samples
- Changelogs and migration guides
What it does
Reads what you already generate
OpenAPI descriptions, SDK readmes and the changelog are documents like any other, pushed from CI whenever you publish.
Answers with the endpoint
The reply names the route and the field and cites the page, which is what a developer verifies before writing the call.
One knowledge base per version
A question about v2 is not answered from v1, because they were never in the same knowledge base.
Questions people ask
Will it write code that does not work?
It answers from your reference and cites it. Where the reference does not cover something, it says so rather than inventing a parameter.
Can we push docs from CI?
Yes. The REST ingest endpoint takes a document per page keyed by your own id, so a rebuild updates instead of duplicating.
Can we keep an internal-only version?
Yes. A separate knowledge base and a separate widget, restricted to the domains you allow.
Connect it to
Upload your documents, get answers that cite them
One knowledge base, an AI chat or an Ask AI search on any site, and every answer with the passage it came from. Free for 14 days.