Whether the chat UI is the web embed or the React Native SDK, the flow is the same: the widget sends the user’s message to the agent runtime, the runtime plans a single turn (retrieve knowledge, call an action if needed, compose a reply), and the widget renders the streamed reply along with any structured UI.

​
Message lifecycle

The integration surface is messages, sessions, and UI payloads. Internal graph nodes, service routes, and model configuration stay server-side and are managed in the dashboard.

​
Knowledge grounding

Builders manage sources in the dashboard under Sources. Your integration does not need to know which documents exist; answers arrive already grounded.

​
Sessions

Each conversation runs on a session that carries memory across turns, so the agent can ask follow-up questions and fill in missing details without a dialog state machine in your app. The web embed creates an anonymous session per visitor automatically, and the React Native SDK can persist sessions locally. See Messages & sessions.

​
Tenant isolation

Every publishable key maps to exactly one workspace. A widget or app using your key can only reach your workspace’s agent, knowledge, and actions.

Quickstart

First message from your React Native app.

Authentication & identity

Keys and signed-in user identity.