Voice sessions, streaming and call control through open REST and WebSocket APIs.
Quality rides alongside the stream — never in series with it.
One pipeline serves both, with zero code forks.
Alebex Voice Engine — the stream, in order.
REST opens the session and places the call; the socket carries the audio. Both shapes below are the ones the platform itself is built on.
Shell request with cURL. Illustrative sample. Endpoint paths, parameter names and field names are confirmed in the documentation issued with your account.
Shell request with cURL. Illustrative sample. Endpoint paths, parameter names and field names are confirmed in the documentation issued with your account.
The cost is effort: the boundary between the application you own and the runtime you do not have to assemble.
Build the client-facing application, connect your backend and define the workflow the voice session serves.
Do not assemble streaming speech-to-text, turn control, the hallucination gate, barge-in classification, multimodal intent and streaming synthesis from separate layers.
Operate your application, credentials, client workflow and first-line support.
Alebex operates the voice runtime and Canadian data residency. Recordings, transcripts and customer information are held in Canada, with PIPEDA and CASL compliance built in.
Each one is a layer the engine owns rather than assembles, which is why it can sit inside the stream instead of in front of it.
A developer ecosystem building custom applications on the platform, with self-serve developer accounts and the models callable directly over the API.
Voice sessions, streaming and call control through open REST and WebSocket APIs.
Self-serve accounts, and the models callable directly.
The runtime everything streams through.
Voice sessions, streaming and call control through open REST and WebSocket APIs.