Skip to content
OpenKUAI

OpenKUAI

Knowledgeable Agents for Converting Sales

OpenKUAI pairs your sales team with AI agent knowledgeable about your products. OpenKUAI agents and customer data stays inside your intranet.

Explore OpenKUAISignin Dashboard

How it works

One agent per rep

Each rep keeps their own WhatsApp business number; the agent works the 1:1 thread, never a group.

Cited answers, human approval

Replies are grounded in your product knowledge with citations, and a human authorises anything a customer receives.

Self-hosted

Conversations, knowledge and CRM stay on your infrastructure; the WhatsApp relay carries ciphertext only.

Running OpenKUAI?

Open the data-admin console, or read what you need before the first login.

Signin DashboardSignup

Quick Links

Capabilities

1:1 WhatsApp agents, conversation intelligence, knowledge automation, analytics

Products

Kuai KB, the per-rep WhatsApp agent, and the self-hosted stack behind them

Research

Field notes on conversation intelligence, knowledge graphs, and human+agent teams

News

Deploy milestones and engineering briefings from the OpenKuai build

Latest News

All news
2026-09-23
Kuai KB Is Live — Serving the Real Database, Read-Only
The Kuai KB knowledge tier went live, serving the real database read-only behind a review board and audit log; the fetch tier lands sha256-checked records hourly.
2026-09-23
Inside the Enquiry Loop — What We Measured
The 1:1 WhatsApp enquiry loop was measured end to end, webhook to send, on the live channel. The transport is not the bottleneck; the time goes to knowledge-base coverage and model re-asks.
2026-09-18
One Bot per Rep — Why OpenKUAI Is 1:1-Only
OpenKUAI is 1:1-only by design — one agent per rep on the rep's own WhatsApp business number, with group chats out of scope. The 1:1 thread keeps session ownership, privacy and per-rep scoping simple.
FAQEsc Close · Ask OpenKuai

Connect an agent

Copy the prompt below into your agent to access OpenKuai via MCP.

Configure ask.mcpUrl in site.config / instance.config to enable MCP.

After connecting, ask in natural language. Does not support /await, promise responses, elicitation, chatgpt_app, arbitrary extension fields, result actions, or long-term memory.

Other machine-readable resources

  • /llms.txtSite entry map for agents to discover articles, FAQ, and API links
  • /openapi.jsonAPI fields and access notes for programmatic clients
  • Health checkConfirm Ask / MCP is online