RAG answers with source citations

Every answer Kelu generates includes links back to the exact source — policy page, runbook, wiki article, or ticket. Teams and customers verify, click through, and trust.

What powers every answer

A production-grade RAG stack you do not have to build yourself

Smart retrieval

RAG Pipeline

  • LLM query rewrite and expansion before retrieval
  • Semantic vector search with embedding model
  • BM25 keyword matching for precision
  • Reciprocal rank fusion for result merging
  • Cross-encoder re-ranking for top result quality
  • Multi-collection queries across sources
Citation-first

Answer Quality

  • Inline source citations on every answer
  • Direct links to exact doc page and anchor
  • Suggested questions and related articles
  • Confidence scoring and low-confidence fallback
  • Hallucination prevention via grounding checks
  • Structured output for code and tables
Context-aware

Conversation

  • Multi-turn conversation memory
  • Pronoun and reference resolution
  • Session persistence across widget reloads
  • Suggested follow-up questions after each answer
  • Clear conversation and start over
  • Shareable conversation links
Surface answers anywhere

One RAG pipeline, every channel

The same AI Chat engine powers your embeddable support widget, your Slack bot, your Teams integration, your employee portal, and your Chat API. Update a knowledge source and every channel reflects the change within minutes.

  • Embeddable widget with full style override support
  • React component for deeper integration
  • JavaScript SDK for custom UI builds
  • POST /chat API for server-side or mobile callers
  • Slack, Discord, and Teams bots with citation links
POST /v1/chat
REQUEST
{
  "knowledge_base_id": "kb_abc123",
  "question": "How do I rate-limit the API?",
  "session_id": "sess_xyz"
}
RESPONSE
{
  "answer": "Use the X-RateLimit-* headers...",
  "citations": [
    {
      "title": "Rate Limiting Guide",
      "url": "https://docs.example.com/rate-limits",
      "excerpt": "All API calls are subject to..."
    }
  ],
  "confidence": 0.94
}
What teams say

Deployed in production, cited by the buyers who chose it

Deployed on our docs site in an afternoon. Every answer has citations, and the abstention gate means we've never had a customer complain about a made-up answer.
PN
Priya Nair
Head of Customer Support · Supabase
The knowledge base connected to our Slack, Confluence, and helpdesk in one setup. On-call teams get the same cited answer whether they ask in chat, in the widget, or from Cursor.
TR
Tom Richter
IT Operations Manager · Grafana Labs
The gap analytics turned into a real docs backlog. Deflection went up because we finally knew which pages were missing — the AI told us.
AC
Ana Castillo
VP of Customer Experience · Clerk

Frequently Asked Questions

Common questions about Kelu AI Chat

Kelu uses best-in-class models from Anthropic and OpenAI depending on the task. The retrieval and reranking layer is model-agnostic. Enterprise customers can bring their own LLM endpoint.
After retrieval, each source chunk is tracked with its URL and page title. The LLM is prompted to cite sources inline. The final response JSON includes a structured citations array with URL, title, and excerpt for each source used.
When retrieval confidence is below the threshold, Kelu returns a transparent fallback message rather than hallucinating. You configure the fallback text — typically pointing users to a support channel.
Yes. The Chat API supports server-sent events (SSE) streaming. The widget uses streaming by default for a fast perceived response time.
Each session_id maps to a conversation context window. Kelu summarizes older turns to stay within the LLM context limit. Sessions expire after 24 hours of inactivity.

Ship AI chat on your knowledge today

Connect a knowledge source and embed the widget in under 5 minutes.

Get Started Free