Head to head · Text-to-speech · October 2026 research run

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against Murf TTS API + MCP's 72 (BB), and leads in 4 of 7 scored categories. Murf TTS API + MCP leads on reliability. Both do text-to-speech.

Best text-to-speech APIs for AI agents · All 148 tts comparisons

Which one, for what

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

Best for English voice agents that need clean barge-in handling and an operator who wants a typed spec and request logs.

Ahead on

  • Schema & documentation, 95 against 85
  • Agent ergonomics, 82 against 71
  • Transparency & trust, 78 against 67

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Murf TTS API + MCP loses 3 points for them

Watch for

Requests can be kept for training unless each one sets mip_opt_out=true

Murf TTS API + MCP BB

Best for Budget voice-agent output where 2 to 5 concurrent streams are enough, or for studio-style renders on Gen2.

Ahead on

  • Reliability, 90 against 80

Watch for

Falcon 2.1 concurrency is 2 outside US-East on free and pay as you go, 5 on US-East

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics Deepgram Text-to-Speech (Aura-2, Flux TTS) +11

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

API reading of the checklist. Encoding, container, sample rate and bit rate are all chosen per request, streaming returns PCM, mu-law or A-law and batch adds MP3, Opus, FLAC and AAC. Word timestamps on Flux only (20 of 25). Aura-2 REST caps a request at 2,000 characters and answers 413 above it, and the request history endpoint pages and filters by date, status and endpoint (20). Documented error codes, an INPUT_MARKUP_STRIPPED warning when SSML is dropped, and Flux's Interrupt event returns what was spoken and what wasn't (17 of 20). Backoff guidance for 429. No idempotency key, and we found nothing on billing for failed calls (10 of 20). /v1/speak needs only the text, and official SDKs ship in Python, JavaScript, Go, .NET and Java (15).

Murf TTS API + MCP 71

Read as an API. Output in MP3, WAV, FLAC, A-law, mu-law or Base64 at 8 to 48 kHz, with word timestamps, streaming over HTTP or WebSocket, and inline Base64 instead of a download link (22 of 25). Per-request cap of 3,000 characters documented and the voice list filters by model, but there's no length control beyond splitting text yourself (12 of 20). Machine-readable error and warning codes with a trace_id (18 of 20). Backoff guidance documented (10). Nothing found on whether failed calls are billed and no seed for repeatable output (0 of 10). Three required fields including locale, and the only official SDK is Python (9 of 15).

Transparency & trust Deepgram Text-to-Speech (Aura-2, Flux TTS) +11

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

Closed service with clear terms, SDKs MIT (15). The docs describe training by default under the Model Improvement Program and EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data sits on US servers and doesn't mention the program (15 of 30). Breaking corrections are flagged in the changelog, but we found no deprecation policy (10 of 20). Sub-processor list and four regional endpoints (20).

Murf TTS API + MCP 67

Closed service under clear terms, SDK and MCP server MIT (15). Data statements still disagree on 1 November. The security page says all customer data is housed in AWS us-east-2 with all storage in that region, while Falcon 2.1 runs on 11 regional hosts and a global router, and the subprocessor list names Azure, Google Cloud, IBM Cloud and Lambda Labs for speech synthesis. Download links last 72 hours by the TTS overview and 24 hours by the Enterprise page (12 of 30). Deprecations dated in the changelog, with no written policy and short or same-day notice (10 of 20). Subprocessor list with locations, last updated 30 January 2025, re-read on 1 November (15 of 20).

Reliability Murf TTS API + MCP +10

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

