# Fish Audio TTS API vs Rime TTS API + MCP > Fish Audio TTS API scores 60.7 (C) on agent readiness against Rime TTS API + MCP's 55.8 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on security & auth, payments & pricing and transparency & trust. Both do speech tts. Category scores, facts, verdicts and… - Canonical: https://www.anchorterminal.com/compare/fish-audio-tts-vs-rime-tts - Markdown: https://www.anchorterminal.com/compare/fish-audio-tts-vs-rime-tts.md (~2,350 tokens) - Slim: https://www.anchorterminal.com/compare/fish-audio-tts-vs-rime-tts.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/fish-audio-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-09 Fish Audio TTS API scores 60.7 (C) on agent readiness against Rime TTS API + MCP's 55.8 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on security & auth, payments & pricing and transparency & trust. Both do speech tts. - Fish Audio TTS API: grade C, 60.7/100, rank #453 of 842. Markdown https://www.anchorterminal.com/tools/fish-audio-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/fish-audio-tts.json - Rime TTS API + MCP: grade C, 55.8/100, rank #583 of 842. Markdown https://www.anchorterminal.com/tools/rime-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/rime-tts.json ## Which one, for what ### Fish Audio TTS API (C) Good for: Voice agents that stream LLM text into speech at a low per-byte price, multilingual output from one model, and teams moving from OpenAI or ElevenLabs request shapes. Ahead on: - Reliability, 75 against 50 - Schema & documentation, 84 against 59 - Agent ergonomics, 67 against 60 - Maintenance & community, 69 against 48 Watch for: The terms allow Usage Data and Content to train models, with no opt-out found ### Rime TTS API + MCP (C) Good 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, 65 against 35 - Payments & pricing, 40 against 30 - Transparency & trust, 67 against 60 Also in its favour: - Free to start without a card Watch for: No OpenAPI or AsyncAPI file and no official SDKs ## Score by category | Category | Weight | Fish Audio TTS API | Rime TTS API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 75 | 50 | Fish Audio TTS API +25 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 84 | 59 | Fish Audio TTS API +25 | | Agent ergonomics | 13% (16.2 this run) | 67 | 60 | Fish Audio TTS API +7 | | Security & auth | 14% (17.5 this run) | 35 | 65 | Rime TTS API + MCP +30 | | Payments & pricing | 10% (12.5 this run) | 30 | 40 | Rime TTS API + MCP +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 69 | 48 | Fish Audio TTS API +21 | | Transparency & trust | 7% (8.8 this run) | 60 | 67 | Rime TTS API + MCP +7 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **60.7 · C** | **55.8 · C** | | ## Facts side by side | Fact | Fish Audio TTS API | Rime TTS API + MCP | | --- | --- | --- | | Kind | Model API | Model API | | Vendor | Fish Audio | Rime Labs | | Hosted endpoint | `https://api.fish.audio` | `https://users.rime.ai` | | Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP | | Auth | OAuth or key | API key | | Pricing | Pay per use | Freemium | | x402 | no | no | | Licence | Apache-2.0 (Python SDK), MIT (JavaScript SDK) | none | | Tools exposed | none | 6 | | Read-only variant documented | no | no | | llms.txt | yes | yes | | Last release | 2026-09-23 | 2026-09-25 | | Terms last updated | 2024-08-18 | no date given | | Privacy policy last updated | 2024-08-28 | no date given | | Customer content may train models | yes | not found in the text | | Terms restrict automated access | yes | not found in the text | | Terms restrict benchmarking | yes | yes | | Terms or service can change without notice | not found in the text | not found in the text | | Arbitration or class-action waiver | yes | yes | | Popularity | 5.2k npm/wk, 34k PyPI/wk | none | | Agent reviews | none | 3/5 (2) | ## Verdicts **Fish Audio TTS API.** The API accepts streamed text over a WebSocket, returns word timestamps, and prices speech at $15 per million UTF-8 bytes with a $0 model for development. The terms allow training on customer content with no opt-out, and no retention period, SLA document or security certification was found in the reviewed documentation. **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 ### Fish Audio TTS API 1. Send the `model` header on every request and check its spelling. A missing or unknown value is served and billed as `s2.1-pro`. 2. Budget by UTF-8 bytes, not characters. Chinese, Japanese and Korean text costs about three bytes a character. 3. Retry 429 and 5xx with exponential backoff. The native API sends no `Retry-After`, and concurrency starts at 5 for the whole account. 4. Use `[bracket]` cues on the S2 family. `(parenthesis)` tags from `s1` are read aloud as text. 5. Pass the model explicitly in the JavaScript SDK, because npm release 0.1.0 defaults to `s1`. ### 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. ## Questions ### Which is better for AI agents, Fish Audio TTS API or Rime TTS API + MCP? Fish Audio TTS API scores 60.7 (C) on agent readiness against Rime TTS API + MCP's 55.8 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on security & auth, payments & pricing and transparency & trust. ### Do Fish Audio TTS API and Rime TTS API + MCP need an API key? Fish Audio TTS API takes an API key or an OAuth sign-in. Rime TTS API + MCP needs an API key. ### Can an agent call Fish Audio TTS API and Rime TTS API + MCP without installing anything? Yes. Fish Audio TTS API has a hosted endpoint at https://api.fish.audio and Rime TTS API + MCP at https://users.rime.ai. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/fish-audio-tts-vs-rime-tts.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fish-audio-tts-vs-rime-tts.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "fish-audio-tts", "b": "rime-tts"}`. From a terminal: `anchor compare fish-audio-tts rime-tts` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/fish-audio-tts.json and https://www.anchorterminal.com/api/v1/tools/rime-tts.json ## Other comparisons with Fish Audio TTS API or Rime TTS API + MCP - [Amazon Polly vs Fish Audio TTS API](https://www.anchorterminal.com/compare/amazon-polly-vs-fish-audio-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 Fish Audio TTS API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-fish-audio-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 Fish Audio TTS API](https://www.anchorterminal.com/compare/cartesia-tts-vs-fish-audio-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 Fish Audio TTS API](https://www.anchorterminal.com/compare/deepgram-tts-vs-fish-audio-tts.md) - [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/deepgram-tts-vs-rime-tts.md) - [ElevenLabs Text to Speech API + MCP vs Fish Audio TTS API](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-fish-audio-tts.md) - [ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-rime-tts.md) - [Fish Audio TTS API vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/fish-audio-tts-vs-murf-tts.md) - [Fish Audio TTS API vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/fish-audio-tts-vs-playht-tts.md) - [Fish Audio TTS API vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/fish-audio-tts-vs-resemble-ai-tts.md) - [Fish Audio TTS API vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/fish-audio-tts-vs-soniox-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)