> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.rydhm.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.rydhm.ai/_mcp/server.

# Rydhm Engine

The Rydhm Engine is how other apps, and the AI coding agents that build them, use Rydhm from the inside. It powers two products:

#### [Onboarding coach](/engine/onboarding-coach)

A voice expert inside your web app. It knows which page your user is on, points at buttons, fills fields, runs guides and announces what's new.

#### [Rep calls](/engine/rep-calls)

Your sales reps call prospects from the browser. Rydhm transcribes both sides, suggests the next question, leaves the voicemail and routes callbacks.

> **Note**
>
> The Rydhm Engine is in **preview**: the Onboarding coach and rep calls are live for early-access workspaces on staging, and small changes are still possible before launch. In the app, the coach is a kind of expert (**Experts**), and rep calls live under **Sales calls**.

## What you need

Three kinds of credentials, each for one place:

| Credential          | Looks like        | Where it lives  | What it can do                                                                                                                                                                                                              |
| ------------------- | ----------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Publishable key** | `rydhm_pk_live_…` | Your web page   | Start a conversation with **one** expert and report what the user did, only from the websites you allow. Public by design.                                                                                                  |
| **Secret API key**  | `rydhm_live_…`    | Your server     | Everything its [scopes](/developers/scopes) allow: set up guides and the page map (`experts:write`), read analytics (`experts:read`), place and follow rep calls (`calls:write`, `calls:read`). Never put it in a web page. |
| **Softphone token** | A LiveKit token   | A rep's browser | Keep one rep online for 12 hours, take their callbacks, and hang up or decline their own calls. Your server mints it with the secret key.                                                                                   |

The browser SDK, [`@rydhm/web`](/developers/sdk-web), uses the publishable key and softphone tokens. The server SDKs, [`@rydhm/sdk`](/developers/sdk-typescript) and [`rydhm`](/developers/sdk-python), use the secret key.

> **Note**
>
> **Rydhm is in early access.** Until launch, workspaces on `staging.rydhm.ai` use `https://api-staging.rydhm.ai` in place of `https://api.rydhm.ai`. Pass it to the SDKs as `apiUrl` (`@rydhm/web`), `baseUrl` (`@rydhm/sdk`) or `base_url` (`rydhm`).

## One event shape everywhere

Everything that happens, a transcript line on a call, a guide step done, a callback ringing, is the same JSON event wherever you receive it: on a [Server-Sent Events](/engine/rep-calls#follow-the-call) stream from the API, in the browser (the SDK's events), and, for the most important ones, as a [webhook](/developers/webhooks#rep-calls-and-the-onboarding-coach).

```json
{
  "id": "evt_01JC2M3W8N4P6R9S3T5V7W9YA",
  "type": "call.transcript",
  "callId": "4b5c6d7e-8f90-4a1b-9c2d-3e4f5a6b7c8d",
  "at": "2026-11-11T15:02:14.120Z",
  "data": { "speaker": "prospect", "text": "Sure, I have a minute.", "final": true, "startMs": 5120 }
}
```

| Field                 | What it is                                                                                                                       |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `id`                  | Unique. Dedupe on it: a reconnected stream can send an event again, and the SDKs drop the repeat for you.                        |
| `type`                | What happened: `call.*` for rep calls, `guide.*`, `announcement.*`, `tool.called` and `target.missing` for the Onboarding coach. |
| `callId`, `sessionId` | The rep call, or the coach's conversation, it belongs to.                                                                        |
| `at`                  | When it happened (ISO 8601).                                                                                                     |
| `data`                | The details, different for each type. The SDKs type it for you.                                                                  |

## Where to start

* **Not a developer?** [Set up the Onboarding coach without code](/engine/onboarding-coach): a script tag, then everything else in the app.
* **Building an onboarding experience?** [Set it up with code](/engine/onboarding-coach-code), then read the [client tool protocol and safety guarantees](/engine/client-tools).
* **Building a dialer or an SDR app?** Start with [Rep calls](/engine/rep-calls), then the [browser softphone](/engine/softphone).
* **Want the reference?** [Browser SDK](/developers/sdk-web), [TypeScript SDK](/developers/sdk-typescript), [Python SDK](/developers/sdk-python).