# Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP

> Deepgram Text-to-Speech (Aura-2, Flux TTS) has a score of 73 (BB) against Rime TTS API + MCP's 56.1 (C). Both do speech tts. The largest gap is schema & documentation, 36 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/deepgram-tts-vs-rime-tts
- Markdown: https://www.anchorterminal.com/compare/deepgram-tts-vs-rime-tts.md (~1,750 tokens)
- Slim: https://www.anchorterminal.com/compare/deepgram-tts-vs-rime-tts.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/deepgram-tts-vs-rime-tts.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

Deepgram Text-to-Speech (Aura-2, Flux TTS) has a score of 73 (BB) against Rime TTS API + MCP's 56.1 (C). Both do speech tts. The largest gap is schema & documentation, 36 points.

- Deepgram Text-to-Speech (Aura-2, Flux TTS): grade BB, 73/100, rank #63 of 452. Markdown https://www.anchorterminal.com/tools/deepgram-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/deepgram-tts.json
- Rime TTS API + MCP: grade C, 56.1/100, rank #305 of 452. Markdown https://www.anchorterminal.com/tools/rime-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/rime-tts.json

## Which one, for what

Pick Deepgram Text-to-Speech (Aura-2, Flux TTS) for reliability (+20), schema & documentation (+36), agent ergonomics (+22), security & auth (+5), maintenance & community (+25).

Pick Rime TTS API + MCP for nothing in particular (no category where it leads by five points or more).

## Score by category

| Category | Weight | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Rime TTS API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 50 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 95 | 59 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +36 |
| Agent ergonomics | 13% (16.2 this run) | 82 | 60 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +22 |
| Security & auth | 14% (17.5 this run) | 70 | 65 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +5 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 48 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +25 |
| Transparency & trust | 7% (8.8 this run) | 75 | 71 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **73 · BB** | **56.1 · C** | |

## Facts side by side

| Fact | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Rime TTS API + MCP |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Deepgram | Rime Labs |
| Hosted endpoint | `https://api.deepgram.com/v1` | `https://users.rime.ai` |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | none |
| Tools exposed | none | 6 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-29 | 2026-09-25 |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |

## Verdicts

**Deepgram Text-to-Speech (Aura-2, Flux TTS).** OpenAPI 3.1 and AsyncAPI files, llms.txt and Markdown pages. Requests can be kept for training unless each one sets `mip_opt_out=true`.

**Rime TTS API + MCP.** Only character counts are kept by default, and customer data isn't used for training without an opt-in. No OpenAPI or AsyncAPI file and no official SDKs.

## Before you call either

### Deepgram Text-to-Speech (Aura-2, Flux TTS)

1. Set `mip_opt_out=true` on every request if the text mustn't be kept for training.
2. Split Aura-2 REST text under 2,000 characters or expect a 413.
3. Pass `model` on `/v2/speak`, where it's required.
4. Strip SSML before sending, since it's removed with an `INPUT_MARKUP_STRIPPED` warning.
5. Back off exponentially on 429 and keep traffic in one project.

### Rime TTS API + MCP

1. Always send `modelId`, since a missing one routes to Mist v3 and Coda speakers then fail.
2. Keep HTTP requests under 1,000 characters or use the WebSocket.
3. Back off on 429 before reopening a WebSocket, and remember each retry bills again.
4. Use `/ws3` when you need word timestamps.
5. Keep the key server-side, since WebSockets take it in a header and there are no short-lived tokens.

## Other comparisons with Deepgram Text-to-Speech (Aura-2, Flux TTS) or Rime TTS API + MCP

- [Amazon Polly vs Deepgram Text-to-Speech (Aura-2, Flux TTS)](https://www.anchorterminal.com/compare/amazon-polly-vs-deepgram-tts.md)
- [Amazon Polly vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/amazon-polly-vs-rime-tts.md)
- [Azure AI Speech text-to-speech vs Deepgram Text-to-Speech (Aura-2, Flux TTS)](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-deepgram-tts.md)
- [Azure AI Speech text-to-speech vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-rime-tts.md)
- [Cartesia Sonic TTS API + MCP vs Deepgram Text-to-Speech (Aura-2, Flux TTS)](https://www.anchorterminal.com/compare/cartesia-tts-vs-deepgram-tts.md)
- [Cartesia Sonic TTS API + MCP vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/cartesia-tts-vs-rime-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs ElevenLabs Text to Speech API + MCP](https://www.anchorterminal.com/compare/deepgram-tts-vs-elevenlabs-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/deepgram-tts-vs-murf-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/deepgram-tts-vs-playht-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/deepgram-tts-vs-resemble-ai-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/deepgram-tts-vs-soniox-tts.md)
- [ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-rime-tts.md)
- [Murf TTS API + MCP vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/murf-tts-vs-rime-tts.md)
- [PlayHT Text-to-Speech API vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/playht-tts-vs-rime-tts.md)
- [Resemble AI Text-to-Speech API vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/resemble-ai-tts-vs-rime-tts.md)
- [Rime TTS API + MCP vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/rime-tts-vs-soniox-tts.md)