API layer access · Alebex
Canada’s #1 streaming speech-to-text model. Alebex STT recorded a 3.96% word error rate for final transcription on September 21, 2026
Partners / API layer access

Take access at the API layer

Voice sessions, streaming and call control through open REST and WebSocket APIs.

The engine is reachable three ways
REST

Configure agents, tools and webhooks; place phone calls.

WebSocket

Browser calls and streaming speech-to-text.

Webhooks

A signed report of every call when it ends.

REST, WebSocket and signed webhooks, on the same engine as the platform.

On this page What the API reaches into The integration What integrating costs Four innovations What partners build
Partners

What the API reaches into

Quality rides alongside the stream — never in series with it.

Telephony
8 kHz mulaw over media streams
Browser voice
16 kHz PCM

One pipeline serves both, with zero code forks.

Alebex Voice Engine — the stream, in order
01
Audio in
02
Noise reduction
Per frame
03
Voice activity detection
04
Streaming speech-to-text
05
Turn control
Turn end + barge-in
06
LLM
Token stream, gated
07
Streaming text-to-speech
Per sentence
08
Audio out
Interruptible

Alebex Voice Engine — the stream, in order.

Developers

What the integration looks like

REST configures the agent and places the call, a WebSocket carries browser calls, and a signed webhook brings back the result when the call ends.

Agents API 
# List your agents. One Voice API key, kept server-side.curl https://api.alebex.ai/api/v1/public/agents \  --header "Authorization: Bearer $ALEBEX_API_KEY"

Full reference in the developer docs.

Place a call 
# Outbound calls go out on your own Twilio account.# 555-01xx is the reserved fictional range.curl https://api.voice.alebex.ai/public/call/phone \  --header "Authorization: Bearer $ALEBEX_API_KEY" \  --header "Content-Type: application/json" \  --data '{"agentId": "agt_...", "to": "+16045550142",           "twilio": {"accountSid": "AC...", "authToken": "...",                      "phoneNumber": "+16045550100"}}'

Full reference in the developer docs.

Developer workstation with two monitors of code, night, cyan monitor glow
Integration effort

What integrating actually costs you

The cost is effort: the boundary between the application you own and the runtime you do not have to assemble.

You build
Your application and workflow

Build the client-facing application, connect your backend and define the workflow the voice session serves.

You skip
A second voice stack

Do not assemble streaming speech-to-text, turn control, the hallucination gate, barge-in classification, multimodal intent and streaming synthesis from separate layers.

You operate
The client-facing boundary

Operate your application, credentials, client workflow and first-line support.

Alebex operates
The runtime underneath

Alebex operates the voice runtime and Canadian data residency. Recordings, transcripts and customer information are held in Canada. The platform is designed to support PIPEDA, CASL and applicable CRTC requirements, with configurable consent, disclosure, opt-out and retention controls. No certification implied.

Alebex Voice Engine

Four documented innovations

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.

01 Context-aware linear streaming speech-to-text Full-context transcription at linear cost: re-decoding’s coherence at chunking’s price, any turn length.
02 The parallel hallucination gate Latent-space check plus NLU confirmation riding the synthesis window, verdict in ~20ms per check. ~20ms per check Anti-hallucination verdict
03 Barge-in classification A learned classifier on raw audio (WavLM-based) that separates real interruptions from backchannels and line noise in milliseconds.
04 Multimodal intent understanding An LLM decoder that consumes audio and text together and writes the intent label: open vocabulary, dynamic per deployment, capturing the hesitation and tone a transcript flattens.
Alebex Voice Engine
Partners

What partners build on it

A developer ecosystem building custom applications on the platform, with self-serve developer accounts and the models callable directly over the API.

API access →

Voice sessions, streaming and call control through open REST and WebSocket APIs.
Developer accounts →

Self-serve accounts, and the models callable directly.
Alebex Voice Engine →

The runtime everything streams through.
Developers

Build with our API

Voice sessions, streaming and call control through open REST and WebSocket APIs.