Universal-3.5 Pro is AssemblyAI’s speech-recognition model for converting recorded speech into text. In its Sync profile, a short audio clip produces a completed transcript in one response. This suits voice messages, push-to-talk input and discrete conversational turns where the application already knows when the recording should end.
Prepare the audio as a bounded clip. AssemblyAI’s Sync requirements accept durations from 80 milliseconds to 120 seconds, with a maximum file size of 40 MB. The supported formats are WAV or raw signed 16-bit little-endian PCM. Audio can be mono or stereo, with stereo down-mixed internally. Supported sample rates are 8, 16, 22.05, 24, 32, 44.1 and 48 kHz. A WAV header supplies the sample rate and channel count; raw PCM needs those values supplied separately in the transcription configuration.
Capture the complete utterance and keep the beginning and ending of the speech intact. A useful original task is a short product-support voice message containing a product name, an order identifier and a request. Retain the source clip so the transcript can be checked against those important details. For a longer recording, prepare a workflow appropriate to long-form transcription rather than treating the short-clip duration limit as a model-wide audio capacity claim.
The result contains the full transcript, a word list with per-word confidence and an overall confidence between zero and one. It also provides the submitted audio duration and a request identifier, making it possible to keep the text associated with its original clip. Use word confidence to locate passages that deserve listening review, especially names, numbers and domain vocabulary that matter to the application.
Word timestamps are optional and off by default. When requested, each aligned word can carry its start and end in milliseconds relative to the clip’s beginning. The maker’s profile leaves those values absent when a word cannot be aligned, rather than inventing an approximate timing. Timestamp accuracy is best for English audio. Retain missing timings explicitly when preparing word highlighting, a searchable waveform or subtitle alignment, and compare the text with the recording before using it as a finished caption track.
A contextual prompt describes what the recording is about. It can name a domain, a scenario or specific details already known to the application, and its maximum length is 6000 characters. Start with a short description that fits the audio, such as a technical-support conversation about a particular device. The prompt supplies recognition context; it is not a request to rewrite the speaker’s message into a different document.
A separate keyterm list biases recognition towards specific vocabulary. The Sync profile accepts up to 100 terms and 8000 characters across that list. Use exact spellings for unusual names, acronyms or product terms, and leave ordinary well-recognised words out of the list. Large or unnecessary term lists can cause overcorrections, so focus the list on words that matter in the recording. The context description and vocabulary list can be used together.
Prior conversation can also help interpret a short reply. Supply previous utterances in chronological order, from oldest to newest, while the current audio remains the turn being transcribed. The documented context allowance is 500 turns or 16,000 characters in total. If it exceeds those caps or the available model context, the oldest entries are removed first. This is useful when a brief answer contains an identifier or a reference whose meaning comes from the preceding question.
Language selection steers recognition towards one or more expected languages. The current Sync interface accepts 32 language codes and defaults to English when no selection is supplied. For code-switching audio, list the expected languages. A custom contextual prompt replaces the managed default and overrides the separate language-code steering, so name the expected languages inside that prompt when both language and scenario context are needed. Keep the transcript in the languages actually spoken rather than treating transcription as a translation instruction.
The model also appears in other AssemblyAI transcription workflows, while the Sync profile’s short-clip requirements and result fields belong to this particular interface. The maker’s Dictation workflow adds a separate text-cleanup stage; a transcript and a rewritten message are different artifacts. Preserve the recognised speech if a later editing or summarisation step produces a cleaned version, so the original wording remains available for comparison.
Useful deliverables include a transcribed voice message, a completed turn for an assistant, short searchable audio text or a timed word list for a review interface. Check the decisive words against the recording, preserve any missing alignments and keep the clip linked to the returned text. The recognition result gives the next application step a source-backed transcription; answering the request or editing the message belongs to the surrounding workflow.
", "aboutText": "Universal-3.5 Pro is AssemblyAI’s speech-recognition model for converting recorded speech into text. In its Sync profile, a short audio clip produces a completed transcript in one response. This suits voice messages, push-to-talk input and discrete conversational turns where the application already knows when the recording should end.\n\nPrepare the audio as a bounded clip. AssemblyAI’s Sync requirements accept durations from 80 milliseconds to 120 seconds, with a maximum file size of 40 MB. The supported formats are WAV or raw signed 16-bit little-endian PCM. Audio can be mono or stereo, with stereo down-mixed internally. Supported sample rates are 8, 16, 22.05, 24, 32, 44.1 and 48 kHz. A WAV header supplies the sample rate and channel count; raw PCM needs those values supplied separately in the transcription configuration.\n\nCapture the complete utterance and keep the beginning and ending of the speech intact. A useful original task is a short product-support voice message containing a product name, an order identifier and a request. Retain the source clip so the transcript can be checked against those important details. For a longer recording, prepare a workflow appropriate to long-form transcription rather than treating the short-clip duration limit as a model-wide audio capacity claim.\n\nThe result contains the full transcript, a word list with per-word confidence and an overall confidence between zero and one. It also provides the submitted audio duration and a request identifier, making it possible to keep the text associated with its original clip. Use word confidence to locate passages that deserve listening review, especially names, numbers and domain vocabulary that matter to the application.\n\nWord timestamps are optional and off by default. When requested, each aligned word can carry its start and end in milliseconds relative to the clip’s beginning. The maker’s profile leaves those values absent when a word cannot be aligned, rather than inventing an approximate timing. Timestamp accuracy is best for English audio. Retain missing timings explicitly when preparing word highlighting, a searchable waveform or subtitle alignment, and compare the text with the recording before using it as a finished caption track.\n\nA contextual prompt describes what the recording is about. It can name a domain, a scenario or specific details already known to the application, and its maximum length is 6000 characters. Start with a short description that fits the audio, such as a technical-support conversation about a particular device. The prompt supplies recognition context; it is not a request to rewrite the speaker’s message into a different document.\n\nA separate keyterm list biases recognition towards specific vocabulary. The Sync profile accepts up to 100 terms and 8000 characters across that list. Use exact spellings for unusual names, acronyms or product terms, and leave ordinary well-recognised words out of the list. Large or unnecessary term lists can cause overcorrections, so focus the list on words that matter in the recording. The context description and vocabulary list can be used together.\n\nPrior conversation can also help interpret a short reply. Supply previous utterances in chronological order, from oldest to newest, while the current audio remains the turn being transcribed. The documented context allowance is 500 turns or 16,000 characters in total. If it exceeds those caps or the available model context, the oldest entries are removed first. This is useful when a brief answer contains an identifier or a reference whose meaning comes from the preceding question.\n\nLanguage selection steers recognition towards one or more expected languages. The current Sync interface accepts 32 language codes and defaults to English when no selection is supplied. For code-switching audio, list the expected languages. A custom contextual prompt replaces the managed default and overrides the separate language-code steering, so name the expected languages inside that prompt when both language and scenario context are needed. Keep the transcript in the languages actually spoken rather than treating transcription as a translation instruction.\n\nThe model also appears in other AssemblyAI transcription workflows, while the Sync profile’s short-clip requirements and result fields belong to this particular interface. The maker’s Dictation workflow adds a separate text-cleanup stage; a transcript and a rewritten message are different artifacts. Preserve the recognised speech if a later editing or summarisation step produces a cleaned version, so the original wording remains available for comparison.\n\nUseful deliverables include a transcribed voice message, a completed turn for an assistant, short searchable audio text or a timed word list for a review interface. Check the decisive words against the recording, preserve any missing alignments and keep the clip linked to the returned text. The recognition result gives the next application step a source-backed transcription; answering the request or editing the message belongs to the surrounding workflow.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "623b3eb3ea94f4f8828a7b36f457cbbd51e211543f4e8007588800fa14b5d515", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "assemblyai/universal-3-5-proUniversal-3.5 Pro is AssemblyAI’s speech-to-text model for turning a short audio clip into a completed transcript in one response. Its Sync profile adds word confidence, optional word timestamps, vocabulary hints and prior-conversation context for voice input and push-to-talk workflows.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Universal-3.5 Pro is AssemblyAI’s speech-recognition model for converting recorded speech into text. In its Sync profile, a short audio clip produces a completed transcript in one response. This suits voice messages, push-to-talk input and discrete conversational turns where the application already knows when the recording should end.
Prepare the audio as a bounded clip. AssemblyAI’s Sync requirements accept durations from 80 milliseconds to 120 seconds, with a maximum file size of 40 MB. The supported formats are WAV or raw signed 16-bit little-endian PCM. Audio can be mono or stereo, with stereo down-mixed internally. Supported sample rates are 8, 16, 22.05, 24, 32, 44.1 and 48 kHz. A WAV header supplies the sample rate and channel count; raw PCM needs those values supplied separately in the transcription configuration.
Capture the complete utterance and keep the beginning and ending of the speech intact. A useful original task is a short product-support voice message containing a product name, an order identifier and a request. Retain the source clip so the transcript can be checked against those important details. For a longer recording, prepare a workflow appropriate to long-form transcription rather than treating the short-clip duration limit as a model-wide audio capacity claim.
The result contains the full transcript, a word list with per-word confidence and an overall confidence between zero and one. It also provides the submitted audio duration and a request identifier, making it possible to keep the text associated with its original clip. Use word confidence to locate passages that deserve listening review, especially names, numbers and domain vocabulary that matter to the application.
Word timestamps are optional and off by default. When requested, each aligned word can carry its start and end in milliseconds relative to the clip’s beginning. The maker’s profile leaves those values absent when a word cannot be aligned, rather than inventing an approximate timing. Timestamp accuracy is best for English audio. Retain missing timings explicitly when preparing word highlighting, a searchable waveform or subtitle alignment, and compare the text with the recording before using it as a finished caption track.
A contextual prompt describes what the recording is about. It can name a domain, a scenario or specific details already known to the application, and its maximum length is 6000 characters. Start with a short description that fits the audio, such as a technical-support conversation about a particular device. The prompt supplies recognition context; it is not a request to rewrite the speaker’s message into a different document.
A separate keyterm list biases recognition towards specific vocabulary. The Sync profile accepts up to 100 terms and 8000 characters across that list. Use exact spellings for unusual names, acronyms or product terms, and leave ordinary well-recognised words out of the list. Large or unnecessary term lists can cause overcorrections, so focus the list on words that matter in the recording. The context description and vocabulary list can be used together.
Prior conversation can also help interpret a short reply. Supply previous utterances in chronological order, from oldest to newest, while the current audio remains the turn being transcribed. The documented context allowance is 500 turns or 16,000 characters in total. If it exceeds those caps or the available model context, the oldest entries are removed first. This is useful when a brief answer contains an identifier or a reference whose meaning comes from the preceding question.
Language selection steers recognition towards one or more expected languages. The current Sync interface accepts 32 language codes and defaults to English when no selection is supplied. For code-switching audio, list the expected languages. A custom contextual prompt replaces the managed default and overrides the separate language-code steering, so name the expected languages inside that prompt when both language and scenario context are needed. Keep the transcript in the languages actually spoken rather than treating transcription as a translation instruction.
The model also appears in other AssemblyAI transcription workflows, while the Sync profile’s short-clip requirements and result fields belong to this particular interface. The maker’s Dictation workflow adds a separate text-cleanup stage; a transcript and a rewritten message are different artifacts. Preserve the recognised speech if a later editing or summarisation step produces a cleaned version, so the original wording remains available for comparison.
Useful deliverables include a transcribed voice message, a completed turn for an assistant, short searchable audio text or a timed word list for a review interface. Check the decisive words against the recording, preserve any missing alignments and keep the clip linked to the returned text. The recognition result gives the next application step a source-backed transcription; answering the request or editing the message belongs to the surrounding workflow.
POST /v1/audio/transcriptionsaudiotext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits assemblyai/universal-3-5-pro | 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.00025 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': 'assemblyai/universal-3-5-pro', '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 assemblyai/universal-3-5-pro
Use the method paths shown above.