Statuspage at status.deepgram.com with component history and an RSS feed (20). Ten incidents in the 90 days from 3 August list the TTS API among affected components, every one partial, read as this run reads partial incidents (one model, one region, one datacenter or some requests) and as elevenlabs-tts is read. Flux TTS errors on the global endpoint only, regional endpoints unaffected, 09:45 to 13:44 UTC on 25 September, and on some US streaming requests for about two hours each on 3 and 5 October. Batch Flux TTS 503s for 91 minutes on 14 October. 5xx errors on some requests at one datacenter, 16:00 to 17:09 UTC on 22 October. Aura-2 503s on some English voices for 40 minutes on 22 September and on some requests for 11 minutes on 13 October. Short bursts on 30 September, 8 October and 29 October. Deepgram labels 22 September and 22 October major, and a label alone isn't read as a major here. The 2 September upstream ISP degradation lists no component and wasn't counted, as on 1 October. The 1 October check read 25 September as one major (10). The AWS us-west-2 event of 24 July has left the window. Minor only (20). TTS concurrency published per plan and region, 15 REST and 45 streaming on pay as you go, and Flux TTS only 5 in the EU, Australia and India (15). Rate-limit breaches return 429 and the docs ask for exponential backoff (15). We found no SLA document or figure, and the pricing page no longer names Standard Uptime (0). Aura-2 is GA, and Flux TTS is priced, on the status page and carries no preview label in the cloud docs we read (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

Murf TTS API + MCP 90

Atlassian status page at murf.statuspage.io, linked from the rate-limits doc, with history back to February 2024 (20). No incident posted since 2025-09-22, still so on 1 November 2026, so the 90-day record is clean. The page tracks only two components (API and Studio), so a clean record says less than a page with a component per region (30). Concurrency limits published per model and region, 5 on US-East and 2 elsewhere for Falcon 2.1 on free and pay as you go, and since 22 October Falcon 2.1 streaming responses report the region, limit and slots in use (15). The errors page tells you to retry 429, 500 and 503 with exponential backoff (15). No SLA found on any self-serve tier (0). Falcon 2.1 carries no beta label (10).

Schema & documentation Deepgram Text-to-Speech (Aura-2, Flux TTS) +10

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

OpenAPI 3.1 file at developers.deepgram.com/openapi.json and an AsyncAPI file for the sockets (25). llms.txt and Markdown pages (10). The docs say to use Flux TTS for live agents that need barge-in and Aura-2 for other languages, though few options say when not to use them (15). /v1/speak has an encoding enum and a default model, /v2/speak requires model, and both are typed in the spec (15). Examples on each endpoint, a general errors page and a TTS troubleshooting page for WebSocket close codes such as NET-1000 (15). Versioned /v1 and /v2 paths and a changelog with entries most weekdays (15).

Murf TTS API + MCP 85

OpenAPI and AsyncAPI specs listed in llms.txt (25). llms.txt with Markdown twins of every page (10). Model pages say which model suits voice agents and which suits studio renders, and the changelog flags Gen2 streaming as deprecated (15 of 20). Typed request bodies in the spec, with text, voiceId and locale required. We didn't check every enum (10 of 15). The errors page lists 7 HTTP codes, 4 WebSocket errors and 8 warnings, each with cause and fix, but covers only the streaming and WebSocket APIs (13 of 15). Dated public changelog, a single /v1 path and one breaking rename in 2026 (multiNativeLocale to locale on 2026-03-05) (12 of 15).

Score by category

CategoryWeightDeepgram Text-to-Speech (Aura-2, Flux TTS)Murf TTS API + MCPEdge
Reliability16%8090Murf TTS API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9585Deepgram Text-to-Speech (Aura-2, Flux TTS) +10
Agent ergonomics13%8271Deepgram Text-to-Speech (Aura-2, Flux TTS) +11
Security & auth14%7268Deepgram Text-to-Speech (Aura-2, Flux TTS) +4
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7373even
Transparency & trust7%7867Deepgram Text-to-Speech (Aura-2, Flux TTS) +11
Negative events≤150-3
TotalA 78.1/100BB 72/100

Facts side by side

FactDeepgram Text-to-Speech (Aura-2, Flux TTS)Murf TTS API + MCP
KindModel APIModel API
VendorDeepgramMurf
Hosted endpointhttps://api.deepgram.com/v1https://api.murf.ai/v1
TransportsHTTP, Streamable HTTP, stdio, SSE (legacy)HTTP, stdio
AuthAPI keyAPI key
PricingPay per useFreemium
Price for text-to-speech$45 per 1M charactersnot published
x402nono
LicenceMIT (SDKs)MIT (SDK and MCP server)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-08-20
Terms last updated2026-08-06no date given
Privacy policy last updated2021-10-26no date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity468 stars, 1.1M npm/wk, 805k PyPI/wk108 stars, 669 PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

What the same task costs

TaskDeepgram Text-to-Speech (Aura-2, Flux TTS)Murf TTS API + MCP
Narrate a 9,000-character scriptabout 1,500 words$0.13 to $0.41$0.09 to $0.27

Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.

How the scores have moved

Verdicts

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.1 costs 1 cent per 1,000 characters on pay as you go, with a $2 minimum purchase. Concurrency is 2 outside US-East on free and pay as you go, 5 on US-East, and on 19 October 2026 the falcon-2 identifier switched to Falcon 2.1 on the day it was announced.

Before you call either

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 verify TTS callbacks with Basic Auth credentials in the callback URL, not the dg-token header.

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.1 calls instead of 2, and read X-Murf-Concurrency-Remaining before opening more
  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.
  6. Send model: "falcon-2.1" and list voices with the same model, since each model has its own voice catalogue

Questions

Which is better for AI agents, Deepgram Text-to-Speech (Aura-2, Flux TTS) or Murf TTS API + MCP?

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against Murf TTS API + MCP's 72 (BB), and leads in 4 of 7 scored categories. Murf TTS API + MCP leads on reliability.

Do Deepgram Text-to-Speech (Aura-2, Flux TTS) and Murf TTS API + MCP need an API key?

Both need an API key.

Can an agent call Deepgram Text-to-Speech (Aura-2, Flux TTS) and Murf TTS API + MCP without installing anything?

Yes. Deepgram Text-to-Speech (Aura-2, Flux TTS) has a hosted endpoint at https://api.deepgram.com/v1 and Murf TTS API + MCP at https://api.murf.ai/v1.

Other comparisons with Deepgram Text-to-Speech (Aura-2, Flux TTS) or Murf TTS API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.