Transcribe a recorded meeting or call and say who said what
Four or more companies' docs show a full fit.
What counts as done
A transcript with a stable speaker label on every segment, labels consistent across the whole file including any chunks, in one job.
Measured, for our own tests: speaker count within one of the true count. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: transcribe this meeting and label the speakers
, who said what in this call
, give me notes with each action item attributed
Does the job 6
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Amazon Transcribe BB Amazon Web Services, Inc. | ShowSpeakerLabels with MaxSpeakerLabels 2 to 30 on batch jobs; files to 28,800 seconds and 2 GB, so a 3-hour meeting runs as one job without chunking. source |
| AssemblyAI Speech-to-Text (Universal) B AssemblyAI, Inc. | speaker_labels with speakers_expected or min and max caps on files to 10 hours and 5 GB in one job; labels are generic A, B (acc-03) and acc-30 lost text on the legacy tier. source |
| Azure AI Speech speech-to-text BB Microsoft Corporation | Fast transcription takes diarization maxSpeakers 2 to 35 on files under 5 hours and 500 MB; batch transcription has diarizationEnabled and 1 GB files. source |
| ElevenLabs Scribe Speech to Text API BB Eleven Labs Inc. | diarize with num_speakers up to 32 on files to 5 GB and 15 hours in one request; use_speaker_library matches registered speakers across jobs. source |
| Rev AI Speech-to-Text API C Rev.com, Inc. | Diarisation is on unless skip_diarization is set, on media to 17 hours and 2 GB in one job; no speaker cap is documented. source |
| Speechmatics Speech-to-Text BB Cantab Research Ltd | diarization speaker with speaker_diarization_config.max_speakers (unrestricted if omitted) and sensitivity; batch files to 1 GB inline or larger via fetch_data URL. acc-01 ranked it last on postcodes, not speakers. source |
Does the job, with a limit 10
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 |
|---|---|
| Deepgram Speech-to-Text (Nova-3, Flux) BB Deepgram, Inc. | diarize_model v2 labels every word on files to 2 GB in one request, but no speaker cap is documented and acc-29 saw accuracy drop past four speakers. source |
| Gladia Speech-to-Text API + MCP BB Gladia SAS | diarization with number_of_speakers, min and max hints (not enforced) on pre-recorded files to 135 minutes and 1,000 MB; a 3-hour meeting must be split, which restarts speaker labels. source |
| Google Cloud Speech-to-Text B Google LLC | diarization_config with min and max speaker counts; Chirp 3 diarises only in BatchRecognize from Cloud Storage, files to 8 hours. acc-11 says live diarisation stops at about three speakers. source |
| IBM Watson Speech to Text C International Business Machines Corporation | speaker_labels works on HTTP and WebSocket requests to 1 GB async, but is optimised for two speakers with a six-speaker maximum and undefined behaviour beyond. source |
| Inworld STT C Theai, Inc. dba Inworld AI | enableSpeakerDiarization is experimental, applies to the streaming endpoint, and labels per stream; async jobs to 512 MB say diarisation works as synchronously, with no speaker cap. source |
| MiniMax Speech-to-Text D Nanonoble Pte. Ltd. | verbose_json returns n_speakers and speaker on each segment, but requests stop at 500 seconds, so any meeting must be split and speaker labels restart per chunk. source |
| Mistral Voxtral Transcribe B Mistral AI (RCS Paris 952 418 325) | diarize with timestamp_granularities segment gives speaker_id per segment on batch; the 3-hour limit is a vendor claim and the card says one speaker is kept on overlap. acc-09 found it good for podcasts. source |
| OpenAI Speech to Text BB OpenAI OpCo, LLC | Only the deprecated gpt-4o-transcribe-diarize returns diarized_json, within 25 MB per file, so long meetings are chunked and labels flip per chunk (acc-20); it shuts on 2027-02-26. source |
| Smallest.ai Pulse STT B Smallest, Inc. | diarize adds per-word and per-utterance speaker labels on pre-recorded files, but no speaker cap is stated and Pulse Pro caps audio at 250 MB. source |
| Soniox Speech-to-Text B Soniox Inc. | enable_speaker_diarization labels every token on async files to 300 minutes, so a 3-hour file is split; no speaker cap is stated. acc-11 says Soniox does live speakers well. source |
Doesn't do this job 13
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Cartesia Ink B Cartesia AI, Inc. | No diarisation parameter on either endpoint; batch POST /stt accepts ink-whisper only. |
| Cohere Transcribe 03-2026 C Cohere Inc. | The docs state the model has neither timestamps nor speaker diarisation. |
| Giggy Speech to Text E Giggy | No speaker labels; the docs list speaker labels among the functions the API does not return. |
| Groq Speech-to-Text BB Groq LLC | No diarisation parameter on the OpenAI-compatible endpoints. |
| Ming-3.0-asr-tiny C inclusionAI, Ant Group (named in the site footer of inclusion-ai.org; the LICENSE copyright line reads inclusionAI) | Card states output has no speaker diarisation. |
| Ming-3.0-audio-flash E inclusionAI, Ant Group (named in the inclusion-ai.org footer; no registered company named) | No diarisation or speaker output on the card. |
| Ming-3.0-audio-tiny D inclusionAI (Ant Group) | No diarisation on the card. |
| Nemotron 3.5 ASR Streaming 0.6B C NVIDIA Corporation | No diarisation; plain text out. |
| Parakeet TDT 0.6B v3 B NVIDIA Corporation | No diarisation; acc-12 paired it with a separate diarisation model. |
| Qwen3-ASR-0.6B C Alibaba Cloud (the registrant of qwen.ai per RDAP, carried from the Qwen3.8-27B check) | No diarisation; acc-08 chained pyannote separately. |
| Qwen3-ASR-1.7B B Alibaba Cloud (the registrant of qwen.ai per RDAP, carried from the Qwen3.8-27B check) | No diarisation; acc-08 chained pyannote separately. |
| Underdog Bark 3.0 E Conway Research | Plain text only, no speaker labels. |
| Voxtral Mini 4B Realtime 2602 B Mistral AI (RCS Paris 952 418 325) | No diarisation or segments for the weights. |
3 listings in the category were added after this reading and aren't marked yet.
What stops agents finishing
- diarisation restarts per chunk when the file must be split (OpenAI 25 MB cap, acc-20)
- no diarisation at all (Groq, Giggy, Cohere Transcribe, Parakeet, Nemotron, Voxtral Realtime weights)
- speaker labels returned as A, B, C with no way to name them without a human step
- accuracy collapses past 4 speakers (acc-29)
Around it
Before: meetings.record, storage.fetch-file. After: llm.summarise, document-extraction.action-items, notes.store.
Where this comes from
Weight 20 of 100 in Speech-to-text: 10 of 32 accounts (acc-03, acc-06, acc-10, acc-11, acc-13, acc-20, acc-26, acc-29, acc-32, acc-09); the most common failure reported was attribution, not words
The same as data: /api/v1/use-cases/speech-to-text.meeting-with-speakers.json, or the MCP tool get_use_case with id speech-to-text.meeting-with-speakers. 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.