Fish Audio TTS API vs Murf TTS API + MCP

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.

Murf TTS API + MCP

Falcon 2 costs 1 cent per 1,000 characters on pay as you go, with a $2 minimum purchase. Falcon 2 concurrency is 2 outside US-East on free and pay as you go, 5 on US-East.

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.

Murf TTS API + MCP

1. Send locale on every request, since multiNativeLocale was replaced on 2026-03-05.
2. Split text into chunks under 3,000 characters per request.
3. Use the US-East host for 5 concurrent Falcon 2 calls instead of 2.
4. Set encodedAsBase64 to get audio inline and skip the expiring download link.
5. Back off on 429 and close WebSocket contexts with end: true to free slots.