Turn a long recording into plain text
Four or more companies' docs show a full fit.
What counts as done
The whole recording is transcribed in one job or an automatic chunking the tool manages.
Measured, for our own tests: full text to the last spoken word, with the final word's timestamp within 5 seconds of the audio's duration, and no repeated or invented sentences over silent stretches. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: transcribe this two-hour podcast
, get me the text of this lecture video
, transcribe these 40 council meeting recordings
Does the job 5
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Azure AI Speech speech-to-text BB Microsoft Corporation | Fast transcription accepts files under 5 hours and 500 MB synchronously; batch takes 1 GB files from a URL with word timestamps. source |
| Deepgram Speech-to-Text (Nova-3, Flux) BB Deepgram, Inc. | Pre-recorded accepts files to 2 GB by upload or URL with a callback for long jobs; the duration field is returned on every response. source |
| ElevenLabs Scribe Speech to Text API BB Eleven Labs Inc. | Files to 5 GB and 15 hours per request with audio_duration_secs returned; webhook delivery for long jobs. source |
| IBM Watson Speech to Text C International Business Machines Corporation | /v1/recognitions takes up to 1 GB per request with callbacks; results are kept one week by default. source |
| Rev AI Speech-to-Text API C Rev.com, Inc. | Jobs take media to 17 hours (6 for Telugu) and 2 GB from a URL, with webhooks. source |
Does the job, with a limit 23
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Amazon Transcribe BB Amazon Web Services, Inc. | Batch jobs take files to 28,800 seconds and 2 GB, but input must sit in S3 and acc-06 reports timestamp drift on long files. source |
| AssemblyAI Speech-to-Text (Universal) B AssemblyAI, Inc. | One job takes files to 10 hours and 5 GB, but acc-30 shows a one-hour file losing half its text on the legacy Best tier; the maintainer advised universal-3-5-pro and checking the last word's end time. source |
| Cartesia Ink B Cartesia AI, Inc. | POST /stt transcribes ink-whisper files with a duration field, but no file size or duration limit is documented and ink-2 has no batch endpoint. source |
| Cohere Transcribe 03-2026 C Cohere Inc. | The Transformers processor chunks long audio and reassembles by audio_chunk_index, but Cohere's API caps files at 25 MB and the blog says the model transcribes non-speech sounds without a VAD. source |
| Giggy Speech to Text E Giggy | Free Batch stops at 25 minutes; paid Fast takes recordings to 12 hours but only as 16 kHz mono PCM WAV, and the transcript is fetched from a signed URL that can disappear after retention cleanup. source |
| Gladia Speech-to-Text API + MCP BB Gladia SAS | Pre-recorded files are capped at 135 minutes and 1,000 MB with an error beyond that, so Gladia advises splitting into about 60-minute chunks yourself. source |
| Google Cloud Speech-to-Text B Google LLC | BatchRecognize takes files to 8 hours but only from Cloud Storage; acc-05 and acc-06 report Chirp repeating filler text on silence and skipping speech. source |
| Groq Speech-to-Text BB Groq LLC | Uploads stop at 25 MB free or 100 MB on the Developer plan; url avoids the attachment cap but the plan size limit still forces client-side chunking of long recordings. source |
| Inworld STT C Theai, Inc. dba Inworld AI | Async jobs take 512 MB of audio or video, but results and the recording are deleted after 7 days, so the agent must collect in time. source |
| Ming-3.0-asr-tiny C inclusionAI, Ant Group (named in the site footer of inclusion-ai.org; the LICENSE copyright line reads inclusionAI) | Long audio is encoded in chunks with --audio-chunk-frames, within an 8,192-token context shared by audio and text, so hours of audio need the caller to split. source |
| Ming-3.0-audio-flash E inclusionAI, Ant Group (named in the inclusion-ai.org footer; no registered company named) | The ASR task runs through vLLM-Omni or SGLang on four to eight 80 GB GPUs; the card warns long audio may OOM the four-GPU profile and documents no chunking. source |
| Ming-3.0-audio-tiny D inclusionAI (Ant Group) | ASR runs on one GPU through SGLang-Omni or vLLM-Omni with inclusionAI's code; no chunking or duration limit is documented for long files. source |
| Mistral Voxtral Transcribe B Mistral AI (RCS Paris 952 418 325) | Batch takes file, file_url or file_id; the up-to-3-hours figure is only on the announcement page, not in the API reference read. source |
| Nemotron 3.5 ASR Streaming 0.6B C NVIDIA Corporation | Offline transcription is documented in NeMo and Transformers with chunked streaming, but no duration limit or long-file test is published. source |
| OpenAI Speech to Text BB OpenAI OpCo, LLC | Files stop at 25 MB and the caller splits; acc-19 shows gpt-4o-transcribe truncating at output_tokens 2048 with no error, unchecked for gpt-transcribe. source |
| Parakeet TDT 0.6B v3 B NVIDIA Corporation | Audio past about 24 minutes needs NeMo switched to local attention, and a discussion reports CUDA out of memory on long audio; no managed chunking in Transformers. source |
| Qwen3-ASR-0.6B C Alibaba Cloud (the registrant of qwen.ai per RDAP, carried from the Qwen3.8-27B check) | The report covers single recordings to 20 minutes and max_new_tokens must be raised for long audio, or output is cut; longer files need caller chunking. source |
| Qwen3-ASR-1.7B B Alibaba Cloud (the registrant of qwen.ai per RDAP, carried from the Qwen3.8-27B check) | The report covers single recordings to 20 minutes and max_new_tokens must be raised for long audio, or output is cut; longer files need caller chunking. source |
| Smallest.ai Pulse STT B Smallest, Inc. | Pre-recorded accepts files with webhook delivery; Pulse Pro caps audio at 250 MB or 50 MB with a webhook and returns 413 beyond, and no duration cap is stated. source |
| Soniox Speech-to-Text B Soniox Inc. | Async files are capped at a fixed 300 minutes and must be deleted by the caller; files and transcripts expire after 30 days. source |
| Speechmatics Speech-to-Text BB Cantab Research Ltd | Files to 1 GB in the request body, larger by URL, but transcripts expire after 7 days and no duration cap is stated. source |
| Underdog Bark 3.0 E Conway Research | The card says split recordings into a few minutes on 8 or 16 GB machines and that long-recording segmentation has not been qualified; a 10-minute file peaked near 15 GB. source |
| Voxtral Mini 4B Realtime 2602 B Mistral AI (RCS Paris 952 418 325) | vLLM's default max model length covers about 3 hours, but acc-22 reports output cut short unless max_new_tokens is at least duration over 80 ms, and acc-27 shows the Docker image failing to load it. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| MiniMax Speech-to-Text D Nanonoble Pte. Ltd. | Audio over 500 seconds or 50 MB returns 400, so a long recording cannot run as one job and the tool manages no chunking. |
3 listings in the category were added after this reading and aren't marked yet.
What stops agents finishing
- silent truncation at an output token cap (acc-19: gpt-4o-transcribe stopped at about 8 to 9 minutes with no error)
- hard duration caps far below the recording (MiniMax 500 seconds, Google sync 1 minute, Groq 25 MB free)
- input must sit in the vendor's own storage (Amazon S3, Google Cloud Storage)
- transcript URL expires before the agent collects it (Speechmatics 7 days, Inworld 7 days, Giggy signed URL)
Around it
Before: media.download-video, storage.fetch-file. After: llm.correct-proper-nouns, llm.summarise, search.index-text.
Where this comes from
Weight 14 of 100 in Speech-to-text: 7 of 32 accounts (acc-09, acc-13, acc-15, acc-16, acc-19, acc-30, acc-32); truncation and silence hallucination were the two failures named
The same as data: /api/v1/use-cases/speech-to-text.long-recording-batch.json, or the MCP tool get_use_case with id speech-to-text.long-recording-batch. Other jobs in this category: /api/v1/niches?category=speech-to-text.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.