Nova-3 is Deepgram’s general-purpose speech-recognition model for converting audio into text. The producer recommends it for meetings, event captions, multi-speaker recordings and challenging conditions such as noise or distant microphones, using either pre-recorded or streaming transcription. Its useful result is recognized speech with timing and confidence information that remains connected to the source audio.
The documented default language is English. A monolingual request selects the spoken language or supported locale. The current general-model table includes English regional variants, Spanish, French, German, Russian, Portuguese, Japanese, Italian, Dutch, Arabic, Chinese scripts and many other languages, including Kazakh. Select from the producer’s supported codes rather than assuming that any locale name is accepted.
The multilingual setting is a separate code-switching workflow. The current Nova-3 table lists ten languages for it: English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian and Dutch. This set is not identical to the larger monolingual list. For a recording that alternates between supported languages, prepare the multilingual mode instead of forcing the whole conversation into an unrelated single-language setting. Preserve what was spoken before preparing any translated or summarized version.
Deepgram’s file workflow accepts uploaded audio bytes or a reference to an audio file. Save the returned transcript when the request completes; the producer does not store transcripts for later retrieval. Common documented input formats and encodings include MP3, MP4, MP2, AAC, WAV, FLAC, PCM, M4A, Ogg, Opus and WebM. Preserve the actual format and channel information with the recording. Give the recording a stable identifier and keep the result associated with the correct source and its channel information. For a meeting, review participant names and technical terms while listening to the original sound. For a lecture or event, retain the sequence of the audio so a later caption or search result can locate the relevant passage.
The producer’s pre-recorded guide lists a maximum file size of 2 GB and recommends extracting the audio stream from a large video file. It also documents a ten-minute processing timeout for Nova requests. That timeout concerns how long the request processes, not a ten-minute maximum recording duration. A useful result includes the ending of the intended recording; a partially retained transcript should not be treated as the complete text.
The documented JSON response includes transcript alternatives and recognized words, with each word’s start and end time in seconds from the beginning of the audio and a confidence value. For a multi-speaker transcript, the producer’s optional diarization assigns a speaker label to each word. Pre-recorded diarization also returns speaker confidence; streaming diarization returns the speaker label. Review those labels against the voices in the recording. Overall transcript confidence is also reported on a 0–1 scale. When smart formatting is requested, the result can include punctuation and capitalization as punctuated words, along with readable paragraph information.
Use those fields according to their meaning. A word time locates recognized speech, while confidence is the model’s indication of reliability, not proof that a difficult name or quantity was heard correctly. For caption preparation, retain the timing alongside reviewed wording and inspect the boundaries against the sound. For a readable editorial version, keep changes distinguishable from the recognized transcript rather than silently replacing uncertain words with a plausible story.
Nova’s streaming workflow returns text as audio arrives, with interim and final results. The is_final indicator distinguishes text that may be revised from a finalized segment. The speech_final indicator relates to endpointing of a spoken segment. Keep these signals distinct from merely receiving a non-empty transcript, and retain the final segments in their audio order when preparing the completed record.
Nova-3 is general ASR rather than the separate Flux conversational model with model-native turn detection. Nova marks transcript finality and speech endpoints; Flux supplies its own conversational turn-state events. Choose the transcription workflow around whether the audio is already recorded or is arriving live, while using the actual final output as the artifact to retain.
Nova-3’s documented Keyterm Prompting supports monolingual and multilingual transcription and adapts recognition toward important terms without retraining the model. Supply relevant names, product terms, acronyms or multi-word phrases that may actually be spoken. The guide limits the combined keyterm input to 500 tokens and recommends focusing on the most important vocabulary rather than adding common words indiscriminately.
The producer’s syntax uses plain terms, with a separate keyterm entry for each term. A multi-word phrase stays one phrase. Legacy keyword weights or intensifiers, and joining separate terms with commas, semicolons or line breaks, are not equivalent: the interface can accept them as one literal value while providing no intended boost. Use the correct capitalization for names, then check the transcript because audio context and smart formatting can still change the final written form.
The general Nova-3 profile is distinct from the separately named Medical and Pharma options. Vocabulary prompting does not turn it into another edition, and specialized models’ language coverage or behavior should not be assumed for the general model. Additional transcript-processing features are choices in the producer’s speech workflow, not evidence that recognition has produced a summary, translation or other artifact that was never requested.
A useful Nova-3 deliverable can be a searchable meeting transcript, caption-ready wording with word timings, or a record of a multilingual conversation. Retain the audio identifier, selected language workflow, final text and any useful confidence or timing fields. Check unclear names, numbers, overlapping voices and language changes against the original recording, and keep the actual recognized speech available for the next content-processing step.
", "aboutText": "Nova-3 is Deepgram’s general-purpose speech-recognition model for converting audio into text. The producer recommends it for meetings, event captions, multi-speaker recordings and challenging conditions such as noise or distant microphones, using either pre-recorded or streaming transcription. Its useful result is recognized speech with timing and confidence information that remains connected to the source audio.\n\n### Choose the language workflow\n\nThe documented default language is English. A monolingual request selects the spoken language or supported locale. The current general-model table includes English regional variants, Spanish, French, German, Russian, Portuguese, Japanese, Italian, Dutch, Arabic, Chinese scripts and many other languages, including Kazakh. Select from the producer’s supported codes rather than assuming that any locale name is accepted.\n\nThe multilingual setting is a separate code-switching workflow. The current Nova-3 table lists ten languages for it: English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian and Dutch. This set is not identical to the larger monolingual list. For a recording that alternates between supported languages, prepare the multilingual mode instead of forcing the whole conversation into an unrelated single-language setting. Preserve what was spoken before preparing any translated or summarized version.\n\n### Recorded audio and transcript preparation\n\nDeepgram’s file workflow accepts uploaded audio bytes or a reference to an audio file. Save the returned transcript when the request completes; the producer does not store transcripts for later retrieval. Common documented input formats and encodings include MP3, MP4, MP2, AAC, WAV, FLAC, PCM, M4A, Ogg, Opus and WebM. Preserve the actual format and channel information with the recording. Give the recording a stable identifier and keep the result associated with the correct source and its channel information. For a meeting, review participant names and technical terms while listening to the original sound. For a lecture or event, retain the sequence of the audio so a later caption or search result can locate the relevant passage.\n\nThe producer’s pre-recorded guide lists a maximum file size of 2 GB and recommends extracting the audio stream from a large video file. It also documents a ten-minute processing timeout for Nova requests. That timeout concerns how long the request processes, not a ten-minute maximum recording duration. A useful result includes the ending of the intended recording; a partially retained transcript should not be treated as the complete text.\n\n### Read the words, times and confidence\n\nThe documented JSON response includes transcript alternatives and recognized words, with each word’s start and end time in seconds from the beginning of the audio and a confidence value. For a multi-speaker transcript, the producer’s optional diarization assigns a speaker label to each word. Pre-recorded diarization also returns speaker confidence; streaming diarization returns the speaker label. Review those labels against the voices in the recording. Overall transcript confidence is also reported on a 0–1 scale. When smart formatting is requested, the result can include punctuation and capitalization as punctuated words, along with readable paragraph information.\n\nUse those fields according to their meaning. A word time locates recognized speech, while confidence is the model’s indication of reliability, not proof that a difficult name or quantity was heard correctly. For caption preparation, retain the timing alongside reviewed wording and inspect the boundaries against the sound. For a readable editorial version, keep changes distinguishable from the recognized transcript rather than silently replacing uncertain words with a plausible story.\n\n### Streaming recognition and final segments\n\nNova’s streaming workflow returns text as audio arrives, with interim and final results. The is_final indicator distinguishes text that may be revised from a finalized segment. The speech_final indicator relates to endpointing of a spoken segment. Keep these signals distinct from merely receiving a non-empty transcript, and retain the final segments in their audio order when preparing the completed record.\n\nNova-3 is general ASR rather than the separate Flux conversational model with model-native turn detection. Nova marks transcript finality and speech endpoints; Flux supplies its own conversational turn-state events. Choose the transcription workflow around whether the audio is already recorded or is arriving live, while using the actual final output as the artifact to retain.\n\n### Keyterms for vocabulary that matters\n\nNova-3’s documented Keyterm Prompting supports monolingual and multilingual transcription and adapts recognition toward important terms without retraining the model. Supply relevant names, product terms, acronyms or multi-word phrases that may actually be spoken. The guide limits the combined keyterm input to 500 tokens and recommends focusing on the most important vocabulary rather than adding common words indiscriminately.\n\nThe producer’s syntax uses plain terms, with a separate keyterm entry for each term. A multi-word phrase stays one phrase. Legacy keyword weights or intensifiers, and joining separate terms with commas, semicolons or line breaks, are not equivalent: the interface can accept them as one literal value while providing no intended boost. Use the correct capitalization for names, then check the transcript because audio context and smart formatting can still change the final written form.\n\n### Model-family boundaries and useful results\n\nThe general Nova-3 profile is distinct from the separately named Medical and Pharma options. Vocabulary prompting does not turn it into another edition, and specialized models’ language coverage or behavior should not be assumed for the general model. Additional transcript-processing features are choices in the producer’s speech workflow, not evidence that recognition has produced a summary, translation or other artifact that was never requested.\n\nA useful Nova-3 deliverable can be a searchable meeting transcript, caption-ready wording with word timings, or a record of a multilingual conversation. Retain the audio identifier, selected language workflow, final text and any useful confidence or timing fields. Check unclear names, numbers, overlapping voices and language changes against the original recording, and keep the actual recognized speech available for the next content-processing step.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "d88026f78df47c365b468d5e8bf00e3f4dcd5cade6523d11232bc2c36f889735", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "deepgram/nova-3Nova-3 is Deepgram’s general-purpose speech-to-text model for recorded and streaming audio. It supports monolingual recognition, a defined multilingual code-switching mode and keyterm prompting, returning transcripts with word timing and confidence information.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Nova-3 is Deepgram’s general-purpose speech-recognition model for converting audio into text. The producer recommends it for meetings, event captions, multi-speaker recordings and challenging conditions such as noise or distant microphones, using either pre-recorded or streaming transcription. Its useful result is recognized speech with timing and confidence information that remains connected to the source audio.
The documented default language is English. A monolingual request selects the spoken language or supported locale. The current general-model table includes English regional variants, Spanish, French, German, Russian, Portuguese, Japanese, Italian, Dutch, Arabic, Chinese scripts and many other languages, including Kazakh. Select from the producer’s supported codes rather than assuming that any locale name is accepted.
The multilingual setting is a separate code-switching workflow. The current Nova-3 table lists ten languages for it: English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian and Dutch. This set is not identical to the larger monolingual list. For a recording that alternates between supported languages, prepare the multilingual mode instead of forcing the whole conversation into an unrelated single-language setting. Preserve what was spoken before preparing any translated or summarized version.
Deepgram’s file workflow accepts uploaded audio bytes or a reference to an audio file. Save the returned transcript when the request completes; the producer does not store transcripts for later retrieval. Common documented input formats and encodings include MP3, MP4, MP2, AAC, WAV, FLAC, PCM, M4A, Ogg, Opus and WebM. Preserve the actual format and channel information with the recording. Give the recording a stable identifier and keep the result associated with the correct source and its channel information. For a meeting, review participant names and technical terms while listening to the original sound. For a lecture or event, retain the sequence of the audio so a later caption or search result can locate the relevant passage.
The producer’s pre-recorded guide lists a maximum file size of 2 GB and recommends extracting the audio stream from a large video file. It also documents a ten-minute processing timeout for Nova requests. That timeout concerns how long the request processes, not a ten-minute maximum recording duration. A useful result includes the ending of the intended recording; a partially retained transcript should not be treated as the complete text.
The documented JSON response includes transcript alternatives and recognized words, with each word’s start and end time in seconds from the beginning of the audio and a confidence value. For a multi-speaker transcript, the producer’s optional diarization assigns a speaker label to each word. Pre-recorded diarization also returns speaker confidence; streaming diarization returns the speaker label. Review those labels against the voices in the recording. Overall transcript confidence is also reported on a 0–1 scale. When smart formatting is requested, the result can include punctuation and capitalization as punctuated words, along with readable paragraph information.
Use those fields according to their meaning. A word time locates recognized speech, while confidence is the model’s indication of reliability, not proof that a difficult name or quantity was heard correctly. For caption preparation, retain the timing alongside reviewed wording and inspect the boundaries against the sound. For a readable editorial version, keep changes distinguishable from the recognized transcript rather than silently replacing uncertain words with a plausible story.
Nova’s streaming workflow returns text as audio arrives, with interim and final results. The is_final indicator distinguishes text that may be revised from a finalized segment. The speech_final indicator relates to endpointing of a spoken segment. Keep these signals distinct from merely receiving a non-empty transcript, and retain the final segments in their audio order when preparing the completed record.
Nova-3 is general ASR rather than the separate Flux conversational model with model-native turn detection. Nova marks transcript finality and speech endpoints; Flux supplies its own conversational turn-state events. Choose the transcription workflow around whether the audio is already recorded or is arriving live, while using the actual final output as the artifact to retain.
Nova-3’s documented Keyterm Prompting supports monolingual and multilingual transcription and adapts recognition toward important terms without retraining the model. Supply relevant names, product terms, acronyms or multi-word phrases that may actually be spoken. The guide limits the combined keyterm input to 500 tokens and recommends focusing on the most important vocabulary rather than adding common words indiscriminately.
The producer’s syntax uses plain terms, with a separate keyterm entry for each term. A multi-word phrase stays one phrase. Legacy keyword weights or intensifiers, and joining separate terms with commas, semicolons or line breaks, are not equivalent: the interface can accept them as one literal value while providing no intended boost. Use the correct capitalization for names, then check the transcript because audio context and smart formatting can still change the final written form.
The general Nova-3 profile is distinct from the separately named Medical and Pharma options. Vocabulary prompting does not turn it into another edition, and specialized models’ language coverage or behavior should not be assumed for the general model. Additional transcript-processing features are choices in the producer’s speech workflow, not evidence that recognition has produced a summary, translation or other artifact that was never requested.
A useful Nova-3 deliverable can be a searchable meeting transcript, caption-ready wording with word timings, or a record of a multilingual conversation. Retain the audio identifier, selected language workflow, final text and any useful confidence or timing fields. Check unclear names, numbers, overlapping voices and language changes against the original recording, and keep the actual recognized speech available for the next content-processing step.
POST /v1/audio/transcriptionsaudiotranscription| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits deepgram/nova-3 | Default— |
Fieldinput_audio | Typeobject | RequirementRequired | Values & limits | Default— |
Fieldlanguage | Typestring | RequirementOptional | Values & limits | Default— |
Fieldtemperature | Typenumber | RequirementOptional | Values & limits Minimum: 0 Maximum: 1 | Default— |
Fieldresponse_format | Typestring | RequirementOptional | Values & limits json, verbose_json | Defaultjson |
Fieldtimestamp_granularities | Typearray | RequirementOptional | Values & limits | Default— |
Fieldprovider | Typeobject | RequirementOptional | Values & limits | Default— |
speech_to_text · Required: actual matching-format audio file
| Parameter | Contract |
|---|---|
Parametercontent_types | Contractapplication/json, multipart/form-data |
Parameterrequired | Contractmodel, input_audio |
Parametermaterial_types | Contractaudio |
ParameterJSON_audio | Contractactual raw audio bytes in base64 plus matching format |
Parametermultipart_required | Contractmodel, file |
Parametermultipart_cap_bytes | Contract26214400 |
Parameteroptional_controls | Contractlanguage, temperature, response_format, timestamp_granularities, provider |
Parameterdefault_response_format | Contractjson |
Parameteroptional_features | ContractVerbose output, diarize/keyterms and URL/larger inline audio require the exact model/provider capability and tariff. |
Lifecycle: synchronous_result_then_owned_library
GET /v1/media/tasks/{task_id} · actual returned task_id or media library record
GET /v1/media/assets/{asset_id}/content
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
Use the exact model and documented input fields.
Keep the complete response, every actual output and original returned IDs.
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 |
| ConfigurationUltra | Rate schedule— | Billing unitper audio input second | Charge Input · audio input second $0.0001433333333334 per audio input 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 →
Model-level reference schedules do not change method selection, quotes or charges. Active charges use the selected Ailoot method rates.
| Configuration | Billing conditions | Charge |
|---|---|---|
| ConfigurationDeepgram: Nova-3 · Default configuration | Billing conditionsDefault configuration | Charge Input · Input audio seconds ≈$0.000143 per input audio second |
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_AUDIO_FILE:?Set the path to your actual WAV recording}"\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\nimport base64\naudio=Path(os.environ['AILOOT_AUDIO_FILE']).read_bytes()\nif not (audio[:4]==b'RIFF' and audio[8:12]==b'WAVE'): raise SystemExit('Supply an actual WAV audio file')\nif len(audio)>26214400: raise SystemExit('Use a documented supported large-file flow')\nrequest={'model': 'deepgram/nova-3', 'input_audio': {'data': '${BASE64_ACTUAL_WAV_BYTES}', 'format': 'wav'}}\nrequest['input_audio']['data']=base64.b64encode(audio).decode('ascii')\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# Keep the complete original response and headers. Read every returned segment, word and usage field.\n# Preserve actual operation/task/asset IDs; continue reads of the original result without resubmitting.\njson
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.
Complete original JSON, all available text/segments/words/speakers/timestamps and usage.
Retain original operation_id/X-Client-Request-ID and original response. Read actual owned task/asset records without resubmitting; no dedicated audio poll URL is constructed.
| Field | Type |
|---|---|
Fieldtext | Typestring |
Fieldusage | Typeobject |
Fieldsegments[] | Typeobject |
Fieldwords[] | Typeobject |
Ailoot Ultra deepgram/nova-3
Use the method paths shown above.