# MiniMax Speech (T2A) vs Soniox Text-to-Speech

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

- Canonical: https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts
- Markdown: https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts.md (~4,900 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Soniox Text-to-Speech scores 70.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 6 of 7 scored categories. Both do text-to-speech.

- MiniMax Speech (T2A): grade C, 55.1/100, rank #884 of 1510. Markdown https://www.anchorterminal.com/tools/minimax-speech.md · JSON https://www.anchorterminal.com/api/v1/tools/minimax-speech.json
- Soniox Text-to-Speech: grade BB, 70.5/100, rank #199 of 1510. Markdown https://www.anchorterminal.com/tools/soniox-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/soniox-tts.json
- Best text-to-speech APIs for AI agents: https://www.anchorterminal.com/best/text-to-speech/index.md
- All 148 tts comparisons: https://www.anchorterminal.com/compare/text-to-speech/index.md

## Which one, for what

### MiniMax Speech (T2A) (C)

Good for: Multilingual speech for narration and agents at mid-range prices, with strong Chinese voices by the vendor's account.

Also in its favour:
- No incidents deducted, where Soniox Text-to-Speech loses 3 points for them

Watch for: No free allowance for synthesis and no official SDK

### Soniox Text-to-Speech (BB)

Good for: Multilingual agents that need any voice in any of 60-plus languages, short turns and strict data handling.

Ahead on:
- Reliability, 87 against 75
- Agent ergonomics, 78 against 56
- Security & auth, 87 against 36
- Maintenance & community, 63 against 38
- Transparency & trust, 73 against 65

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

Watch for: Audio stops at 2 minutes per request or stream and the cap can't be raised


## Why the edge

### Security & auth: Soniox Text-to-Speech +51

- 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.
- Soniox Text-to-Speech (87): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Project API keys now carry permissions per resource (TTS real-time, cloned voices, usage, model listing, temporary keys, with read and write levels), a missing permission returns 403 `permission_denied`, and an organisation API key can list, create and delete project keys. Temporary keys for browsers expire and are scoped to a `usage_type` (30; was 25). Soniox says audio and text are never used to improve its models (20). Nothing is stored unless you ask, and logs carry no content (15). Per-request usage logs record model, duration, tokens and the client reference id, readable through `GET /v1/usage-logs`, as soniox-stt reads them (10 of 15; was 5). SOC 2 Type 2, ISO/IEC 27001:2022 and HIPAA listed on the security page. The Python SDK's SECURITY.md (since May 2026) gives a disclosure route by email, GitHub, a maintainer or Discord. soniox.com/.well-known/security.txt answers 404 and no bug bounty was found (12 of 20; was 10). 30 + 20 + 15 + 10 + 12 = 87.

### Maintenance & community: Soniox Text-to-Speech +25

- 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.
- Soniox Text-to-Speech (63): Read as a model, on the lines deepgram-tts and cartesia-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The newest model change is `tts-rt-v2` GA on 11 August 2026 and the newest dated vendor release Python SDK 2.10.0 on 2 October, 31 days before 2 November (20). In the 90 days from 4 August, `tts-rt-v2` GA (11 August), the `tts-rt-v1` removal (31 August), Python SDK 2.9.0 (11 August) and 2.10.0 (2 October), and the JavaScript SDK tag v2026.08.11 (10 August, counted half) (10; was 0). `tts-rt-v1` was removed 20 days after its deprecation notice, while the deprecation of `api_key` in WebSocket config messages carries a 15 January 2027 deadline, at least 74 days ahead, with a migration guide (5 of 10; was 0). The models page and a support channel, untested (5 of 15). SDK issues couldn't be read because GitHub's pages answered 403 (3 of 10). SDKs for Python, Node, the web and React (15). The Python SDK has a test suite and lock file, but its CI file sits in `.github/` rather than `.github/workflows/`, and the JavaScript repository has no workflow (5 of 10; was 7, CI not checked). 20 + 10 + 5 + 5 + 3 + 15 + 5 = 63.

### Agent ergonomics: Soniox Text-to-Speech +22

- 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.
- Soniox Text-to-Speech (78): API reading of the checklist. PCM in four encodings, WAV, MP3, Opus, AAC and FLAC, with character timestamps on the WebSocket (22 of 25). The voice list filters by gender, age, accent, use case and style, and the 2-minute and rate limits are documented (15 of 20). Machine-readable `error_type` values an agent can branch on (20). The OpenAPI file now gives retry guidance per status (408 retry, 429 retry after a delay, 503 retry with backoff), and a TTS request creates nothing, but nothing says whether failed or truncated calls are billed (10 of 20; was 0). Model, language, voice, format and text are all set per request. SDKs for Python, Node, the web and React (11 of 15). 22 + 15 + 20 + 10 + 11 = 78.

### Reliability: Soniox Text-to-Speech +12

- MiniMax Speech (T2A) (75): Atlassian Statuspage at status.minimax.io with a Text-to-Speech component (20). Its history, re-read on 6 November, shows three incidents in the 90 days from 8 August, all titled elevated errors and labelled major, 22 minutes on 28 September, 3 minutes on 16 October and 2 minutes on 19 October, and none in November. Elevated errors with no fuller scope are read as partial, as on minimax-api and minimax-voice-cloning, so minor only (20). T2A is limited to 60 requests a minute, with higher limits on audio subscriptions (15). Error codes 1002 and 2045 say to retry later and avoid sudden increases, with no Retry-After or backoff figures (10 of 15). No SLA (0). No beta or preview label on T2A (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
- Soniox Text-to-Speech (87): Instatus page at status.soniox.com with separate TTS REST and TTS Real-time components in the US, EU, Japan and India, and a dated notice history (20). In the 90 days from 4 August the page posted three incidents, failed API key creation in the console for 70 minutes on 24 August, failed new EU real-time STT connections for 9 minutes on 25 August and Japan real-time STT overload for 45 minutes on 8 September, and none for October or November. None touches TTS, so the record is clean for this listing (30). Limits published, 100 requests a minute and 3 concurrent requests or streams, raisable in the console (15). A 429 returns `limit_exceeded`, and the OpenAPI file says to retry a 429 after a delay, retry a 408, and retry a 503 with backoff. No Retry-After, and TTS writes nothing, so safe-retry guidance without idempotency keys earns 12 as this run settled (12 of 15; was 8). No SLA found (0). `tts-rt-v2` is GA in all four regions (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.

### Transparency & trust: Soniox Text-to-Speech +8

- 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.
- Soniox Text-to-Speech (73): Closed service under terms updated 2026-06-29, Python SDK under Apache-2.0 (15). The security page, the terms and the TTS docs agree on no storage and no training, with async data deleted after 30 days (25 of 30). Model removals are dated on the models page with 20 days' notice for v1, and the WebSocket authentication change is dated to 15 January 2027 with a migration guide, but there is no written policy (12 of 20; was 10). Regional hosts in the US, EU, Japan and India and a data residency page, no sub-processor list found (12 of 20). 15 + 25 + 12 + 12 = 64.

## Score by category

| Category | Weight | MiniMax Speech (T2A) | Soniox Text-to-Speech | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 87 | Soniox Text-to-Speech +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 81 | 85 | Soniox Text-to-Speech +4 |
| Agent ergonomics | 13% (16.2 this run) | 56 | 78 | Soniox Text-to-Speech +22 |
| Security & auth | 14% (17.5 this run) | 36 | 87 | Soniox Text-to-Speech +51 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 38 | 63 | Soniox Text-to-Speech +25 |
| Transparency & trust | 7% (8.8 this run) | 65 | 73 | Soniox Text-to-Speech +8 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **55.1 · C** | **70.5 · BB** | |

## Facts side by side

| Fact | MiniMax Speech (T2A) | Soniox Text-to-Speech |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | MiniMax | Soniox |
| Hosted endpoint | no (local only) | `https://tts-rt.soniox.com` |
| Transports | HTTP, websocket | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for text-to-speech | not published | $0.0117 per minute of audio |
| x402 | no | no |
| Licence | none | Apache-2.0 (Python SDK) |
| Tools exposed | 0 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-01-23 | 2026-10-02 |
| Terms last updated | couldn't be read | 2026-06-29 |
| Privacy policy last updated | couldn't be read | 2026-06-29 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 12 stars, 22k npm/wk |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### MiniMax Speech (T2A)

No score change since it was listed.

### Soniox Text-to-Speech

- +6.8 on 2 November 2026 (B to BB): product, new evidence, negative event
- -0.2 on 8 October 2026: checklist

## Verdicts

**MiniMax Speech (T2A).** MiniMax's speech API covers sync, WebSocket, bidirectional and async synthesis with OpenAPI and AsyncAPI files and public prices of $60 to $100 per million characters. Text-to-Speech had only short incidents in 90 days. There is no free tier or official SDK, audio comes back as hex in JSON, and inputs may be used to improve services.

**Soniox Text-to-Speech.** Content is not stored by default or used for training, keys carry per-resource permissions, an OpenAPI file covers the REST endpoint, and no TTS incident was posted in the 90 days to 2 November. Audio stops at two minutes per request, and Python SDK 2.10.0 removed public interfaces in a minor release without notice.

## Before you call either

### MiniMax Speech (T2A)

1. Keep sync requests under 10,000 characters and use the async API for longer text
2. Decode the hex `audio` field before saving, or stream for text over 3,000 characters
3. Check `base_resp.status_code` on every response, since errors arrive inside a 200
4. Stay under 60 requests a minute and back off on code 1002
5. Use speech-2.8-turbo for agents and HD only where quality matters, since HD costs two thirds more

### Soniox Text-to-Speech

1. Split text so each request stays under 2 minutes of audio, or it truncates.
2. Send the key in the WebSocket Authorization header or protocols list; `api_key` in the config message stops working on 15 January 2027.
3. Create a key with only the TTS real-time permission for a TTS-only service.
4. Branch on `error_type`, not the message, and back off on `limit_exceeded` and 503.
5. Pick the regional host (EU, Japan, India) that matches your data residency.

## Questions

### Which is better for AI agents, MiniMax Speech (T2A) or Soniox Text-to-Speech?

Soniox Text-to-Speech scores 70.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 6 of 7 scored categories.

### Do MiniMax Speech (T2A) and Soniox Text-to-Speech need an API key?

Both need an API key.

### Can an agent call MiniMax Speech (T2A) and Soniox Text-to-Speech without installing anything?

No hosted endpoint is listed for MiniMax Speech (T2A). Soniox Text-to-Speech has a hosted endpoint at https://tts-rt.soniox.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts.json, and with the fewest tokens: https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "minimax-speech", "b": "soniox-tts"}`. From a terminal: `anchor compare minimax-speech soniox-tts`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/minimax-speech.json and https://www.anchorterminal.com/api/v1/tools/soniox-tts.json

## Other comparisons with MiniMax Speech (T2A) or Soniox Text-to-Speech

- [Amazon Polly vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/amazon-polly-vs-minimax-speech.md)
- [Amazon Polly vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/amazon-polly-vs-soniox-tts.md)
- [Azure AI Speech text-to-speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.md)
- [Azure AI Speech text-to-speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-soniox-tts.md)
- [Cartesia Sonic TTS API + MCP vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/cartesia-tts-vs-minimax-speech.md)
- [Cartesia Sonic TTS API + MCP vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/cartesia-tts-vs-soniox-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech.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 MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-minimax-speech.md)
- [ElevenLabs Text to Speech API + MCP vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-soniox-tts.md)
- [Fish Audio TTS API vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/fish-audio-tts-vs-minimax-speech.md)
- [Fish Audio TTS API vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/fish-audio-tts-vs-soniox-tts.md)
- [Google Cloud Text-to-Speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.md)
- [Google Cloud Text-to-Speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/google-cloud-tts-vs-soniox-tts.md)
- [HeyGen Voice vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/heygen-voice-vs-minimax-speech.md)
- [HeyGen Voice vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/heygen-voice-vs-soniox-tts.md)
- [Inworld Realtime TTS-2 vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/inworld-tts-vs-minimax-speech.md)
- [Inworld Realtime TTS-2 vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/inworld-tts-vs-soniox-tts.md)
- [MiniMax Speech (T2A) vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/minimax-speech-vs-murf-tts.md)
- [MiniMax Speech (T2A) vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.md)
- [MiniMax Speech (T2A) vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/minimax-speech-vs-resemble-ai-tts.md)
- [MiniMax Speech (T2A) vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/minimax-speech-vs-rime-tts.md)
- [MiniMax Speech (T2A) vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/minimax-speech-vs-smallest-lightning-tts.md)
- [Murf TTS API + MCP vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/murf-tts-vs-soniox-tts.md)
- [PlayHT Text-to-Speech API vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/playht-tts-vs-soniox-tts.md)
- [Resemble AI Text-to-Speech API vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/resemble-ai-tts-vs-soniox-tts.md)
- [Rime TTS API + MCP vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/rime-tts-vs-soniox-tts.md)
- [Smallest.ai Lightning TTS vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/smallest-lightning-tts-vs-soniox-tts.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp