Muse Voice Transcribe 1.0 is Meta’s audio-perception model for transcribing speech, detecting utterance boundaries and attributing turns to speakers. It belongs to the Muse Spark model family and combines recognition, diarization and endpointing within the model. Its output is recognised text with the timing and speaker information available in the selected mode.
The model processes audio in 80-millisecond chunks and decides when to continue listening or emit text. Its adaptive delay allows it to wait for additional audio when a word is more difficult to resolve. This produces partial text while speech is arriving, followed by completed transcription results. Treat the partial hypothesis and the completed turn as different stages of the listening experience.
Choose among three modes. Push-to-talk is the default for a single controlled utterance, such as a voice query or a short dictated passage. Endpointing lets the model detect speech-turn boundaries and return one completed transcript per detected segment. Diarization attributes the recognised speech to speaker labels and is intended for multi-speaker recordings rather than the fastest voice-command turn-taking.
For a recorded clip, the file-transcription workflow returns a complete transcript in one request. The default result is JSON containing the transcript and audio duration, with a turns array in endpointing and diarization modes. Each turn can carry an identifier, start and end in milliseconds and its recognised text. Speaker labels are present in diarization mode. Push-to-talk produces the complete transcript without detected turns in that array. The manufacturer’s recorded-file interface can also return plain text or a stream of transcription events. Plain text keeps detected turns on separate lines and can include speaker labels; an event stream ends after its final event without a separate JSON summary. Its delta partial mode returns incremental text, while the final transcript event contains the complete wording.
Prepare a RIFF/WAVE file containing mono, 16-bit integer PCM audio at 16 or 24 kHz. The model’s native rate is 24 kHz, and the interface also accepts 16 kHz. Convert other containers or encodings into that supported WAV form before supplying a recording. The file-transcription profile allows audio up to 10 minutes and a total request body up to 32 MB. Keep the original recording and any conversion associated with the returned transcript for later listening review.
The live-audio workflow uses raw signed 16-bit little-endian mono PCM, with 16 or 24 kHz audio paced approximately in real time. Its documented session window is 60 minutes. Meta describes native audio input exceeding one hour; the documented file and live-session limits remain separate interface boundaries. Select the recorded-file or live workflow according to whether the audio is already complete or still being captured, and keep results from separate sessions associated with their own input segments.
Muse Voice Transcribe is trained across more than 70 languages, while the documented recognition interface enumerates 25 supported languages. These include English, French, German, Spanish, Arabic, Mandarin Chinese, Hindi, Japanese, Korean, Italian and Portuguese. It recognises code-switching within or between sentences. A language hint can name the languages expected in the audio, but it steers recognition rather than forcing the transcript into one language.
Vocabulary hints help with product terms, acronyms, names or places that are important in a recording. Supply the actual words and spellings you expect to hear. The keyword list biases recognition without guaranteeing an exact spelling, so review decisive terms against the audio. Language hints and keywords are selected at the start of the transcription; keep them appropriate to that recording rather than changing their meaning while a session is running.
The model supports diarization for conversations with more than 20 speakers. Labels such as A and B identify speakers within one transcription. They are not verified names and do not establish that a label refers to the same person in another session. For an original meeting-analysis task, request speaker-attributed turns, retain the recording and use the labels to organise the discussion before assigning any real participant names through the surrounding workflow.
Live partial transcripts can change as more speech arrives. In cumulative mode, each partial replaces the preceding hypothesis instead of adding another copy of it. A detected end of speech marks a boundary, while the completed-turn result supplies the final text and can differ from the last partial. Keep overlapping turns associated with their turn identifiers, and consume the completed results before treating a transcript as finished. When live input ends, signal end of input and keep receiving until the producer finishes flushing pending results. Closing the connection immediately can discard those results; a detected speech boundary ends a turn rather than the whole session.
Timing is at the turn level. This profile does not supply word-level timestamps or confidence scores, and audio-processing progress is not a timestamp for a particular word. Sound-event detection, emotion detection and transcript reformatting are also outside the documented output profile. Use the returned turn intervals for a speaker timeline or segment-level review, and retain the recognised words if a separate editing step later creates cleaner notes.
Useful artifacts include a completed dictated passage, a voice-query transcript, a speaker-attributed conversation or an utterance timeline. Compare names, numbers and technical terms with the original recording, preserve the mode and timing associations, and keep the complete turns available for review. The transcription establishes what was recognised in the audio; answering a spoken question, translating it or turning it into meeting notes belongs to a subsequent application step.
", "aboutText": "Muse Voice Transcribe 1.0 is Meta’s audio-perception model for transcribing speech, detecting utterance boundaries and attributing turns to speakers. It belongs to the Muse Spark model family and combines recognition, diarization and endpointing within the model. Its output is recognised text with the timing and speaker information available in the selected mode.\n\nThe model processes audio in 80-millisecond chunks and decides when to continue listening or emit text. Its adaptive delay allows it to wait for additional audio when a word is more difficult to resolve. This produces partial text while speech is arriving, followed by completed transcription results. Treat the partial hypothesis and the completed turn as different stages of the listening experience.\n\nChoose among three modes. Push-to-talk is the default for a single controlled utterance, such as a voice query or a short dictated passage. Endpointing lets the model detect speech-turn boundaries and return one completed transcript per detected segment. Diarization attributes the recognised speech to speaker labels and is intended for multi-speaker recordings rather than the fastest voice-command turn-taking.\n\nFor a recorded clip, the file-transcription workflow returns a complete transcript in one request. The default result is JSON containing the transcript and audio duration, with a turns array in endpointing and diarization modes. Each turn can carry an identifier, start and end in milliseconds and its recognised text. Speaker labels are present in diarization mode. Push-to-talk produces the complete transcript without detected turns in that array. The manufacturer’s recorded-file interface can also return plain text or a stream of transcription events. Plain text keeps detected turns on separate lines and can include speaker labels; an event stream ends after its final event without a separate JSON summary. Its delta partial mode returns incremental text, while the final transcript event contains the complete wording.\n\nPrepare a RIFF/WAVE file containing mono, 16-bit integer PCM audio at 16 or 24 kHz. The model’s native rate is 24 kHz, and the interface also accepts 16 kHz. Convert other containers or encodings into that supported WAV form before supplying a recording. The file-transcription profile allows audio up to 10 minutes and a total request body up to 32 MB. Keep the original recording and any conversion associated with the returned transcript for later listening review.\n\nThe live-audio workflow uses raw signed 16-bit little-endian mono PCM, with 16 or 24 kHz audio paced approximately in real time. Its documented session window is 60 minutes. Meta describes native audio input exceeding one hour; the documented file and live-session limits remain separate interface boundaries. Select the recorded-file or live workflow according to whether the audio is already complete or still being captured, and keep results from separate sessions associated with their own input segments.\n\nMuse Voice Transcribe is trained across more than 70 languages, while the documented recognition interface enumerates 25 supported languages. These include English, French, German, Spanish, Arabic, Mandarin Chinese, Hindi, Japanese, Korean, Italian and Portuguese. It recognises code-switching within or between sentences. A language hint can name the languages expected in the audio, but it steers recognition rather than forcing the transcript into one language.\n\nVocabulary hints help with product terms, acronyms, names or places that are important in a recording. Supply the actual words and spellings you expect to hear. The keyword list biases recognition without guaranteeing an exact spelling, so review decisive terms against the audio. Language hints and keywords are selected at the start of the transcription; keep them appropriate to that recording rather than changing their meaning while a session is running.\n\nThe model supports diarization for conversations with more than 20 speakers. Labels such as A and B identify speakers within one transcription. They are not verified names and do not establish that a label refers to the same person in another session. For an original meeting-analysis task, request speaker-attributed turns, retain the recording and use the labels to organise the discussion before assigning any real participant names through the surrounding workflow.\n\nLive partial transcripts can change as more speech arrives. In cumulative mode, each partial replaces the preceding hypothesis instead of adding another copy of it. A detected end of speech marks a boundary, while the completed-turn result supplies the final text and can differ from the last partial. Keep overlapping turns associated with their turn identifiers, and consume the completed results before treating a transcript as finished. When live input ends, signal end of input and keep receiving until the producer finishes flushing pending results. Closing the connection immediately can discard those results; a detected speech boundary ends a turn rather than the whole session.\n\nTiming is at the turn level. This profile does not supply word-level timestamps or confidence scores, and audio-processing progress is not a timestamp for a particular word. Sound-event detection, emotion detection and transcript reformatting are also outside the documented output profile. Use the returned turn intervals for a speaker timeline or segment-level review, and retain the recognised words if a separate editing step later creates cleaner notes.\n\nUseful artifacts include a completed dictated passage, a voice-query transcript, a speaker-attributed conversation or an utterance timeline. Compare names, numbers and technical terms with the original recording, preserve the mode and timing associations, and keep the complete turns available for review. The transcription establishes what was recognised in the audio; answering a spoken question, translating it or turning it into meeting notes belongs to a subsequent application step.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "29a61ff48a8ea7f6480e59b634eb6cd3ee8df58408812f0f2f202676cc862d96", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "meta/muse-voice-transcribe-1.0Muse Voice Transcribe 1.0 is Meta’s speech-to-text model for dictation, detected speech turns and speaker-aware transcripts. It supports language and vocabulary hints, code-switching and turn-level timing, with separate workflows for a recorded clip and live audio.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Muse Voice Transcribe 1.0 is Meta’s audio-perception model for transcribing speech, detecting utterance boundaries and attributing turns to speakers. It belongs to the Muse Spark model family and combines recognition, diarization and endpointing within the model. Its output is recognised text with the timing and speaker information available in the selected mode.
The model processes audio in 80-millisecond chunks and decides when to continue listening or emit text. Its adaptive delay allows it to wait for additional audio when a word is more difficult to resolve. This produces partial text while speech is arriving, followed by completed transcription results. Treat the partial hypothesis and the completed turn as different stages of the listening experience.
Choose among three modes. Push-to-talk is the default for a single controlled utterance, such as a voice query or a short dictated passage. Endpointing lets the model detect speech-turn boundaries and return one completed transcript per detected segment. Diarization attributes the recognised speech to speaker labels and is intended for multi-speaker recordings rather than the fastest voice-command turn-taking.
For a recorded clip, the file-transcription workflow returns a complete transcript in one request. The default result is JSON containing the transcript and audio duration, with a turns array in endpointing and diarization modes. Each turn can carry an identifier, start and end in milliseconds and its recognised text. Speaker labels are present in diarization mode. Push-to-talk produces the complete transcript without detected turns in that array. The manufacturer’s recorded-file interface can also return plain text or a stream of transcription events. Plain text keeps detected turns on separate lines and can include speaker labels; an event stream ends after its final event without a separate JSON summary. Its delta partial mode returns incremental text, while the final transcript event contains the complete wording.
Prepare a RIFF/WAVE file containing mono, 16-bit integer PCM audio at 16 or 24 kHz. The model’s native rate is 24 kHz, and the interface also accepts 16 kHz. Convert other containers or encodings into that supported WAV form before supplying a recording. The file-transcription profile allows audio up to 10 minutes and a total request body up to 32 MB. Keep the original recording and any conversion associated with the returned transcript for later listening review.
The live-audio workflow uses raw signed 16-bit little-endian mono PCM, with 16 or 24 kHz audio paced approximately in real time. Its documented session window is 60 minutes. Meta describes native audio input exceeding one hour; the documented file and live-session limits remain separate interface boundaries. Select the recorded-file or live workflow according to whether the audio is already complete or still being captured, and keep results from separate sessions associated with their own input segments.
Muse Voice Transcribe is trained across more than 70 languages, while the documented recognition interface enumerates 25 supported languages. These include English, French, German, Spanish, Arabic, Mandarin Chinese, Hindi, Japanese, Korean, Italian and Portuguese. It recognises code-switching within or between sentences. A language hint can name the languages expected in the audio, but it steers recognition rather than forcing the transcript into one language.
Vocabulary hints help with product terms, acronyms, names or places that are important in a recording. Supply the actual words and spellings you expect to hear. The keyword list biases recognition without guaranteeing an exact spelling, so review decisive terms against the audio. Language hints and keywords are selected at the start of the transcription; keep them appropriate to that recording rather than changing their meaning while a session is running.
The model supports diarization for conversations with more than 20 speakers. Labels such as A and B identify speakers within one transcription. They are not verified names and do not establish that a label refers to the same person in another session. For an original meeting-analysis task, request speaker-attributed turns, retain the recording and use the labels to organise the discussion before assigning any real participant names through the surrounding workflow.
Live partial transcripts can change as more speech arrives. In cumulative mode, each partial replaces the preceding hypothesis instead of adding another copy of it. A detected end of speech marks a boundary, while the completed-turn result supplies the final text and can differ from the last partial. Keep overlapping turns associated with their turn identifiers, and consume the completed results before treating a transcript as finished. When live input ends, signal end of input and keep receiving until the producer finishes flushing pending results. Closing the connection immediately can discard those results; a detected speech boundary ends a turn rather than the whole session.
Timing is at the turn level. This profile does not supply word-level timestamps or confidence scores, and audio-processing progress is not a timestamp for a particular word. Sound-event detection, emotion detection and transcript reformatting are also outside the documented output profile. Use the returned turn intervals for a speaker timeline or segment-level review, and retain the recognised words if a separate editing step later creates cleaner notes.
Useful artifacts include a completed dictated passage, a voice-query transcript, a speaker-attributed conversation or an utterance timeline. Compare names, numbers and technical terms with the original recording, preserve the mode and timing associations, and keep the complete turns available for review. The transcription establishes what was recognised in the audio; answering a spoken question, translating it or turning it into meeting notes belongs to a subsequent application step.
POST /v1/audio/transcriptionsaudiotext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits meta/muse-voice-transcribe-1.0 | 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.0001 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': 'meta/muse-voice-transcribe-1.0', '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 meta/muse-voice-transcribe-1.0
Use the method paths shown above.