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:
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:
The browser SDK, @rydhm/web, uses the publishable key and softphone tokens. The server SDKs, @rydhm/sdk and rydhm, use the secret key.
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 stream from the API, in the browser (the SDK’s events), and, for the most important ones, as a webhook.
Where to start
- Not a developer? Set up the Onboarding coach without code: a script tag, then everything else in the app.
- Building an onboarding experience? Set it up with code, then read the client tool protocol and safety guarantees.
- Building a dialer or an SDR app? Start with Rep calls, then the browser softphone.
- Want the reference? Browser SDK, TypeScript SDK, Python SDK.