API access · Alebex
Models / API access

API access

Call the models directly, the way you would call any other model provider.

Open REST and WebSocket APIs, plus a CLI. Voice sessions, streaming and call control — the three things the platform itself is built on.

The surface
Base URL api.alebex.ai/v1
Authentication Authorization: Bearer
Interfaces REST · WebSocket · CLI

Illustrative until the reference is issued with your account.

On this page Interfaces Authentication Call control What you can address
Interfaces

REST manages, the socket streams, the CLI tests

REST places and manages calls, configures agents and pulls transcripts. The WebSocket carries audio for live sessions. The CLI covers test calls, session replays and experiments.

REST
Place and manage calls, configure agents, pull transcripts.
WebSocket
Audio streaming for live sessions.
CLI
Test calls, session replays, experiments.
Hands on a mechanical keyboard with a terminal on screen, dark desk, cool light
Authentication

One bearer token

Keys are issued from the dashboard and are server-side only.

The key never belongs in a browser bundle. A browser is given a short-lived session URL by your own backend, and the session URL is what it opens.

Authentication cURLTypeScriptPython Copy Illustrative 
# Every request carries the key as a bearer token. Keys are issued from the# dashboard when the account is created, and they are server-side only.export ALEBEX_API_KEY="..." curl https://api.alebex.ai/v1/models \  --header "Authorization: Bearer $ALEBEX_API_KEY"

Shell request with cURL. Illustrative sample. Endpoint paths, parameter names and field names are confirmed in the documentation issued with your account.

Call control

Place a call, pull the transcript

Placing and managing calls, configuring agents and pulling transcripts are all REST. There is no separate surface for the API customer.

REST Copy Illustrative 
# REST places and manages calls.# 555-01xx is the reserved fictional range.curl https://api.alebex.ai/v1/calls \  --header "Authorization: Bearer $ALEBEX_API_KEY" \  --header "Content-Type: application/json" \  --data '{ "to": "+16045550142", "agent": "agt_..." }' # Pull the transcript once the call has ended.curl https://api.alebex.ai/v1/calls/cal_.../transcript \  --header "Authorization: Bearer $ALEBEX_API_KEY"

Shell request with cURL. Illustrative sample. Endpoint paths, parameter names and field names are confirmed in the documentation issued with your account.

The CLI reaches the same two operations without a client to write first, and it is where test calls, session replays and experiments live.

CLI Copy Illustrative 
# The same call, without writing a client first.alebex calls create --to "+16045550142" --agent agt_... # Replay a session locally, frame by frame,# against a change you are testing.alebex sessions replay ses_...

Shell session. Illustrative sample. Endpoint paths, parameter names and field names are confirmed in the documentation issued with your account.

The surface

What you can address today

One of the three is addressed by a model id. The other two are reached differently, or not yet at all — which is the thing a client library has to know before anything else.

ModelModel idInterfacesAudio
Alebex Voice Engine  ·  the runtime—REST · WebSocket · CLI—
Speech-to-text  ·  ships firstalebex-asrREST · WebSocketpcm_s16le · mulaw
Text-to-speech  ·  coming soon———

Only speech-to-text is addressed by a model id today. The engine is reached as calls and sessions rather than as a model, and text-to-speech has no standalone surface to call yet — it runs inside the platform.

Models pricing Coming soon

Model pricing is coming soon.

No rates are published on the site yet. Model pricing is listed in the navigation and carries the coming-soon mark until go-to-market pricing is established.