# Deepgram Text-to-Speech (Aura-2, Flux TTS) vs MiniMax Speech (T2A) (slim)

> Deepgram Text-to-Speech scores 75.6 (BB) to MiniMax Speech's 55.1 (C) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech.md (~4,950 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech.json · canonical https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 75.6 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in every scored category. Both do text-to-speech.

- Deepgram Text-to-Speech (Aura-2, Flux TTS): BB 75.6, rank #58 of 1510 · https://www.anchorterminal.com/tools/deepgram-tts.min.md
- MiniMax Speech (T2A): C 55.1, rank #884 of 1510 · https://www.anchorterminal.com/tools/minimax-speech.min.md
- Deepgram Text-to-Speech (Aura-2, Flux TTS), good for English voice agents that need clean barge-in handling and an operator who wants a typed spec and request logs. Ahead on Reliability, 80 against 75; Schema & documentation, 95 against 81; Agent ergonomics, 82 against 56; Security & auth, 72 against 36; Payments & pricing, 40 against 20; Maintenance & community, 73 against 38; Transparency & trust, 78 against 65. Also Agent-ready, a grade of BB or better; A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.
- MiniMax Speech (T2A), good for Multilingual speech for narration and agents at mid-range prices, with strong Chinese voices by the vendor's account.

| Category | Deepgram Text-to-Speech (Aura-2, Flux TTS) | MiniMax Speech (T2A) |
| --- | --- | --- |
| Reliability (16%) | 80 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 95 | 81 |
| Agent ergonomics (13%) | 82 | 56 |
| Security & auth (14%) | 72 | 36 |
| Payments & pricing (10%) | 40 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 38 |
| Transparency & trust (7%) | 78 | 65 |

