Skip to content
jibuni

For developers

An answer API, and a chat box that behaves itself

Two ways in: one line of HTML, or a POST that returns an answer with the passages it came from. Both answer from one business's own material and nothing else.

Get a key Free plan · no card · no fee per person

The chat box

One line in the <head>. It renders in a shadow root, so your styles cannot reach it and it cannot reach yours. About 11 KB, no framework, no build step.

<script src="https://jibuni.com/widget.js" data-jibuni="YOUR_BOT_ID" async></script>

If your security review asks

Every release is also published at its own permanent address with an integrity hash, so you can pin one audited file and the browser will refuse to run it if a single character differs — including if our own server is ever tampered with.

<script src="https://jibuni.com/widget-<digest>.js"
        integrity="sha384-…" crossorigin="anonymous" async></script>

It is served under a strict content security policy without needing unsafe-inline, and it never writes HTML — every piece of text goes in as text, so a reply can never become markup on your page.

The Answer API

For your own software: a question in, a grounded answer and its sources out.

curl https://jibuni.com/v1/answer \
  -H "Authorization: Bearer jb_live_…" \
  -H "Content-Type: application/json" \
  -d '{"question": "Ada ya Grade 5 ni ngapi kwa term?"}'

The reply carries the answer, whether it was found at all, and the passages it was built from. A question your material does not answer comes back with found: false rather than something invented — every figure in an answer has to appear in the material or the answer is not sent.

Rules worth knowing before you build

Make a key under Settings once you have an account. Start free.

Put a real answer inside your own software.

Start free — live in minutes. No card, no fee for each person on your team.

Start free

Or read the guides, see what it costs, or look at your own country.