Providers overview

Every provider Syrinx ships is a thin adapter over one of three shared streaming-lifecycle modules. The module owns the socket, reconnect, the interim/final funnel, and usage billing; the provider implements only its wire protocol. That’s what makes swapping a vendor a one-line change instead of a rewrite.

Module	Owns	A provider implements
@kuralle-syrinx/stt-core	Socket, reconnect, the interim/final transcript funnel, usage.recorded audio-second billing, pre-handshake audio buffering, reconfigure/reset	An SttWireProtocol: encodeFinalize, decode, and optional encodeAudio / onOpen / encodeReconfigure
@kuralle-syrinx/tts-core	The multi-context streaming lifecycle, attribution, usage.recorded character billing	A WireProtocol: attribution plus encode text/finish/cancel and decode
@kuralle-syrinx/realtime	The RealtimeBridge plugin, capability negotiation, resume	A RealtimeAdapter: sendAudio / sendText / requestResponse / cancelResponse, tools, events

Pick a provider

• STT providers — Deepgram (Nova and Flux), ElevenLabs, Google, Grok.
• TTS providers — Cartesia, ElevenLabs, Deepgram Aura, Gemini, Grok, and any OpenAI-compatible endpoint.
• Realtime providers — OpenAI Realtime, Gemini Live, and Grok’s realtime API.

Socket factories

Every provider plugin opens its own WebSocket to the vendor through an injectable socket factory — that’s what lets the same plugin run on Node and on the Cloudflare Workers edge. The plugin constructor takes it as an optional argument:

import { createNodeWsSocket } from '@kuralle-syrinx/ws/node';       // Node
import { createWorkersSocket } from '@kuralle-syrinx/ws/workers';   // Cloudflare Workers

new DeepgramSTTPlugin();                     // Node — uses the default Node socket factory
new DeepgramSTTPlugin(createNodeWsSocket);   // Node — the same thing, explicit
new DeepgramSTTPlugin(createWorkersSocket);  // Cloudflare Workers

On Node you can omit it — the plugin defaults to a Node WebSocket. On Cloudflare Workers, pass createWorkersSocket (from @kuralle-syrinx/ws/workers), which dials out over the Workers fetch-upgrade path. Nothing else in your code changes. This applies to every STT, TTS, and realtime provider.

Mid-call reconfigure

Some STT providers let you bias recognition — keyterms, end-of-turn thresholds, language — without tearing down the session. See STT reconfigure.

Usage and pricing

Every STT, TTS, and LLM provider emits a usage.recorded packet (STT audio-seconds, TTS characters, LLM tokens). Turn that into a running dollar cost, or bound it with a spend cap — see Usage & pricing.