Head to head · Text-to-speech · October 2026 research run
Rime TTS API + MCP vs Soniox Text-to-Speech
Soniox Text-to-Speech scores 71.8 (BB) on agent readiness against Rime TTS API + MCP's 57.3 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on payments & pricing and maintenance & community. Both do text-to-speech.
Best text-to-speech APIs for AI agents · All 148 tts comparisons
Which one, for what
Best for English and a handful of other languages in live voice agents where the operator cares most about data terms and price.
Ahead on
- Payments & pricing, 60 against 30
- Maintenance & community, 70 against 63
Also in its favour
- Free to start without a card
Watch for
No OpenAPI file read, and the official SDKs are all 0.1.0 alpha
Best for Multilingual agents that need any voice in any of 60-plus languages, short turns and strict data handling.
Ahead on
- Reliability, 87 against 47
- Schema & documentation, 85 against 59
- Agent ergonomics, 78 against 60
- Security & auth, 87 against 59
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Audio stops at 2 minutes per request or stream and the cap can't be raised
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Soniox Text-to-Speech +40
Rime TTS API + MCP 47
status.rime.ai now redirects to www.rimestat.us, an incident.io page with a Text-to-speech API component and history since 30 August 2026 (20, was 10). Its feed lists two incidents in the 90 days from 6 August, "Text-to-speech APIs are partially degraded" on 3 and 5 September, both partial. The window before 30 August can't be read, and this run gives no credit for an unread part of the window, so the line keeps its recorded award (5). The errors page says synthesis concurrency depends on the plan and points to the pricing page, which on 4 November lists the Free, Flex, Scale and Enterprise plans with no concurrency or rate figure, and the WebSocket connection limit isn't published. The Starter figure of 20 concurrent generations is gone (0, was 10). The errors page says to back off on 429 and retry the upgrade after a delay, marks 500 and 502 as retryable and warns that retries bill as new synthesis. Synthesis writes nothing, so safe-retry guidance without idempotency keys earns 12 in this run, as soniox-tts, fish-audio-tts and rime-prism (12, was 15). SLAs are an Enterprise item, none published (0). Coda and Mist v3 are GA (10). 20+5+0+12+0+10 = 47.
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.
Payments & pricing Rime TTS API + MCP +30
Rime TTS API + MCP 60
No x402, MPP or L402 (0). Per-minute prices published without a login, Mist v3 $0.030 and Coda v2 $0.050 a minute on Flex, $0.024 and $0.040 on Scale, metered by characters at about 1,000 a minute (20). Every account gets $50 of usage a month on the Free plan with no card (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Soniox Text-to-Speech 30
No x402, MPP or L402 (0). Token prices published without a login, $4.00 per 1M input tokens and $21.50 per 1M output tokens, which Soniox puts at about $0.70 an hour, re-read on 2 November (20). No free credits for new accounts found (0). A person signs up and funds the account in a browser; the new organisation API needs an organisation key from that account (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Security & auth Soniox Text-to-Speech +28
Rime TTS API + MCP 59
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key per request, sent as a header on WebSockets too, with no scopes or short-lived tokens, so browser apps need a server bridge (20 of 30). The terms effective 29 October 2026 (section 6.3(b)) grant Rime a perpetual licence to train its models on Free Plan customer data, excluding voice recordings and audio with a natural person's voice, with no opt-out found. Paid plans aren't covered by that licence, and the privacy policy says customer data isn't used for training unless agreed (10, was 20). Only character counts are kept by default, and request retention for support is an off-by-default dashboard switch since 2026-08-25 (15). No per-call log found (0 of 15). SOC 2 Type II since May 2025, HIPAA since February 2024 with an audit in March 2026, and a formal vulnerability disclosure programme linked from the security page. No security.txt or bug bounty, the same reading as rime-prism (14 of 20, was 10). 20+10+15+0+14 = 59.
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.
Schema & documentation Soniox Text-to-Speech +26
Rime TTS API + MCP 59
No OpenAPI file (0). The Coda Protobuf quickstart says the rime-api package on PyPI carries text_to_speech.proto and text_to_speech.asyncapi.yaml, but pypi.org didn't resolve on 4 November, so the files weren't read and the line stays at 0 as never read. llms.txt with Markdown pages (10). The models page says which model suits what, and that a request without modelId goes to Mist v3 (15 of 20). Parameters are typed in reference tables (10 of 15). Examples on each endpoint and an errors page listing the messages for each status, as plain text (12 of 15). Dated changelog and versioned WebSocket paths (/ws3, /ws2), no API version header (12 of 15). 0+10+15+10+12+12 = 59.
Soniox Text-to-Speech 85
Soniox now publishes an OpenAPI 3.1.0 file at docs.soniox.com/openapi.yaml (last modified 1 November 2026) covering POST /tts, TTS models, shared voices, cloned voices, usage logs and the organisation API; the WebSocket API has no AsyncAPI file (25; was 0). llms.txt and .mdx pages, now on docs.soniox.com (10). The models page and concept guides explain the 2-minute cap, audio tags and voices, but say little about when not to use the API (14 of 20). The spec lists required fields and length limits for /tts, but audio_format, voice and language are free strings with no enum (11 of 15). One error format across surfaces with a stable error_type, a request_id and a more_info link, and the spec lists each status's messages with examples (15). Model versions and their deprecation are dated on the models page, which stands in for a changelog (10 of 15). 25 + 10 + 14 + 11 + 15 + 10 = 85.
Agent ergonomics Soniox Text-to-Speech +18
Rime TTS API + MCP 60
API reading of the checklist. MP3, WAV, Opus, PCM and mu-law from 8 to 96 kHz, chosen by Accept, with word timestamps on /ws3 (22 of 25). HTTP requests stop at 1,000 characters and the WebSocket buffers by sentence, but no voice-list paging or filters found in the API (12 of 20). Errors are plain-text messages, 11 for validation and 5 for auth, with no machine-readable codes, and WebSocket failures arrive as close code 1011 with the reason in a string (12 of 20). Clear retry guidance, and the docs say retries are billed (10 of 20). Two required fields, but the default model breaks Coda speakers. The Rime SDK now has TTS clients in Python, Node.js, Go and Rust that require the model, all 0.1.0 alpha releases. Partly met, so the earlier 4 is kept and flagged (4 of 15).
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.
Maintenance & community Rime TTS API + MCP +7
Rime TTS API + MCP 70
Read as a model, on the lines cartesia-tts and fish-audio-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The changelog's newest entry is on-prem release 20261104 for Coda v2 and Mist v3 on 4 November 2026 (30). In the 90 days from 6 August, text-to-speech entries on 15 August, 25 August, 12 September, 25 September, 13 October, 28 October and 4 November, and SDK releases touching the TTS client (10). The terms of 29 October promise at least 30 days' notice before retiring a Model Version used on a paid plan, while Arcana's cloud retirement came 17 days after its 29 July notice (5 of 10, was 0). Public changelog with RSS and a support address (8 of 15). The SDK repository's issues couldn't be read (github.com answers 403), so the line stays absent (0). Official Rime SDKs in Python, Node.js, Go and Rust with TTS clients, newest python-v0.1.0-alpha.29 on 3 November, all alpha, read as rime-prism reads the same SDK (12 of 15, was 0). The SDK repository's checks workflow runs the tests with locked dependencies, results unread (5 of 10, was 0). 30+10+5+8+0+12+5 = 70.
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.
Score by category
| Category | Weight | Rime TTS API + MCP | Soniox Text-to-Speech | Edge |
|---|---|---|---|---|
| Reliability | 16% | 47 | 87 | Soniox Text-to-Speech +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 85 | Soniox Text-to-Speech +26 |
| Agent ergonomics | 13% | 60 | 78 | Soniox Text-to-Speech +18 |
| Security & auth | 14% | 59 | 87 | Soniox Text-to-Speech +28 |
| Payments & pricing | 10% | 60 | 30 | Rime TTS API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 63 | Rime TTS API + MCP +7 |
| Transparency & trust | 7% | 76 | 73 | Rime TTS API + MCP +3 |
| Negative events | ≤15 | -2 | -3 | |
| Total | C 57.3/100 | BB 71.8/100 |
Facts side by side
| Fact | Rime TTS API + MCP | Soniox Text-to-Speech |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Rime Labs | Soniox |
| Hosted endpoint | https://users.rime.ai | https://tts-rt.soniox.com |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | 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 | 6 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-10-02 |
| Terms last updated | no date given | 2026-06-29 |
| Privacy policy last updated | no date given | 2026-06-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 12 stars, 22k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Rime TTS API + MCP | Soniox Text-to-Speech |
|---|---|---|
| LedgerCost analyst | 3/5 $30 or $50 per 1M characters, and a free allowance stated twice | 3/5 About $11.70 per 1,000 minutes of speech, token-billed |
| SprintLatency and reliability tester | 3/5 Retries bill as new synthesis, and the docs say so | 3/5 Audio stops at 2 minutes and the cap can't move |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
What the same task costs
| Task | Rime TTS API + MCP | Soniox Text-to-Speech |
|---|---|---|
| Narrate ten minutes of speech10 minutes of generated audio | $0.24 to $0.50 | $0.12 |
Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.
How the scores have moved
Verdicts
Rime TTS API + MCP
Per-minute prices are public, $50 of free usage a month needs no card, and official SDKs now cover four languages, all alpha. Terms from 29 October 2026 license training on Free plan data while the security page says Rime never trains on customer audio or text, and no rate figure is published.
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
Rime TTS API + MCP
- Always send
modelId, since a missing or unknown one routes to Mist v3 and Coda speakers then fail. - Keep HTTP requests under 1,000 characters or use the WebSocket.
- Back off on 429 before reopening a WebSocket, and remember each retry bills again.
- Use a paid plan for customer audio or text you don't want used for training, since the terms license Free plan data for it.
- Keep the key server-side, since WebSockets take it in a header and there are no short-lived tokens.
Soniox Text-to-Speech
- Split text so each request stays under 2 minutes of audio, or it truncates.
- Send the key in the WebSocket Authorization header or protocols list;
api_keyin the config message stops working on 15 January 2027. - Create a key with only the TTS real-time permission for a TTS-only service.
- Branch on
error_type, not the message, and back off onlimit_exceededand 503. - Pick the regional host (EU, Japan, India) that matches your data residency.
Questions
Which is better for AI agents, Rime TTS API + MCP or Soniox Text-to-Speech?
Soniox Text-to-Speech scores 71.8 (BB) on agent readiness against Rime TTS API + MCP's 57.3 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on payments & pricing and maintenance & community.
Do Rime TTS API + MCP and Soniox Text-to-Speech need an API key?
Both need an API key.
Can an agent call Rime TTS API + MCP and Soniox Text-to-Speech without installing anything?
Yes. Rime TTS API + MCP has a hosted endpoint at https://users.rime.ai and Soniox Text-to-Speech at https://tts-rt.soniox.com.
Other comparisons with Rime TTS API + MCP or Soniox Text-to-Speech
- Amazon Polly vs Rime TTS API + MCP
- Amazon Polly vs Soniox Text-to-Speech
- Azure AI Speech text-to-speech vs Rime TTS API + MCP
- Azure AI Speech text-to-speech vs Soniox Text-to-Speech
- Cartesia Sonic TTS API + MCP vs Rime TTS API + MCP
- Cartesia Sonic TTS API + MCP vs Soniox Text-to-Speech
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Soniox Text-to-Speech
- ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Soniox Text-to-Speech
- Fish Audio TTS API vs Rime TTS API + MCP
- Fish Audio TTS API vs Soniox Text-to-Speech
- Google Cloud Text-to-Speech vs Rime TTS API + MCP
- Google Cloud Text-to-Speech vs Soniox Text-to-Speech
- HeyGen Voice vs Rime TTS API + MCP
- HeyGen Voice vs Soniox Text-to-Speech
- Inworld Realtime TTS-2 vs Rime TTS API + MCP
- Inworld Realtime TTS-2 vs Soniox Text-to-Speech
- MiniMax Speech (T2A) vs Rime TTS API + MCP
- MiniMax Speech (T2A) vs Soniox Text-to-Speech
- Murf TTS API + MCP vs Rime TTS API + MCP
- Murf TTS API + MCP vs Soniox Text-to-Speech
- PlayHT Text-to-Speech API vs Rime TTS API + MCP
- PlayHT Text-to-Speech API vs Soniox Text-to-Speech
- Resemble AI Text-to-Speech API vs Rime TTS API + MCP
- Resemble AI Text-to-Speech API vs Soniox Text-to-Speech
- Rime TTS API + MCP vs Smallest.ai Lightning TTS
- Smallest.ai Lightning TTS vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/rime-tts-vs-soniox-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/rime-tts.json·/api/v1/tools/soniox-tts.json - From a terminal
anchor compare rime-tts soniox-tts(the CLI) - Over MCP
compare_tools {"a": "rime-tts", "b": "soniox-tts"}at/mcp, no key