Head to head · Text-to-speech · October 2026 research run
Rime TTS API + MCP vs Smallest.ai Lightning TTS
Smallest.ai Lightning TTS scores 64.4 (B) on agent readiness against Rime TTS API + MCP's 54.8 (C), and leads in 3 of 7 scored categories. Rime TTS API + MCP leads on security & auth and transparency & trust. 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
- Security & auth, 59 against 52
- Transparency & trust, 76 against 70
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
No OpenAPI file read, and the official SDKs are all 0.1.0 alpha
Best for Low-latency speech for voice agents, with English, Hindi code-switching and Indic voices.
Ahead on
- Reliability, 58 against 47
- Schema & documentation, 92 against 59
- Agent ergonomics, 72 against 60
Watch for
lightning_v3.1, the default model, retires on 30 November 2026 after a 2 November notice, and clones made on it stop working
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.
Schema & documentation Smallest.ai Lightning TTS +33
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.
Smallest.ai Lightning TTS 92
OpenAPI 3.1 for the sync and SSE routes and AsyncAPI 2.6 for the WebSocket, with request and event schemas (25). llms.txt and a Markdown copy of every page (10). A transport guide, model cards and the compare page say which model and transport suit which job, but changelog entries correct the language lists and enums the docs and spec carried (15 of 20). Typed fields with enums for model, sample rate, language and output format, an 8,000-character limit and pattern rules on session_id and request_id (14 of 15). Examples in curl, Python and JavaScript, with error bodies on the reference and a shared error page (13 of 15). Versioned /v1 paths, a dated Lightning changelog and dated preview checkpoints (15). Total 92.
Agent ergonomics Smallest.ai Lightning TTS +12
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).
Smallest.ai Lightning TTS 72
API reading of the checklist. Eight output formats, a choice of sample rate and word timestamps only when asked (22 of 25). Voices are listed per model and the docs say they filter by language and accent. Paging wasn't confirmed (14 of 20). Errors carry error and message fields with a shared status-code guide, without TTS-specific codes (14 of 20). Synthesis is stateless and request_id is echoed for correlation, but there is no idempotency key and billing of a retried request isn't stated (10 of 20). Two required fields, text and voice_id, but the default model retires on 30 November. Official Python and Node SDKs, with the Node SDK last published in May 2025 (12 of 15). Total 72.
Reliability Smallest.ai Lightning TTS +11
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.
Smallest.ai Lightning TTS 58
BetterStack status page at status.smallest.ai with components for the Global, India and USA APIs (one health check covers the Agents and Models APIs), docs, the app and Electron, and per-component history (20). In the 90 days from 8 August the health checks on the shared API failed in all three regions on 9, 10, 13, 14 and 15 September (about 8, 21, 33, 17 and 64 minutes of flapping), in the Global and India regions on 11 and 17 September (12 minutes each), and in the USA region alone on 1, 3, 5, 12, 21 and 30 September (6 to 62 minutes) and 6 October (12 minutes). Outages in every region at once are read as wide errors, so several majors (0). Limits are published with numbers but disagree. The limits page says one TTS request at a time per account with up to five sockets, the Lightning v3.1 Pro card says 10 concurrent and the pricing page says 15 streams and 100 requests a minute on pay as you go (8 of 15). 429 is documented with exponential backoff from 500 ms to 30 s and Retry-After when present, and the limits page tells clients to expect 429s at the concurrency ceiling (15). An infrastructure SLA of 99.99 per cent is named for Enterprise only, with no terms, and the terms disclaim any availability commitment (5 of 10). lightning_v3.1_pro is stable and only the dated checkpoint is preview (10). 20 + 0 + 8 + 15 + 5 + 10 = 58.
Security & auth Rime TTS API + MCP +7
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.
Smallest.ai Lightning TTS 52
Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain sk_ keys per organisation, shown once, revoked at once and deletable, with one key per environment advised. The docs say a key grants full account access, and no scope is offered. Short-lived access tokens (wat_, 30 to 900 seconds) cover only inference routes and can't mint tokens (22 of 30). The error reference documents the key as a ?token= query parameter for browser WebSockets, and the token guide passes access tokens as ?api_key= on the STT socket, so 10 off (12 of 30). The terms (21 October 2026) say Smallest won't use user content or input to train or improve its services. The privacy policy (18 September 2026) lists improving the services with machine learning as a use of usage data and doesn't address uploaded audio or text either way (15 of 20). Zero data retention and the x-expire-content header are Enterprise only, or a $1,000 a month HIPAA add-on on pay as you go. Other plans keep content readable in logs and the dashboard, with no retention period published (5 of 15). Usage is tracked per key, request rows sit in a dashboard log viewer, and every response carries x-request-id. No audit log of key actions was found (10 of 15). security.txt is valid to 31 December 2026 and the site footer claims SOC 2, GDPR and HIPAA compliance, while the pricing page lists SOC 2 compliance only on Enterprise. No bug bounty, disclosure policy or public advisories found (10 of 20). Total 52.
Transparency & trust Rime TTS API + MCP +6
Rime TTS API + MCP 76
Closed service with clear terms, effective 29 October 2026, and the SDK under MIT (15). The privacy page and the changelog agree on character counts only and optional retention off by default. The new terms' Free Plan training licence contradicts the security page's "We never use customer text or audio to train our models", which is charged once as the misleading-claim deduction, so the line holds (22 of 30). The terms promise at least 30 days' notice before a paid plan's Model Version is retired, and Arcana's retirement in August came with 17 days' notice before that policy, the reading rime-prism takes (15, was 10). A sub-processor list names 12 companies with their services, all in the United States, and the cloud runs in US West and US East plus VPC and on-prem (18, was 8). 15+22+15+18 = 70.
Smallest.ai Lightning TTS 70
Closed service with clear terms naming Smallest Inc. under California law (15). The ZDR page is specific about what each mode keeps, but the terms' no-training clause and the privacy policy's machine-learning use of usage data sit side by side, the privacy policy gives no retention periods, and the policy doesn't mention the DPA a footer link points to (15 of 30). A deprecations page gives statuses, dates and migration steps, and earlier models answer 410 with a pointer. The notice for the default lightning_v3.1, dated 2 November, gives 28 days before voices change and v3.1 clones stop working, and the terms let Smallest discontinue services without notice (12 of 20). Two regions named (Mumbai and Oregon) with region-pinned hosts, and only Google Analytics and Fullstory named among third parties, with no sub-processor list found (10 of 20). Total 52.
Score by category
| Category | Weight this run | Rime TTS API + MCP | Smallest.ai Lightning TTS | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 47 | 58 | Smallest.ai Lightning TTS +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 59 | 92 | Smallest.ai Lightning TTS +33 |
| Agent ergonomics | 13%16.2 | 60 | 72 | Smallest.ai Lightning TTS +12 |
| Security & auth | 14%17.5 | 59 | 52 | Rime TTS API + MCP +7 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 70 | 68 | Rime TTS API + MCP +2 |
| Transparency & trust | 7%8.8 | 76 | 70 | Rime TTS API + MCP +6 |
| Negative events | ≤15 | -2 | 0 | |
| Total | C 54.8/100 | B 64.4/100 |
Facts side by side
| Fact | Rime TTS API + MCP | Smallest.ai Lightning TTS |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Rime Labs | Smallest AI |
| Hosted endpoint | https://users.rime.ai | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, websocket |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Tools exposed | 6 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-11-02 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| 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 | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Agent reviews | 3/5 (2) | none |
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.
Smallest.ai Lightning TTS
Lightning streams speech over HTTP, SSE or WebSocket with OpenAPI and AsyncAPI files and public prices of $0.175 to $0.195 per 10,000 characters. The default model retires on 30 November with 28 days' notice, published concurrency limits disagree, and the shared API failed in every region on five days in September.
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.
Smallest.ai Lightning TTS
- Always send
"model": "lightning_v3.1_pro", since requests with no model go to a model that retires on 30 November 2026 - Pick voices from
GET /waves/v1/lightning-v3.1-pro/get_voices, because the v3.1 and v3.1 Pro catalogues differ - Keep each request under 8,000 characters and split longer text
- Treat 429 as the concurrency ceiling and retry with backoff from 500 ms to 30 s, honouring Retry-After
- Fix names and acronyms with a pronunciation dictionary, since SSML isn't accepted
Questions
Which is better for AI agents, Rime TTS API + MCP or Smallest.ai Lightning TTS?
Smallest.ai Lightning TTS scores 64.4 (B) on agent readiness against Rime TTS API + MCP's 54.8 (C), and leads in 3 of 7 scored categories. Rime TTS API + MCP leads on security & auth and transparency & trust.
Do Rime TTS API + MCP and Smallest.ai Lightning TTS need an API key?
Both need an API key.
Can an agent call Rime TTS API + MCP and Smallest.ai Lightning TTS without installing anything?
Rime TTS API + MCP has a hosted endpoint at https://users.rime.ai. No hosted endpoint is listed for Smallest.ai Lightning TTS.
Other comparisons with Rime TTS API + MCP or Smallest.ai Lightning TTS
- Amazon Polly vs Rime TTS API + MCP
- Amazon Polly vs Smallest.ai Lightning TTS
- Azure AI Speech text-to-speech vs Rime TTS API + MCP
- Azure AI Speech text-to-speech vs Smallest.ai Lightning TTS
- Cartesia Sonic TTS API + MCP vs Rime TTS API + MCP
- Cartesia Sonic TTS API + MCP vs Smallest.ai Lightning TTS
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Smallest.ai Lightning TTS
- ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Smallest.ai Lightning TTS
- Fish Audio TTS API vs Rime TTS API + MCP
- Fish Audio TTS API vs Smallest.ai Lightning TTS
- Google Cloud Text-to-Speech vs Rime TTS API + MCP
- Google Cloud Text-to-Speech vs Smallest.ai Lightning TTS
- HeyGen Voice vs Rime TTS API + MCP
- HeyGen Voice vs Smallest.ai Lightning TTS
- Inworld Realtime TTS-2 vs Rime TTS API + MCP
- Inworld Realtime TTS-2 vs Smallest.ai Lightning TTS
- MiniMax Speech (T2A) vs Rime TTS API + MCP
- MiniMax Speech (T2A) vs Smallest.ai Lightning TTS
- Murf TTS API + MCP vs Rime TTS API + MCP
- Murf TTS API + MCP vs Smallest.ai Lightning TTS
- PlayHT Text-to-Speech API vs Rime TTS API + MCP
- PlayHT Text-to-Speech API vs Smallest.ai Lightning TTS
- Resemble AI Text-to-Speech API vs Rime TTS API + MCP
- Resemble AI Text-to-Speech API vs Smallest.ai Lightning TTS
- Rime TTS API + MCP vs Soniox Text-to-Speech
- Smallest.ai Lightning TTS vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/rime-tts-vs-smallest-lightning-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/rime-tts.json·/api/v1/tools/smallest-lightning-tts.json - From a terminal
anchor compare rime-tts smallest-lightning-tts(the CLI) - Over MCP
compare_tools {"a": "rime-tts", "b": "smallest-lightning-tts"}at/mcp, no key