Skip to main content
The integration is bidirectional. Content flows from the customer’s platform into Kai Brain for analysis. Aggregated emotional signals flow back out to the customer’s dashboard. The connector handles the inbound stream. The plugin renders the outbound signals. All intelligence runs on Kai’s servers — the customer never sees individual data.

​
Data flow

CUSTOMER CONTENT          KAI CONNECTOR              KAI BRAIN                KAI API              DASHBOARD
Slack messages     →    Strips identifiers    →   Mood · States       →   GET /pulse      →   Mood spectrum
WP comments               Assigns uid               Topics · Trends          GET /alerts         State bubbles
Surveys                   POST /ingest              Alert detection                              Topic tags
                                                                                                    Suggested actions

​
Components

Kai connector

Handles the inbound content stream. Pulls content from nominated sources, strips identifiers, assigns pseudonymous uids, and sends batches to POST /ingest.

Kai Brain

Runs on Kai’s servers. Classifies each item for mood, psychological state, topic, and distress score using the same emotional intelligence framework that powers Kai’s AI companion.

Kai API

Exposes ingestion endpoints (POST /ingest) and output endpoints (GET /pulse, GET /alerts) for the plugin to consume.

Dashboard plugin

Renders aggregated signals natively inside the host platform UI. Calls GET /pulse on a configurable schedule.

​
Integration lifecycle

1

Install

Admin installs the Kai connector from the platform marketplace or via manual package. A single API key ties the connector to the organisation’s Kai account.
2

Configure

Admin nominates content sources, sets anonymisation floor, alert thresholds, Kai tone, and signal layers via the admin configuration panel.
3

Ingest

The connector sends text batches to POST /ingest. Raw text is processed in memory and never stored.
4

Render

The dashboard plugin calls GET /pulse and renders mood distribution, psychological states, topic trends, and suggested actions.
Model A (Pulse tier) sends plain text arrays. Model B (Signal/Brain tiers) sends pseudonymous {uid, text, ts} objects so Kai can track per-user trends without holding re-identification keys.