Drop a chat
on any site. One line.
Issue a share token. Paste the script tag. Your customers can ask questions; the agent answers with citations from the bucket you connect — never the raw bytes.
Paste it. Ship it.
The widget loads defer, code-split into a ~9 KB gzipped bundle, and never blocks your render path.
<script src="https://embed.kraterion.com/v1.js"
data-token="kr_share_test_..."
data-theme="light"
data-position="bottom-right"
defer></script>Public tokens you can rotate.
Every share token is scoped to one agent, one bucket, one origin allowlist, and a daily request cap. Tokens use the kr_share_test_ / kr_share_live_ prefix — distinct from your bearer keys so the auth guard can route them separately.
Tokens only work from origins you allow-list. Stolen tokens fail elsewhere.
Public tokens can read cited answers — never your raw files. Only the agent's response ships.
Cap requests per minute, per day, per token. Predictable cost ceilings, abuse-resistant by design.
Allowed. Capped. Visible.
Each token's policy is editable from the dashboard and visible in your audit log. Rotate any time without redeploying — the script tag stays the same, you swap the token value.
See it on a real-shape page.
Theme it. Position it. Watch it sit on a real-shape page — same layout your customers will see. Theme and placement are token-level settings; rotate the token and the widget reconfigures without a redeploy.
Getting started with the Acme API.
Welcome to Acme. This guide walks you through authenticating, making your first request, and handling rate-limited responses gracefully. Pick a language tab below.
The bytes never leave your bucket.
Only the cited answer ships.
Chat on your site.
One script tag.
Origin-locked share tokens. Per-token rate limits. Cited answers, never raw files.