Everything outside the platform UI authenticates with an API key. This page gets you from nothing to a working request.

1. Create a key

Open API keys and choose New key.
The key is shown once, at creation. We store only a hash, so a lost key cannot be recovered — create a replacement and revoke the old one.
Keys look like sk-eesi-… and carry full access to your organization. Treat one like a password: never commit it, never put it in frontend code, and give each deployment its own so you can revoke one without taking down the rest.

2. Find out what your environment serves

Speech tiers are opt-in per environment: a backend with no configured URL is hidden entirely. So ask the API what exists rather than hardcoding a model id that may not be enabled where you are running.

3. Make a request

Pick a tts id from that list and synthesize something.
The speech endpoints speak the OpenAI wire protocol, so the official OpenAI SDKs work unchanged — you only change the base URL. See SDKs for the EESI-specific client that also covers voices, care and usage.

What a failure means

Next

Text to speech

Formats, streaming, speed, and voice selection.

Voices

Clone a voice, and why every voice is a reference clip.

Realtime

Speech-to-speech over a WebSocket.

Authentication

Scopes, rotation, and how keys differ from session tokens.