Unblock developers integrating your API
Answer auth, webhook, and SDK questions with code-aware AI.
Developers evaluating your API get stuck on authentication, webhooks, or an SDK edge case, file a ticket, and stall for a day — or silently abandon the integration. Every stalled integration is delayed or lost revenue.
Kelu ingests your API docs, OpenAPI spec, and GitHub READMEs with code-block-aware normalization, so answers include working snippets with citations. Deploy it on your developer portal as a widget or Cmd+K search, and developers self-serve through integration issues in minutes.
How it works
- 01
Connect your API docs site, OpenAPI spec, and GitHub READMEs as sources.
- 02
Code-block-aware normalization preserves snippets, so answers include working code.
- 03
Deploy on your developer portal as a chat widget, search bar, or Cmd+K modal.
- 04
Developers ask 'how do I authenticate?' and get cited answers combining spec and guides.
What you get
- Unblock integrating developers in minutes instead of a ticket round-trip.
- Answer auth, webhook, and SDK edge cases with cited, code-aware responses.
- Reduce silent abandonment during API evaluation.
- Keep answers synced to your spec and repos via scheduled and webhook-triggered syncs.
Features that make it work
Got questions?
Frequently asked questions
Will answers include actual code snippets?
Yes. The ingestion pipeline extracts and preserves code blocks during HTML→markdown normalization, and chunking is heading- and code-aware, so retrieved context includes runnable snippets with citations to the source page.
Can it answer from our OpenAPI spec directly?
Yes. OpenAPI is a first-class source type — endpoints, parameters, and schemas are indexed and retrieved alongside your guides, so 'which endpoint does X and what auth does it need?' gets a precise answer.
How does it stay current with our API changes?
GitHub sources re-index via webhook on every push, and other sources sync on a schedule — so a shipped API change is reflected in answers after the next sync, not the next docs rewrite.
How long does setup take?
Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and Kelu crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack bot installs in a few clicks. There is no model to fine-tune and no infrastructure to run.
Are answers backed by citations?
Yes. Every answer from your docs includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.
Is my content used to train AI models?
No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, a widget without Kelu branding, and a custom SLA.
Which knowledge sources can I connect?
24 source types: websites, GitHub (docs files, source code, issues, pull requests, discussions), Notion, Confluence, Google Drive, OneDrive, Zendesk (Help Center and solved tickets), Jira, Jira Service Management, Linear, Salesforce Knowledge articles, Salesforce Cases, Discourse, Stack Overflow for Teams, YouTube, OpenAPI specs, S3, curated Q&A, and direct file uploads (PDF, DOCX, XLSX, CSV, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub sources can re-index automatically via webhook on every push.
What happens when the AI is not confident in an answer?
Answers are grounded in your sources. When they do not cover a question, Kelu returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.
Related use cases
Put your docs inside the IDE via MCP
Cursor, Claude, and other MCP clients answer from your docs.
Learn moreFix developer portal search
Hybrid semantic + keyword search that actually finds the page.
Learn moreQ&A over your OpenAPI reference
Ask 'which endpoint updates a subscription?' and get the answer.
Learn moreReady to unblock developers integrating your API?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required