Read the workspace, then act when grounded.

KiBee is a workspace intelligence layer. It learns your product — language, paths, documents, outcomes, and friction — and can answer, hand off, or finish a step on screen when that knowledge is grounded. Flying to a control is one command, not the product.

How It Works

KiBee works with any SaaS product regardless of framework. The integration pattern is the same everywhere:

  1. Add data-kibee-id attributes to the UI elements you want guided
  2. Initialize the SDK with your API key
  3. Define flows — sequences of steps that guide users through your product
  4. KiBee learns those controls, answers from workspace memory, and can finish a step on screen when grounded
Your SaaS (any framework)
<!-- Step 1: Add data-kibee-id to your controls -->
<input data-kibee-id="company-name" placeholder="Company name" />
<button data-kibee-id="invite-team">Invite team</button>
<button data-kibee-id="launch">Launch workspace</button>
SDK Initialization
import { KiBeeClient } from "@kibee/sdk";
import { ThreeBeeRenderer } from "@kibee/renderer-three";

const kibee = new KiBeeClient({
  renderer: new ThreeBeeRenderer({ dockPosition: "bottom-right" }),
  apiBaseUrl: "https://api.kibee.ai",
});

kibee.init();
kibee.identifyPage("onboarding");
kibee.registerTargets([
  { id: "company-name", label: "Company name", target: { kibeeId: "company-name" } },
  { id: "invite-team", label: "Invite team", target: { kibeeId: "invite-team" } },
  { id: "launch", label: "Launch workspace", target: { kibeeId: "launch" } },
]);

That's it. KiBee now knows those controls as part of workspace memory. A later ask can match them. When a grounded flow runs, the bee can act on a target, speak, or wait for the real action — flying is one of those steps.