Architecture
ORI-Realtime is a system, not a single network. Four layers run as one pipeline:
The API surface follows OpenAI Realtime API event shapes — if you’ve built against a realtime speech API before, the event flow will look familiar. See the WebSocket reference.
Capabilities
- Speech-to-speech conversation with streaming text transcripts of both sides
- Natural interruption — barge-in is handled server-side by the semantic turn engine; just keep streaming microphone audio
- 9 preset voices (plus custom reference support for enterprise) — see voices
- Steerable persona via plain-text instructions in
session.update - Word-level transcript deltas for both user and model speech, with natural spacing
Numbers (preview, honest)
Limitations
Be aware of these before you build:- No client-side
response.cancel. You cannot force-stop a response from the client; interruption happens server-side when the user speaks. This is a deliberate design of the turn engine, but it differs from OpenAI’s Realtime API. - Sessions are ephemeral. If the connection drops, a reconnect starts a fresh session — conversation history is not restored. Keep your own transcript if you need continuity.
- Audio is Opus, not PCM16. Drop-in OpenAI Realtime clients need their audio encode/decode swapped — see audio.
Built in the open
The streaming STT and TTS foundations are open models released by Kyutai (CC BY 4.0); preset voices derive from the CSTR VCTK Corpus (CC BY 4.0). The turn engine, reasoning orchestration, serving stack, and this API are Waterr’s. Full attributions: voice attributions.Quickstart
Key to first conversation in five minutes.
WebSocket reference
Every event, field, and close code.

