ElevenLabs 上线 OpenRouter：9 个 TTS 与 2 个 STT 模型

Blog; /; Announcements; /; ElevenLabs is now on OpenRouter

On this page

Which model to use; Walkthrough: from a first MP3 to a voice agent; Tips for your first requests; Getting started

Sasha Blumenfeld ·10/7/2026

ElevenLabs is now on OpenRouter with nine Text to Speech models and two Speech to Text models.

If your app already talks to a language model through OpenRouter, it can now speak and listen too. Narrate long-form content with direction over tone and delivery with Eleven v4, give your agent faster spoken replies with v4 Turbo, or transcribe conversations with speaker labels with Scribe v2. You don’t need a separate ElevenLabs plan. Just call POST /api/v1/audio/speech and POST /api/v1/audio/transcriptions with your OpenRouter API key.

Which model to use

Start with three models and reach for the rest when a job needs them:

Narration, characters, product videos: Eleven v4. Audio tags let the script carry the performance; Voice agents and live replies: Eleven v4 Turbo, ElevenLabs built it for real-time use, at half the v4 rate; Transcripts, meeting notes, captions: Scribe v2, with speaker labels and word timestamps

Use Multilingual v2 when long-form audio needs speed control, and Flash v2.5 for high-volume speech of up to 40,000 characters per request. Scribe v2 Medical is fine-tuned for medical terms.

Text to Speech

ElevenLabs prices its models in two tiers. Eleven v4, v3, and Multilingual v2 bill the full per-character rate, and v4 Turbo, v3 Conversational, Flash, and Turbo bill half of it. Current per-character prices are on each model page in the Text to Speech collection.

Speech to Text

Both Scribe models use the same request shape and the same per-second price. Realtime Scribe v2 over WebSocket isn’t part of this launch.

Walkthrough: from a first MP3 to a voice agent

We’ll build a small product tour in three steps. First Eleven v4 narrates it. Then a voice agent answers questions about it, and finally Scribe v2 turns the team’s review meeting into notes that show who said what. If a request doesn’t behave the way you expect, check the tips at the end.

Set your key once:

Step 1: Narrate a product tour with Eleven v4

Start with one line of narration:

voice takes any of ElevenLabs’ 21 premade voices by name (george here); names aren’t case-sensitive. Note the explicit response_format — see Tips for your first requests for both.

The bracketed words are audio tags. Eleven v4 and v3 read tags such as [whispering], [laughing], [sighs], and [curious] as delivery directions instead of speaking them. Tags count toward your billed characters.

A full tour script is longer than one request allows (10,000 characters on v4, 5,000 on v3), so split it on paragraph boundaries. ElevenLabs-only settings go under provider.options.elevenlabs. Pass the neighbouring text as previous_text and next_text so intonation stays consistent across the joins, and fix a seed so reruns are more repeatable:

Step 2: Answer questions with a voice agent

Now let users ask the tour questions out loud. A voice agent chains three models: Scribe v2 for the question, a chat model for the answer, and Eleven v4 Turbo for the reply. ElevenLabs builds v4 Turbo for real-time use, and it bills at half the v4 rate.

The transcription response is JSON with the transcript in text and a usage object that reports the audio seconds and the dollar cost of the request. Swap openai/gpt-5-mini for any chat model in the catalog without touching the audio calls, and keep the same voice so the agent sounds like the narrator from step 1.

Step 3: Turn the review meeting into speaker-labelled notes

When your team meets to review the tour, Scribe v2 can tell you who said what. Upload the recording as multipart, ask for verbose_json with word timestamps, and set diarize under provider.options.elevenlabs. Every word in the response then carries a speaker. If you know how many people were in the meeting, pass num_speakers to improve the split.

Each entry in words has word, start, end, confidence, speaker (an integer), and speaker_label (speaker_0, speaker_1, and so on). tag_audio_events adds entries such as (laughter) alongside the words. Group consecutive words by speaker to get turns, then send the turns to a chat model for a summary and action items:

Uploads are capped at 25 MB, which covers about 27 minutes of 128 kbps MP3.

For longer recordings, pass a public URL and ElevenLabs downloads the file directly, so the 25 MB cap doesn’t apply:

Very long files can still hit the 180-second upstream request timeout, so split recordings that run long.

Tips for your first requests

Pick a voice by name or ID. For voice, pass any of ElevenLabs’ 21 premade voices by name: george, sarah, adam, alice, bella, brian, charlie, daniel, jessica, roger, will and more (full list on each model page). Names aren’t case-sensitive. To use any other voice, pass its ElevenLabs voice ID as voice — copy it from the ElevenLabs voice library. Voices you clone or design live in your own ElevenLabs account, so use those with BYOK; Ask for mp3 when you want a file you can play If you leave out response_format, our speech endpoint returns raw PCM (16-bit little-endian mono at 24 kHz). That suits an audio pipeline, but most players can’t open it. Set "response_format": "mp3" to get a playable 44.1 kHz, 128 kbps file; Use Multilingual v2 or Flash for speed control Multilingual v2 and Flash take speed from 0.7 to 1.2. Eleven v4 and v4 Turbo have no speed control and reject a non-default speed, so leave it out on those models and change the pacing with audio tags instead; Split long scripts Each model has a per-request character limit (see the model table). Audio tags count toward the limit and toward your billed characters. Split on paragraph boundaries as in step 1, and pass previous_text and next_text so the joins sound natural; ElevenLabs-specific settings go under provider.options.elevenlabs Text to Speech accepts seed, previous_text, next_text, language_code, apply_text_normalization, apply_language_text_normalization, pronunciation_dictionary_locators, voice_settings (stability, similarity_boost, style, use_speaker_boost, speed), and output_format (an ElevenLabs format name such as mp3_22050_32 or pcm_16000; it must match your response_format codec). Speech to Text accepts diarize, num_speakers, diarization_threshold, tag_audio_events, no_verbatim, and seed. num_speakers and diarization_threshold need diarize: true, and you can set one or the other, not both. Use the field names exactly as listed. Keys that aren’t on these lists are ignored; a listed key with a bad value returns a 400; Scribe returns three-letter language codes You can send a two-letter language hint (en). The detected language comes back as an ISO 639-3 code (eng)

Getting started

Create an OpenRouter API key; Make your first request with the curl example in Step 1 above; For every parameter, see the Text to Speech and Speech to Text guides

Text to Speech is billed per character of input, counted as Unicode code points, so an emoji or a CJK character counts once. Audio tags count as characters. Scribe is billed per second of audio, and the usage.cost field on every transcription response tells you what that request cost. We pass through ElevenLabs pricing without markup; see each model page for the current rate.

Already have an ElevenLabs account?

Add your key with BYOK to use your own cloned voices, pronunciation dictionaries, and higher-quality formats such as mp3_44100_192.

Create an OpenRouter API key, or try a model first in the Playground. The Text to Speech and Speech to Text guides have the full request reference.

Related posts

Model Router BenchmarksAnnouncements·Oct 2, 2026; Manage and de-risk your API keys with new Security CenterAnnouncements·Sep 28, 2026; Batch API: half-price inference by bundling requestsAnnouncements·Sep 22, 2026