Fish Audio TTS API vs HeyGen Voice

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.

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.

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.

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