> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://developers.deepgram.com/changelog/2026/5/13/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.deepgram.com/_mcp/server. ## Diarization v2: Improved Batch Speaker Diarization #### A new batch diarization model is available today via the `diarize_model` API parameter. Deepgram is rolling out v2 of our batch speaker diarization model. v2 is a new architecture available today on an opt-in basis through the new `diarize_model` parameter. In side-by-side human evaluation, v2 was preferred 3.3× over our current production diarizer (v1), with the largest gains on contact-center audio — median CER reduced roughly 80% compared to the prior version of the diarization model. Customers using `diarize=true` are unaffected. **Key Features:** - **New `diarize_model` parameter** — A single parameter that both enables diarization and selects the version. Most customers should choose `latest`; `v2` or `v1` are also accepted. - **`diarize_model=latest` auto-upgrades** — Resolves to the newest GA diarizer. Today that's v2. - **No breaking changes** — `diarize=true` continues to route to v1. - **Compatible with the rest of the platform** — Works with Nova-1, Nova-2, Nova-3, enhanced, and base batch models (async and sync), monolingual and multilingual, alongside existing batch features. **New `diarize_model` parameter:** The new `diarize_model` parameter enables diarization and selects the model version in a single parameter — no need to also set `diarize=true`: ``` https://api.deepgram.com/v1/listen?model=nova-3&diarize_model=latest ``` | Value | Description | |---|---| | `latest` | Resolves to the newest GA diarizer | | `v2` | New improved batch diarizer | | `v1` | Original production diarizer | **Migration guidance:** - **New integrations**: For new projects we recommend `diarize_model=latest`. To pin a specific version, use `diarize_model=v2` or `diarize_model=v1`. - **Existing `diarize=true` users:** No breaking changes — your existing requests continue to work with v1. To pick up v2's improvements, update your requests to `diarize_model=latest` (always newest) or `diarize_model=v2`. We recommend testing on a representative sample of your audio before flipping production traffic. **No pricing changes.** Diarization continues to be included at current rates. ### Availability - Available now on the `/v1/listen` endpoint, on both US-hosted and EU-hosted endpoints - Supported on Nova-1, Nova-2, Nova-3, enhanced, and base batch models (async and sync), monolingual and multilingual - Streaming: `diarize_model` is not accepted on streaming requests and returns `400`. Use `diarize=true` for streaming diarization. Streaming improvements ship separately. - Self-hosted support is now available. See [Batch Diarization v2 Model Delivery for Self-Hosted Deployments](/changelog#2026-05-14-batch-diarization-v2-model-delivery-for-new-self-hosted-deployments) for details. Learn more in the [Speaker Diarization documentation](/docs/diarization). ## Nova-3 Portuguese Model Update #### Improved Nova-3 Portuguese Model We’ve enhanced the Nova-3 Portuguese model with improved transcription accuracy across Portuguese language variants, including Brazilian Portuguese (`pt-BR`) and European Portuguese (`pt-PT`). To use the updated model, set `model="nova-3"` and use one of the supported Portuguese language codes: - `language="pt"` - `language="pt-BR"` - `language="pt-PT"` Learn more about Nova-3 and supported languages on the [Models and Language Overview](https://developers.deepgram.com/docs/models-languages-overview) page.