Transcribe 1 is Fish Audio’s general speech-to-text model for short recordings. It accepts an audio file and returns the recognised words as text, with the recording’s duration, optional timed segments and language information when known. This model is useful for a short voice note, a spoken instruction, an excerpt from a recording or an audio clip that needs a readable text representation.
An illustrative voice-note workflow keeps the recording together with its full transcript and an identifier for the original clip. A later application step can search that text, organise the note or develop a summary while preserving the spoken source. For a command, the transcript supplies recognised words to the application; any action is a separate interpretation and execution step. For an interview excerpt, record the clip’s position in the complete audio so a quotation can be checked at the right location.
The producer accepts WAV, MP3, AAC including M4A/MP4, FLAC and Ogg containing Opus or Vorbis. Browser recordings in WebM should be converted to Ogg/Opus, MP3 or WAV for this model; Pro documents native support for additional containers. Supply one audio file per request. The base model’s documented request allowance is up to 50 MiB, with MP3 and Opus files kept under 25 MiB. File size and recording length are different considerations: a compressed file can fit the upload allowance while still taking too long to process.
Transcribe 1 is designed for short recordings. The producer recommends Pro for audio longer than a few minutes; a long base-model request can fail if it exceeds the processing-time limit. When preparing a longer source for short-clip transcription, preserve each clip’s starting offset and confirm that the returned transcript covers the complete clip before combining the results. Add the original offset to local segment times to keep navigation connected to the full recording. The base model’s guidance should not be interpreted as Pro’s separate 60-minute allowance.
The producer response includes text, duration and segments. Duration is expressed in seconds, and the readable full transcript should be kept as the primary wording of the clip. Timestamps are optional: ignore_timestamps defaults to true in the producer API, while false requests word-level segments with text, start and end times in seconds. Requesting alignment adds processing time. An empty segments array can reflect skipped timing, no speech or temporarily unavailable alignment, so it should not automatically be interpreted as an empty full transcript.
Segments are generally words, or a character or a few in Chinese and Japanese. Their text omits punctuation and can normalise a value differently from the full transcript; it is not a character-for-character copy of the readable response. A segment can have the same start and end time. Use segments for finding a position in the recording or preparing timed display, and use the full text when the wording and punctuation matter. Keep those two representations distinct in the resulting artifact.
Language is detected automatically, whether or not an optional language hint is supplied. The producer documents lowercase ISO 639-1 codes for hints and returns a language code for application logic together with a language name for display when known. The response reports one language rather than every language in a recording that switches between languages. Keep the source wording and available language metadata with the result instead of treating the transcription request as a translation operation.
For a caption workflow, group consecutive timed segments into readable cues rather than showing one word at a time. A useful output is an SRT or WebVTT file linked to the original clip, with cue boundaries that fit pauses and a manageable amount of text on screen. Check for missing timing and ensure each cue’s end follows its start. Caption grouping and file formatting are application steps built from the returned alignment, and their display choices should suit the player and audience.
Transcribe 1’s documented controls are audio, a language hint and the timestamp choice. Pro’s speaker markers, structured speaker turns, emotion-event controls and speaker-count hints are separate features; they are not part of this base model’s documented response contract. Choose the required artifact before processing: plain readable text for a note, or text together with alignment for playback navigation and captions. Preserving the clip identifier, transcript and any available timing makes that result useful for the next application stage.
", "aboutText": "Transcribe 1 is Fish Audio’s general speech-to-text model for short recordings. It accepts an audio file and returns the recognised words as text, with the recording’s duration, optional timed segments and language information when known. This model is useful for a short voice note, a spoken instruction, an excerpt from a recording or an audio clip that needs a readable text representation.\n\nAn illustrative voice-note workflow keeps the recording together with its full transcript and an identifier for the original clip. A later application step can search that text, organise the note or develop a summary while preserving the spoken source. For a command, the transcript supplies recognised words to the application; any action is a separate interpretation and execution step. For an interview excerpt, record the clip’s position in the complete audio so a quotation can be checked at the right location.\n\nThe producer accepts WAV, MP3, AAC including M4A/MP4, FLAC and Ogg containing Opus or Vorbis. Browser recordings in WebM should be converted to Ogg/Opus, MP3 or WAV for this model; Pro documents native support for additional containers. Supply one audio file per request. The base model’s documented request allowance is up to 50 MiB, with MP3 and Opus files kept under 25 MiB. File size and recording length are different considerations: a compressed file can fit the upload allowance while still taking too long to process.\n\nTranscribe 1 is designed for short recordings. The producer recommends Pro for audio longer than a few minutes; a long base-model request can fail if it exceeds the processing-time limit. When preparing a longer source for short-clip transcription, preserve each clip’s starting offset and confirm that the returned transcript covers the complete clip before combining the results. Add the original offset to local segment times to keep navigation connected to the full recording. The base model’s guidance should not be interpreted as Pro’s separate 60-minute allowance.\n\nThe producer response includes text, duration and segments. Duration is expressed in seconds, and the readable full transcript should be kept as the primary wording of the clip. Timestamps are optional: ignore_timestamps defaults to true in the producer API, while false requests word-level segments with text, start and end times in seconds. Requesting alignment adds processing time. An empty segments array can reflect skipped timing, no speech or temporarily unavailable alignment, so it should not automatically be interpreted as an empty full transcript.\n\nSegments are generally words, or a character or a few in Chinese and Japanese. Their text omits punctuation and can normalise a value differently from the full transcript; it is not a character-for-character copy of the readable response. A segment can have the same start and end time. Use segments for finding a position in the recording or preparing timed display, and use the full text when the wording and punctuation matter. Keep those two representations distinct in the resulting artifact.\n\nLanguage is detected automatically, whether or not an optional language hint is supplied. The producer documents lowercase ISO 639-1 codes for hints and returns a language code for application logic together with a language name for display when known. The response reports one language rather than every language in a recording that switches between languages. Keep the source wording and available language metadata with the result instead of treating the transcription request as a translation operation.\n\nFor a caption workflow, group consecutive timed segments into readable cues rather than showing one word at a time. A useful output is an SRT or WebVTT file linked to the original clip, with cue boundaries that fit pauses and a manageable amount of text on screen. Check for missing timing and ensure each cue’s end follows its start. Caption grouping and file formatting are application steps built from the returned alignment, and their display choices should suit the player and audience.\n\nTranscribe 1’s documented controls are audio, a language hint and the timestamp choice. Pro’s speaker markers, structured speaker turns, emotion-event controls and speaker-count hints are separate features; they are not part of this base model’s documented response contract. Choose the required artifact before processing: plain readable text for a note, or text together with alignment for playback navigation and captions. Preserving the clip identifier, transcript and any available timing makes that result useful for the next application stage.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "47df0ab108472a401a6db793ca89c275fbafee7acfded2731e33927bcffbf55b", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "fish-audio/transcribe-1Transcribe 1 converts short audio recordings into text with automatic language detection and optional word-level timestamps. Use the transcript for voice notes, searchable clips or caption preparation, keeping timed segments separate from the readable full text.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Transcribe 1 is Fish Audio’s general speech-to-text model for short recordings. It accepts an audio file and returns the recognised words as text, with the recording’s duration, optional timed segments and language information when known. This model is useful for a short voice note, a spoken instruction, an excerpt from a recording or an audio clip that needs a readable text representation.
An illustrative voice-note workflow keeps the recording together with its full transcript and an identifier for the original clip. A later application step can search that text, organise the note or develop a summary while preserving the spoken source. For a command, the transcript supplies recognised words to the application; any action is a separate interpretation and execution step. For an interview excerpt, record the clip’s position in the complete audio so a quotation can be checked at the right location.
The producer accepts WAV, MP3, AAC including M4A/MP4, FLAC and Ogg containing Opus or Vorbis. Browser recordings in WebM should be converted to Ogg/Opus, MP3 or WAV for this model; Pro documents native support for additional containers. Supply one audio file per request. The base model’s documented request allowance is up to 50 MiB, with MP3 and Opus files kept under 25 MiB. File size and recording length are different considerations: a compressed file can fit the upload allowance while still taking too long to process.
Transcribe 1 is designed for short recordings. The producer recommends Pro for audio longer than a few minutes; a long base-model request can fail if it exceeds the processing-time limit. When preparing a longer source for short-clip transcription, preserve each clip’s starting offset and confirm that the returned transcript covers the complete clip before combining the results. Add the original offset to local segment times to keep navigation connected to the full recording. The base model’s guidance should not be interpreted as Pro’s separate 60-minute allowance.
The producer response includes text, duration and segments. Duration is expressed in seconds, and the readable full transcript should be kept as the primary wording of the clip. Timestamps are optional: ignore_timestamps defaults to true in the producer API, while false requests word-level segments with text, start and end times in seconds. Requesting alignment adds processing time. An empty segments array can reflect skipped timing, no speech or temporarily unavailable alignment, so it should not automatically be interpreted as an empty full transcript.
Segments are generally words, or a character or a few in Chinese and Japanese. Their text omits punctuation and can normalise a value differently from the full transcript; it is not a character-for-character copy of the readable response. A segment can have the same start and end time. Use segments for finding a position in the recording or preparing timed display, and use the full text when the wording and punctuation matter. Keep those two representations distinct in the resulting artifact.
Language is detected automatically, whether or not an optional language hint is supplied. The producer documents lowercase ISO 639-1 codes for hints and returns a language code for application logic together with a language name for display when known. The response reports one language rather than every language in a recording that switches between languages. Keep the source wording and available language metadata with the result instead of treating the transcription request as a translation operation.
For a caption workflow, group consecutive timed segments into readable cues rather than showing one word at a time. A useful output is an SRT or WebVTT file linked to the original clip, with cue boundaries that fit pauses and a manageable amount of text on screen. Check for missing timing and ensure each cue’s end follows its start. Caption grouping and file formatting are application steps built from the returned alignment, and their display choices should suit the player and audience.
Transcribe 1’s documented controls are audio, a language hint and the timestamp choice. Pro’s speaker markers, structured speaker turns, emotion-event controls and speaker-count hints are separate features; they are not part of this base model’s documented response contract. Choose the required artifact before processing: plain readable text for a note, or text together with alignment for playback navigation and captions. Preserving the clip identifier, transcript and any available timing makes that result useful for the next application stage.
POST /v1/audio/transcriptionsaudiotext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits fish-audio/transcribe-1 | 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.0002 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': 'fish-audio/transcribe-1', '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 fish-audio/transcribe-1
Use the method paths shown above.