| Fact (where they differ) | Deepgram Text-to-Speech (Aura-2, Flux TTS) | MiniMax Speech (T2A) |
| --- | --- | --- |
| Vendor | Deepgram | MiniMax |
| Hosted endpoint | `https://api.deepgram.com/v1` | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP, websocket |
| Price for text-to-speech | $45 per 1M characters | not published |
| Licence | MIT (SDKs) | none |
| Tools exposed | none | 0 |
| Last release | 2026-10-28 | 2026-01-23 |
| Terms last updated | 2026-08-06 | couldn't be read |
| Privacy policy last updated | 2021-10-26 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Security & auth, Deepgram Text-to-Speech (Aura-2, Flux TTS) +36: Deepgram Text-to-Speech (Aura-2, Flux TTS) 72 (Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys belong to a project, carry a role and scopes, and browser JWTs live 30 seconds (30). Requests fall under the Model Improvement Program, which covers TTS, unless each request sets `mip_opt_out=true` (10 of 20). Opted-out requests are kept only for processing, so zero retention is self-serve but not the default (10 of 15). Per-request logs through `GET /v1/projects/{project_id}/requests`, no audit log of key actions found (10 of 15). SOC 2 Type 1 and Type 2, HIPAA with a BAA on request and PCI listed on the compliance page. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy or bug bounty found (12 of 20). 30 + 10 + 10 + 10 + 12 = 72.); MiniMax Speech (T2A) 36 (Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain API keys with no scopes found, and leaked keys may be disabled (20 of 30). The terms (effective 30 March 2026), as read for minimax-voice-cloning on 4 November, let MiniMax use input and generated content to operate, maintain, develop and improve its services, with no opt-out found, and the privacy policy rules out only training to profile or target consumers (5 of 20). The speech docs call every interface stateless, and no retention period for submitted text or generated audio was found (5 of 15). Responses carry `usage_characters` and a trace ID, with no audit log (6 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). Total 36.)
- Maintenance & community, Deepgram Text-to-Speech (Aura-2, Flux TTS) +35: Deepgram Text-to-Speech (Aura-2, Flux TTS) 73 (Read as a model. Changelog entries to 27 October 2026, the newest changing how callbacks, TTS callbacks included, are verified (30). 34 dated entries in the 90 days from 3 August (10). We found no deprecation policy and no TTS deprecation notices in the period (0 of 10). Public changelog and community support channels (10 of 15). The Python SDK had 27 open issues on 1 October, the newest from August 2026 with no maintainer reply visible, per the 1 October check, not re-read on 1 November (3 of 10). Official SDKs current in five languages, the Python SDK at 7.16.0 on 28 October (15). SDK CI not checked (5 of 10).); MiniMax Speech (T2A) 38 (Read as a model, as minimax-voice-cloning is. The newest dated change touching speech is the MCP servers' August update, `minimax-mcp-js` 0.0.18 on 21 August 2026, 77 days before 6 November, and Speech 2.8 dates from 23 January 2026 (20 of 30). No dated API entries in the last 90 days (0). Support by email and Discord, not tested (6 of 15). No official SDK for speech; the MCP servers expose `text_to_audio` and `list_voices` (8 of 15). The Python MCP server has tests and moved to version 2 of the MCP SDK in August, with no CI workflow (4 of 10). Total 38.)
- Agent ergonomics, Deepgram Text-to-Speech (Aura-2, Flux TTS) +26: Deepgram Text-to-Speech (Aura-2, Flux TTS) 82 (API reading of the checklist. Encoding, container, sample rate and bit rate are all chosen per request, streaming returns PCM, mu-law or A-law and batch adds MP3, Opus, FLAC and AAC. Word timestamps on Flux only (20 of 25). Aura-2 REST caps a request at 2,000 characters and answers 413 above it, and the request history endpoint pages and filters by date, status and endpoint (20). Documented error codes, an `INPUT_MARKUP_STRIPPED` warning when SSML is dropped, and Flux's Interrupt event returns what was spoken and what wasn't (17 of 20). Backoff guidance for 429. No idempotency key, and we found nothing on billing for failed calls (10 of 20). `/v1/speak` needs only the text, and official SDKs ship in Python, JavaScript, Go, .NET and Java (15).); MiniMax Speech (T2A) 56 (API reading of the checklist. Audio comes back hex-encoded inside JSON by default, with subtitles opt-in and format, bitrate and sample rate settable (15 of 25). Voices are listed by type through `POST /v1/get_voice`, which has no pagination and returns 300+ system voices for `all` (10 of 20). Errors come as numeric codes in `base_resp` with a short remedy for each, inside responses documented only as 200 (13 of 20). No idempotency key, and the MCP tools carry no read-only or destructive annotations (10 of 20). Two required fields. No official SDK for speech, with MCP servers in Python and JavaScript (8 of 15). Total 56.)
- Payments & pricing, Deepgram Text-to-Speech (Aura-2, Flux TTS) +20: Deepgram Text-to-Speech (Aura-2, Flux TTS) 40 (No x402, MPP or L402 (0). Per-1,000-character prices for Flux TTS, Aura-2 and Aura-1 published without a login (20). $200 credit with no card (20). A person signs up in a browser to get the first key (0).); MiniMax Speech (T2A) 20 (No x402, MPP or L402 (0). Per-character prices for every speech model published without a login (20). No free allowance for synthesis is published (0). A person signs up in a browser and funds a balance (0). Total 20.)
- Schema & documentation, Deepgram Text-to-Speech (Aura-2, Flux TTS) +14: Deepgram Text-to-Speech (Aura-2, Flux TTS) 95 (OpenAPI 3.1 file at developers.deepgram.com/openapi.json and an AsyncAPI file for the sockets (25). llms.txt and Markdown pages (10). The docs say to use Flux TTS for live agents that need barge-in and Aura-2 for other languages, though few options say when not to use them (15). `/v1/speak` has an `encoding` enum and a default model, `/v2/speak` requires `model`, and both are typed in the spec (15). Examples on each endpoint, a general errors page and a TTS troubleshooting page for WebSocket close codes such as NET-1000 (15). Versioned `/v1` and `/v2` paths and a changelog with entries most weekdays (15).); MiniMax Speech (T2A) 81 (OpenAPI 3.1 for the sync and async routes and AsyncAPI files for the WebSocket and bidirectional sockets (25). llms.txt and a Markdown copy of every page (10). The text field says when to stream and how to mark pauses, and guides separate sync, WebSocket and async use (15 of 20). Enums for model and audio settings, with `model` and `text` required (13 of 15). Examples throughout and the shared table of error codes, but the OpenAPI file documents only a 200 response (10 of 15). Versioned `/v1` paths. The API release notes stop at 28 October 2025, and the last T2A entry is 23 September 2025 (8 of 15). Total 81.)
- Transparency & trust, Deepgram Text-to-Speech (Aura-2, Flux TTS) +13: Deepgram Text-to-Speech (Aura-2, Flux TTS) 78 (Closed service with clear terms, SDKs MIT (15). The docs describe training by default under the Model Improvement Program and EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data sits on US servers and doesn't mention the program (15 of 30). Breaking corrections are flagged in the changelog, but we found no deprecation policy (10 of 20). Sub-processor list and four regional endpoints (20).); MiniMax Speech (T2A) 65 (Closed API with clear terms under Singapore law naming Nanonoble Pte. Ltd., and MIT MCP servers (15 of 30). Terms and privacy policy agree that inputs may be used to improve services and that data sits in a United States data centre, with no retention period, as on minimax-voice-cloning (8 of 30). The API release notes carry a dated legacy notice of 20 June 2025 for the old text-to-voice API with service continuing, and older speech models stay accepted, with no written policy or notice period (15 of 20). Data location stated as the United States and an EU representative named, third parties only by category (10 of 20). Total 48.)

| Task | Deepgram Text-to-Speech (Aura-2, Flux TTS) | MiniMax Speech (T2A) |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.13 to $0.41 | $0.54 to $0.90 |