Embed
Create keys, allow your domains, add the assistant to your app and check that it connected, using the Deploy and Integrate pages.
Two pages get an agent into your app. Deploy & access holds the keys and the allowed domains. Integrate gives you the code and tells you what Baseera has seen from your app.
Allow your domains
Only requests from allowed domains can start a session. A request from any other origin is refused with origin_not_allowed.
Open the agent, then Deploy in the sidebar. The page is titled Deploy & access. Scroll to Access (or open Agent settings at the bottom of the sidebar).
Under Allowed domains, write one domain per line, for example app.example.com or localhost:3000. A *. prefix allows every subdomain. You can list up to 50.
Press Save domains. You see "Domains saved."
With no domains, "every request is refused until you add one." If you gave Your product when you created the agent, its address is already here. Add your production domain before you go live.
Create the keys
An agent has two kinds of key.
| Key | Starts with | Goes in | Rules |
|---|---|---|---|
| Publishable key | pk_ | Your app's browser code | Safe in the browser. Works only from the allowed domains. |
| Secret key | sk_ | Your server's environment | Signs user tokens and server calls. Never put one in the browser. |
Under Publishable keys press Create publishable key, optionally name it (for example "Production web app"), and copy it with Copy.
Under Secret keys press Create secret key. The key is shown once ("Copy this key now. It is shown only once."). Copy it, store it in your server's secrets, then press I have saved it.
Each key shows when it was created and last used. Press Revoke to stop a key working. Revoked keys are counted at the bottom of the list. An agent can have up to 20 active keys of each kind.
Developers can create publishable keys. Only owners and admins can create or revoke secret keys. If your organization requires two-factor, you must have entered your code in this session first.
The workspace page API keys lists your agents so you can jump to each one's domains and keys.
Treat a secret key like a password. If it leaks, revoke it and create a new one. Baseera cannot show it to you again.
Development mode
Development mode lets a session start from localhost without a user token. It is for quick starts. Turn Allow sessions without a user token from localhost off before you go live. Sessions started this way show as "Dev mode (anonymous)" and cannot rate replies.
Add the assistant to your app
Open Integrate. Three ways in shows the install steps and copy-ready snippets for each:
- Chat (minutes): a launcher and chat panel that answer from the agent's knowledge.
- Tools (hours): tools you define in code. Every change a tool makes is approved by the user. See Tools.
- Immersive (days): Baseera works inside the record the user is editing, with checks, drafts and a guarded finish.
The snippets use this agent's publishable key. If it has none, they show YOUR_PUBLISHABLE_KEY, and a note tells you to create one in Deploy & access. Secret keys are never shown on this page.
Your server signs a short-lived user token for each signed-in user, with the secret key. See User tokens and the SDK quickstart.
Let your coding agent do it
Under Prompts for your coding agent, press Show prompt and copy Integrate the SDK or Add immersive mode into Claude Code, Cursor or Codex. The prompt is filled with this agent's id, publishable key, domains and tools. It never contains a secret key. The coding agent first surveys your code, lists what it plans to change and asks before any breaking change.
Check that it connected
Integration health reads what Baseera has recorded and updates live. Each line is Ready, Needs attention, Missing or Not seen yet:
| Line | Ready when |
|---|---|
| Publishable key | An active key exists. |
| Allowed domains | At least one domain can start a session. |
| Provider key | The agent's model has an active provider key. |
| Published version | A version is live. |
| App connected | A session from your app has reached Baseera. |
| Signed user tokens | Sessions carried a token your server signed. |
| Language and direction | A session sent its locale. Pass locale when you sign the token. |
| Tool manifest | Your app has sent its tools. |
| Immersive records | A record started in immersive mode. |
| Finish verification (verifyFinish) | Your server verified a finish. |
Baseera does not record the SDK version, the framework or which fields use BaseeraField, so the page does not check them.
While no session has arrived, the tile says Waiting for your app. After three minutes it says Still waiting and lists the likely causes from your settings: no publishable key, your domain not allowed, no provider key on the model, or nothing published.
What can go wrong
| Symptom | Cause and fix |
|---|---|
| The panel cannot reach the assistant | The runtime address in your app is wrong, or your domain is not in Allowed domains. |
| "No domain is allowed" | Add your app's domain, with its port if it has one. |
| Sessions start but all are anonymous | Your server is not signing a user token. See Signed user tokens. |
| "Only localhost works, through dev mode." | No domain is set. Add one. |
| "The assistant has not been set up yet." | The agent has no model or provider key. See Instructions and model. |
| "This agent already has 20 active keys of this kind. Revoke one first." | Revoke keys you no longer use. |
| "Not a valid domain: ..." | Remove the protocol and path. Write only the host and port. |