Self-serve. Sign up, take a key, and call the models directly.
A developer account is one of the three ways in. Partners white-label the platform; businesses run agents on it. Same runtime underneath.
The posture is the point: you can sign up and build on Alebex without talking to anyone first. The same runtime that serves the agent platform serves the API.
Four steps, and none of them is a sales conversation.
The dashboard issues the key when the account is created. There is no request to make and nobody to ask. It belongs in your own server’s environment and nowhere else.
Shell session. Illustrative sample. Endpoint paths, parameter names and field names are confirmed in the documentation issued with your account.
A browser never holds it. Your own backend mints a short-lived session URL, and the session URL is what the browser opens — so a key is never shipped in a bundle you serve to the public.
Developer accounts are the starting motion. API access is the reference for the surface itself — the authentication block in cURL, TypeScript and Python, the three interfaces, and call control.
Model pricing is not published yet. It is listed in the navigation and marked coming soon until go-to-market pricing is established.
| Layer | What it prices | Rate |
|---|---|---|
| 01 Platform | For teams running the agent platform in their business. | Not published |
| 02 Agents | For agents deployed across voice, SMS and email. | Not published |
| 03 Models · coming soon | For the models called directly over the API. | Coming soon |