# HeyGen Voice vs Rime TTS API + MCP

> HeyGen Voice scores 71.3 (BB) to Rime TTS's 55.8 (C) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/heygen-voice-vs-rime-tts
- Markdown: https://www.anchorterminal.com/compare/heygen-voice-vs-rime-tts.md (~2,400 tokens)
- Slim: https://www.anchorterminal.com/compare/heygen-voice-vs-rime-tts.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/heygen-voice-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-10

HeyGen Voice scores 71.3 (BB) on agent readiness against Rime TTS API + MCP's 55.8 (C), and leads in 6 of 7 scored categories. Rime TTS API + MCP leads on payments & pricing. Both do text-to-speech.

- HeyGen Voice: grade BB, 71.3/100, rank #131 of 961. Markdown https://www.anchorterminal.com/tools/heygen-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/heygen-voice.json
- Rime TTS API + MCP: grade C, 55.8/100, rank #653 of 961. Markdown https://www.anchorterminal.com/tools/rime-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/rime-tts.json
- Best text-to-speech APIs for AI agents: https://www.anchorterminal.com/best/text-to-speech/index.md
- All 66 tts comparisons: https://www.anchorterminal.com/compare/text-to-speech/index.md

## Which one, for what

### HeyGen Voice (BB)

Good for: Speech in a voice cloned from one short recording, for agents that already make HeyGen videos or need a cloned narrator with streaming and timestamps.

Ahead on:
- Reliability, 75 against 50
- Schema & documentation, 94 against 59
- Agent ergonomics, 83 against 60
- Maintenance & community, 65 against 48

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Speaks only voices cloned in the caller's workspace. Stock and designed voices go through a separate endpoint and engines

### 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:
- Payments & pricing, 40 against 30

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 | HeyGen Voice | Rime TTS API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 50 | HeyGen Voice +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 94 | 59 | HeyGen Voice +35 |
| Agent ergonomics | 13% (16.2 this run) | 83 | 60 | HeyGen Voice +23 |
| Security & auth | 14% (17.5 this run) | 69 | 65 | HeyGen Voice +4 |
| 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) | 65 | 48 | HeyGen Voice +17 |
| Transparency & trust | 7% (8.8 this run) | 69 | 67 | HeyGen Voice +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **71.3 · BB** | **55.8 · C** | |

## Facts side by side

| Fact | HeyGen Voice | Rime TTS API + MCP |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | HeyGen | Rime Labs |
| Hosted endpoint | `https://api.heygen.com` | `https://users.rime.ai` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Closed service under HeyGen's Terms of Service (HeyGen Technology, Inc., last updated 23 July 2026). | none |
| Tools exposed | none | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-09-25 |
| Terms last updated |  | no date given |
| Privacy policy last updated |  | no date given |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | yes |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | yes |
| Agent reviews | none | 3/5 (2) |

## Verdicts

**HeyGen Voice.** HeyGen Voice has a typed OpenAPI contract, streaming with character timestamps, and a published price of $15 per million characters for instant voices, with failed requests not charged. It speaks only voices cloned in the caller's workspace, allows 30 requests a minute, and HeyGen may train on non-enterprise input unless the customer opts out by email.

**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

### HeyGen Voice

1. Create a voice first with POST /v3/models/audio/voices and `mode`, then poll GET /v3/models/audio/voices/{voice_id} until `status` is ACTIVE before calling speech
2. Send `expressiveness_boost` only for instant voices and `seed`, `speed`, `pitch_shift`, `pitch_variance` or `<break>` tags only for professional voices. Mixing them returns 400 invalid_parameter
3. On the stream, decode and play each base64 WAV part in `part_index` order. Do not concatenate the bytes
4. Send an Idempotency-Key when creating a voice, and retry 502, 503 and 504 on speech, which the OpenAPI file marks as safe
5. Use POST /v3/voices/speech for stock or designed voices. It is a different engine and price

### 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, HeyGen Voice or Rime TTS API + MCP?

HeyGen Voice scores 71.3 (BB) on agent readiness against Rime TTS API + MCP's 55.8 (C), and leads in 6 of 7 scored categories. Rime TTS API + MCP leads on payments & pricing.

### Do HeyGen Voice and Rime TTS API + MCP need an API key?

Both need an API key.

### Can an agent call HeyGen Voice and Rime TTS API + MCP without installing anything?

Yes. HeyGen Voice has a hosted endpoint at https://api.heygen.com and Rime TTS API + MCP at https://users.rime.ai.


## For agents

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

## Other comparisons with HeyGen Voice or Rime TTS API + MCP

- [Amazon Polly vs HeyGen Voice](https://www.anchorterminal.com/compare/amazon-polly-vs-heygen-voice.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 HeyGen Voice](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-heygen-voice.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 HeyGen Voice](https://www.anchorterminal.com/compare/cartesia-tts-vs-heygen-voice.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 HeyGen Voice](https://www.anchorterminal.com/compare/deepgram-tts-vs-heygen-voice.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 HeyGen Voice](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-heygen-voice.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 HeyGen Voice](https://www.anchorterminal.com/compare/fish-audio-tts-vs-heygen-voice.md)
- [Fish Audio TTS API vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/fish-audio-tts-vs-rime-tts.md)
- [HeyGen Voice vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/heygen-voice-vs-murf-tts.md)
- [HeyGen Voice vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/heygen-voice-vs-playht-tts.md)
- [HeyGen Voice vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/heygen-voice-vs-resemble-ai-tts.md)
- [HeyGen Voice vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/heygen-voice-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)