Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Murf TTS API + MCP

Deepgram Text-to-Speech (Aura-2, Flux TTS)

OpenAPI 3.1 and AsyncAPI files, llms.txt and Markdown pages. Requests can be kept for training unless each one sets mip_opt_out=true.

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.

Deepgram Text-to-Speech (Aura-2, Flux TTS)

1. Set mip_opt_out=true on every request if the text mustn't be kept for training.
2. Split Aura-2 REST text under 2,000 characters or expect a 413.
3. Pass model on /v2/speak, where it's required.
4. Strip SSML before sending, since it's removed with an INPUT_MARKUP_STRIPPED warning.
5. Back off exponentially on 429 and keep traffic in one project.

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.