ElevenLabs Scribe v2 is the batch speech-recognition model for recorded audio, transcription, subtitling and captioning. It builds on Scribe v1 with improved handling of long recordings, pauses, changes in tone and extended silence. The result is written speech with timing information and optional speaker and audio-event annotations. Scribe v2 Realtime is a separate live-transcription edition; this model’s purpose is processing complete recordings.
The maker documents recognition across more than 90 languages and automatic language detection, including recordings that switch languages. A known language hint can help the model interpret the audio. Prepare a clear recording, retain the original language and names, and avoid severe clipping or unnecessary processing that removes speech detail. Common documented inputs include WAV, MP3, FLAC, M4A, AAC, OGG, Opus and WebM. Choose an input representation supported by the transcription implementation and preserve the source recording for review.
The standard response contains the recognized text, detected language information and a sequence of timed words. Word records can include start and end times, speaker identifiers and a recognition log-probability. These make the result useful for subtitles, searchable interviews or an editor that jumps back to the relevant sound. Keep the timed result with the source audio. For a podcast, for example, the deliverable can be an editable transcript and a word-aligned record that supports locating corrections before arranging captions.
Speaker diarization labels who speaks when in multi-speaker audio, with up to 32 speakers documented by the maker. Enable it when speaker turns are important, and supply a reasonable speaker count if that information is known. Distinguish a detected speaker label from a verified person’s name. For an interview or meeting, review turn changes against the recording, especially where voices overlap or sound similar. A label helps organize the transcript; it does not independently establish the speaker’s identity.
A recording with one speaker per channel has a different structure from several voices mixed into one channel. The producer interface can process up to five channels independently and return separate transcripts or a combined transcript ordered by time, with channel indices. Preserve that channel layout when it is meaningful. Flattening a separated call recording before transcription can discard a useful source of speaker information. Keep channel-based attribution distinct from diarization inferred from mixed audio. The combined-channel response requires timestamps and cannot include entity detection or redaction.
Keyterm prompting guides recognition of names, product terms and specialist vocabulary using context. The current batch documentation allows up to 1,000 terms, with each term kept under 50 characters and at most five words. Provide relevant spellings rather than a broad unrelated catalogue. For a technical interview, supply the product names and abbreviations likely to occur, then inspect them at their timestamps in the result. Keyterms bias recognition; they are not instructions to insert a term when the recording does not support it.
Choose the transcript’s purpose before applying cleanup. A verbatim record retains the spoken wording, while the documented no-verbatim option removes fillers, false starts and disfluencies for a more readable result. Dynamic audio tagging can identify non-speech events such as laughter or footsteps. A polished transcript may be useful for captions or reading, but it should not silently replace the raw record when repetitions, corrections or non-speech sounds are important to the task.
The maker also documents entity detection and experimental transcript editing. Transcript editing cannot be combined with entity detection, entity redaction or multichannel transcription in the producer interface. Detected entities provide structured positions for selected information in the transcript. Optional entity redaction masks detected text with replacement labels; it depends on entity detection, and the entity list is not returned when redaction is enabled. Redaction happens during transcription, using a generic replacement marker, a category label or a numbered category label. Automated redaction can miss sensitive content, so inspect the redacted transcript before sharing it. A natural-language edit returns an edited text alongside the original result, leaving the original timing and speaker record available. Keep those artifacts distinct: a corrected spelling or reformatted sentence may need a renewed check before it is aligned with the audio or used in a downstream extraction. These features process the transcript; they do not establish that every important detail was recognized correctly.
For a finished transcript, review names, numbers, negations and speaker changes by returning to the corresponding audio. Pay attention to quiet sections, overlap and language switches rather than judging quality only from fluent text. Retain uncertain wording for correction instead of completing an inaudible passage with a plausible sentence. The useful result is a checked text record with the timing and speaker information needed for its intended use; a transcript can then become input to a separate summary, translation or analysis step.
", "aboutText": "ElevenLabs Scribe v2 is the batch speech-recognition model for recorded audio, transcription, subtitling and captioning. It builds on Scribe v1 with improved handling of long recordings, pauses, changes in tone and extended silence. The result is written speech with timing information and optional speaker and audio-event annotations. Scribe v2 Realtime is a separate live-transcription edition; this model’s purpose is processing complete recordings.\n\nThe maker documents recognition across more than 90 languages and automatic language detection, including recordings that switch languages. A known language hint can help the model interpret the audio. Prepare a clear recording, retain the original language and names, and avoid severe clipping or unnecessary processing that removes speech detail. Common documented inputs include WAV, MP3, FLAC, M4A, AAC, OGG, Opus and WebM. Choose an input representation supported by the transcription implementation and preserve the source recording for review.\n\nThe standard response contains the recognized text, detected language information and a sequence of timed words. Word records can include start and end times, speaker identifiers and a recognition log-probability. These make the result useful for subtitles, searchable interviews or an editor that jumps back to the relevant sound. Keep the timed result with the source audio. For a podcast, for example, the deliverable can be an editable transcript and a word-aligned record that supports locating corrections before arranging captions.\n\nSpeaker diarization labels who speaks when in multi-speaker audio, with up to 32 speakers documented by the maker. Enable it when speaker turns are important, and supply a reasonable speaker count if that information is known. Distinguish a detected speaker label from a verified person’s name. For an interview or meeting, review turn changes against the recording, especially where voices overlap or sound similar. A label helps organize the transcript; it does not independently establish the speaker’s identity.\n\nA recording with one speaker per channel has a different structure from several voices mixed into one channel. The producer interface can process up to five channels independently and return separate transcripts or a combined transcript ordered by time, with channel indices. Preserve that channel layout when it is meaningful. Flattening a separated call recording before transcription can discard a useful source of speaker information. Keep channel-based attribution distinct from diarization inferred from mixed audio. The combined-channel response requires timestamps and cannot include entity detection or redaction.\n\nKeyterm prompting guides recognition of names, product terms and specialist vocabulary using context. The current batch documentation allows up to 1,000 terms, with each term kept under 50 characters and at most five words. Provide relevant spellings rather than a broad unrelated catalogue. For a technical interview, supply the product names and abbreviations likely to occur, then inspect them at their timestamps in the result. Keyterms bias recognition; they are not instructions to insert a term when the recording does not support it.\n\nChoose the transcript’s purpose before applying cleanup. A verbatim record retains the spoken wording, while the documented no-verbatim option removes fillers, false starts and disfluencies for a more readable result. Dynamic audio tagging can identify non-speech events such as laughter or footsteps. A polished transcript may be useful for captions or reading, but it should not silently replace the raw record when repetitions, corrections or non-speech sounds are important to the task.\n\nThe maker also documents entity detection and experimental transcript editing. Transcript editing cannot be combined with entity detection, entity redaction or multichannel transcription in the producer interface. Detected entities provide structured positions for selected information in the transcript. Optional entity redaction masks detected text with replacement labels; it depends on entity detection, and the entity list is not returned when redaction is enabled. Redaction happens during transcription, using a generic replacement marker, a category label or a numbered category label. Automated redaction can miss sensitive content, so inspect the redacted transcript before sharing it. A natural-language edit returns an edited text alongside the original result, leaving the original timing and speaker record available. Keep those artifacts distinct: a corrected spelling or reformatted sentence may need a renewed check before it is aligned with the audio or used in a downstream extraction. These features process the transcript; they do not establish that every important detail was recognized correctly.\n\nFor a finished transcript, review names, numbers, negations and speaker changes by returning to the corresponding audio. Pay attention to quiet sections, overlap and language switches rather than judging quality only from fluent text. Retain uncertain wording for correction instead of completing an inaudible passage with a plausible sentence. The useful result is a checked text record with the timing and speaker information needed for its intended use; a transcript can then become input to a separate summary, translation or analysis step.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "cb0e5f7588224057ca5e9956593571113383ac548c79670cf283f3d5d3d3709f", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "elevenlabs/scribe-v2ElevenLabs Scribe v2 transcribes recorded audio across 90+ languages, with word-level timing, optional speaker diarization and non-speech event tags. It is built for long-form recordings, captions and editable transcripts, with contextual keyterms and verbatim or cleaned-up transcription choices.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
ElevenLabs Scribe v2 is the batch speech-recognition model for recorded audio, transcription, subtitling and captioning. It builds on Scribe v1 with improved handling of long recordings, pauses, changes in tone and extended silence. The result is written speech with timing information and optional speaker and audio-event annotations. Scribe v2 Realtime is a separate live-transcription edition; this model’s purpose is processing complete recordings.
The maker documents recognition across more than 90 languages and automatic language detection, including recordings that switch languages. A known language hint can help the model interpret the audio. Prepare a clear recording, retain the original language and names, and avoid severe clipping or unnecessary processing that removes speech detail. Common documented inputs include WAV, MP3, FLAC, M4A, AAC, OGG, Opus and WebM. Choose an input representation supported by the transcription implementation and preserve the source recording for review.
The standard response contains the recognized text, detected language information and a sequence of timed words. Word records can include start and end times, speaker identifiers and a recognition log-probability. These make the result useful for subtitles, searchable interviews or an editor that jumps back to the relevant sound. Keep the timed result with the source audio. For a podcast, for example, the deliverable can be an editable transcript and a word-aligned record that supports locating corrections before arranging captions.
Speaker diarization labels who speaks when in multi-speaker audio, with up to 32 speakers documented by the maker. Enable it when speaker turns are important, and supply a reasonable speaker count if that information is known. Distinguish a detected speaker label from a verified person’s name. For an interview or meeting, review turn changes against the recording, especially where voices overlap or sound similar. A label helps organize the transcript; it does not independently establish the speaker’s identity.
A recording with one speaker per channel has a different structure from several voices mixed into one channel. The producer interface can process up to five channels independently and return separate transcripts or a combined transcript ordered by time, with channel indices. Preserve that channel layout when it is meaningful. Flattening a separated call recording before transcription can discard a useful source of speaker information. Keep channel-based attribution distinct from diarization inferred from mixed audio. The combined-channel response requires timestamps and cannot include entity detection or redaction.
Keyterm prompting guides recognition of names, product terms and specialist vocabulary using context. The current batch documentation allows up to 1,000 terms, with each term kept under 50 characters and at most five words. Provide relevant spellings rather than a broad unrelated catalogue. For a technical interview, supply the product names and abbreviations likely to occur, then inspect them at their timestamps in the result. Keyterms bias recognition; they are not instructions to insert a term when the recording does not support it.
Choose the transcript’s purpose before applying cleanup. A verbatim record retains the spoken wording, while the documented no-verbatim option removes fillers, false starts and disfluencies for a more readable result. Dynamic audio tagging can identify non-speech events such as laughter or footsteps. A polished transcript may be useful for captions or reading, but it should not silently replace the raw record when repetitions, corrections or non-speech sounds are important to the task.
The maker also documents entity detection and experimental transcript editing. Transcript editing cannot be combined with entity detection, entity redaction or multichannel transcription in the producer interface. Detected entities provide structured positions for selected information in the transcript. Optional entity redaction masks detected text with replacement labels; it depends on entity detection, and the entity list is not returned when redaction is enabled. Redaction happens during transcription, using a generic replacement marker, a category label or a numbered category label. Automated redaction can miss sensitive content, so inspect the redacted transcript before sharing it. A natural-language edit returns an edited text alongside the original result, leaving the original timing and speaker record available. Keep those artifacts distinct: a corrected spelling or reformatted sentence may need a renewed check before it is aligned with the audio or used in a downstream extraction. These features process the transcript; they do not establish that every important detail was recognized correctly.
For a finished transcript, review names, numbers, negations and speaker changes by returning to the corresponding audio. Pay attention to quiet sections, overlap and language switches rather than judging quality only from fluent text. Retain uncertain wording for correction instead of completing an inaudible passage with a plausible sentence. The useful result is a checked text record with the timing and speaker information needed for its intended use; a transcript can then become input to a separate summary, translation or analysis step.
POST /v1/audio/transcriptionsaudiotext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits elevenlabs/scribe-v2 | Default— |
Fieldinput_audio | Typeobject | RequirementRequired | Values & limits | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, input_audio |
Parametermaterial_types | Contractaudio |
Parametermaterial_conditions | ContractThe example reads your actual nonempty PCM WAV file, encodes the complete file bytes as base64 and sends input_audio.format as wav. |
Lifecycle: synchronous_result_then_owned_library
GET /v1/media/tasks/{task_id} · exact task_id from an existing owned media record
GET /v1/media/assets/{asset_id}/content
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Billing unit | Charge |
|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Billing unit— | Charge Input · Input tokens — / 1K tokens Output · Output tokens — / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
| Configurationinput audio second | Rate schedule— | Billing unitper input audio second | Charge Input · input audio second $0.0001222222222222 per input audio second |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_AUDIO_FILE:?Set the path to your actual PCM WAV recording}"\nexport AILOOT_AUDIO_FILE\npython3 - <<'PY_REQUEST'\nimport base64, io, json, os, wave\nfrom pathlib import Path\naudio = Path(os.environ['AILOOT_AUDIO_FILE']).read_bytes()\nif not (audio[:4] == b'RIFF' and audio[8:12] == b'WAVE'):\n raise SystemExit('Supply your actual PCM WAV audio file')\nwith wave.open(io.BytesIO(audio), 'rb') as recording:\n if recording.getcomptype() != 'NONE' or recording.getnframes() <= 0:\n raise SystemExit('Supply a nonempty PCM WAV recording')\nrequest = {'model': 'elevenlabs/scribe-v2', 'input_audio': {'data': base64.b64encode(audio).decode('ascii'), 'format': 'wav'}}\nPath('request.json').write_text(json.dumps(request, ensure_ascii=False), encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/audio/transcriptions \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o response.bin\n# Retain the complete original response, headers and actual X-Client-Request-ID.\n# Read existing owned records for recovery; do not resubmit an uncertain operation.\nComplete original response body, status and forwarded headers. No universal JSON shape, text field or task envelope is added by this handler.
GET /v1/media/tasks/{task_id}GET /v1/media/assets/{asset_id}/contentGET /v1/media/assetsGET /v1/media/assets/{asset_id}Keep every complete returned response, file and content part.
Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.
Retain the actual X-Client-Request-ID and complete response. Read the original owned assets and their exact signed content URLs; never resubmit an uncertain creation.
| Field | Type |
|---|---|
Fieldtext (when present) | Type |
Fieldusage (when present) | Type |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionThe JSON body or explicit canonical model ID is invalid. | Next stepRetain the response and correct the indicated request field. |
Response401 · authentication_error | ConditionThe Ailoot API key is invalid. | Next stepUse your authorized Ailoot API key. |
Response403 · permission_error | ConditionThe key group does not admit this method. | Next stepRetain the returned error details. |
Response404 · not_found_error | ConditionThe selected method has no admitted route. | Next stepRetain the returned error details. |
Response422 · price_unavailable | ConditionThe accepted tariff cannot obtain its required input quantity or bound. | Next stepRetain the response; use the input representation required by the accepted tariff. |
Response503 · | ConditionRequired storage, route, method price or reservation is unavailable. | Next stepKeep the complete original response. An uncertain reservation is not permission to resubmit. |
Response502 · server_error | ConditionThe original result, usage or settlement requires checking. | Next stepRetain the actual request ID and original response. Read the existing owned record; do not resubmit creation. |
Ailoot Ultra elevenlabs/scribe-v2
Use the method paths shown above.