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

Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Resemble AI Text-to-Speech API

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against Resemble AI Text-to-Speech API's 48.5 (D), and leads in every scored category. 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

  • Reliability, 80 against 75
  • Schema & documentation, 95 against 75
  • Agent ergonomics, 82 against 46
  • Security & auth, 72 against 48
  • Payments & pricing, 60 against 0
  • Maintenance & community, 73 against 31
  • Transparency & trust, 78 against 65

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5
  • No incidents deducted, where Resemble AI Text-to-Speech API loses 3 points for them

Watch for

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

Resemble AI Text-to-Speech API D

Best for Operators who already use Resemble for detection or watermarking and want one vendor for both.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Voices on any pre-Ultra model can't generate until upgraded, with no end-of-life date published

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.

Payments & pricing Deepgram Text-to-Speech (Aura-2, Flux TTS) +60

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

No x402, MPP or L402 (0). Per-1,000-character prices for Flux TTS, Aura-2 and Aura-1 published without a login (20). $200 credit with no card (20). A person signs up in a browser to get the first key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Resemble AI Text-to-Speech API 0

No x402, MPP or L402 (0). The per-second prices ($0.00067 on Flex, $0.0005 on Team and Business) were read on 30 September from app.resemble.ai/billing/api/v1/plans, a billing data endpoint this run doesn't read, so that reading is struck, and the pricing pages can't be re-read under the terms, so no per-unit price stands today (0). No free synthesis allowance per the 1 October check (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Maintenance & community Deepgram Text-to-Speech (Aura-2, Flux TTS) +42

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

Read as a model. Changelog entries to 27 October 2026, the newest changing how callbacks, TTS callbacks included, are verified (30). 34 dated entries in the 90 days from 3 August (10). We found no deprecation policy and no TTS deprecation notices in the period (0 of 10). Public changelog and community support channels (10 of 15). The Python SDK had 27 open issues on 1 October, the newest from August 2026 with no maintainer reply visible, per the 1 October check, not re-read on 1 November (3 of 10). Official SDKs current in five languages, the Python SDK at 7.16.0 on 28 October (15). SDK CI not checked (5 of 10).

Resemble AI Text-to-Speech API 31

Read as a model. The newest changelog entry is 2026-06-30 per the 1 October check, not re-read on 4 November (terms), 127 days old (10). No dated entries in the last 90 days that we could read (0 of 10). Older models were deprecated on 2026-06-29 and the docs say voices on them can't generate until upgraded, with no effective date published (0 of 10). Public changelog and a support address, SDK issue trackers not checked (8 of 25). The Node SDK clone on 4 November still ends at 754a91e (6 April 2026, 3.5.3); Python 1.9.0 of 6 April per the 1 October check, not re-read. Neither has a release since the June model changes (10 of 15). The Python SDK still declares support from Python 3.6, and the Node repository has no CI workflow and no release tags (3 of 10).

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

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).

Resemble AI Text-to-Speech API 46

API reading of the checklist. WAV or MP3 from 8 to 48 kHz at 16, 24 or 32-bit, but synchronous synthesis returns the whole clip as base64 inside JSON (18 of 25). 2,000 characters per synchronous or HTTP stream request, 3,000 per WebSocket message. Longer scripts go through projects and clips (10 of 20). Errors are a boolean and a message, with advice to log the request ID (5 of 20). No retry, idempotency or billing-on-failure guidance found (0 of 20). Two required fields, a voice UUID and the text, and SDKs in Node and Python (13 of 15). The Node SDK is unchanged since 6 April 2026 (clone, 4 November); the rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

Security & auth Deepgram Text-to-Speech (Aura-2, Flux TTS) +24

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

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys belong to a project, carry a role and scopes, and browser JWTs live 30 seconds (30). Requests fall under the Model Improvement Program, which covers TTS, unless each request sets mip_opt_out=true (10 of 20). Opted-out requests are kept only for processing, so zero retention is self-serve but not the default (10 of 15). Per-request logs through GET /v1/projects/{project_id}/requests, no audit log of key actions found (10 of 15). SOC 2 Type 1 and Type 2, HIPAA with a BAA on request and PCI listed on the compliance page. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy or bug bounty found (12 of 20). 30 + 10 + 10 + 10 + 12 = 72.

Resemble AI Text-to-Speech API 48

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key with no scopes found (20 of 30). The privacy policy (14 August 2026) says customer voice data isn't used to train general-purpose models, worded for voice data rather than text (15 of 20). Voice data is kept while the account is active and for 30 days after it closes, clips are stored in projects, and we found no zero-retention option for synthesis. The Node SDK's zero_retention_mode (3.5.3) is a detection option (5 of 15). No per-call log found (0 of 15). Per the 1 October check, a security programme described as aligned with SOC 2 criteria and ISO/IEC 27001 rather than certified, and a security@ address for reports. No security.txt (8 of 20). Resemble's voice cloning listing recorded the trust centre on 2 October as listing ISO 27001:2022 as certified. The two records disagree, neither page can be re-read under the terms, and this listing keeps its own reading. OSV lists no records for @resemble/node or resemble (4 November). The rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

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

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).

Resemble AI Text-to-Speech API 75

OpenAPI file in JSON and YAML at docs.resemble.ai (25). llms.txt with Markdown pages (10). The docs separate synchronous, HTTP streaming and WebSocket synthesis and say WebSocket needs Business, but rarely say when not to use one (12 of 20). Request bodies typed in the spec. The model is chosen by the voice, not the request (12 of 15). Examples on each endpoint, but the errors page only describes success: false with a message and lists no status codes (6 of 15). /api/v2 paths and a dated product changelog shared with detection (10 of 15). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

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

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).

Resemble AI Text-to-Speech API 65

Closed service with clear terms (15 of 30). The privacy policy gives retention periods and links a sub-processor list, but names Google Cloud, Render and Cerebrium as infrastructure while the changelog calls Resemble Ultra xAI-powered, and no xAI processing is mentioned (15 of 30). Deprecation started on a dated changelog entry (29 June 2026), with no end-of-life date or policy (5 of 20). The voice cloning listing gives 10 for the same entry and its model versions page reading. That split is left for a re-read. US hosting with named regions and UK processing for Enterprise on request, sub-processor list at trust.resemble.ai (15 of 20). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means); the terms of 14 August 2026 were re-read on 4 November.

Score by category

CategoryWeightDeepgram Text-to-Speech (Aura-2, Flux TTS)Resemble AI Text-to-Speech APIEdge
Reliability16%8075Deepgram Text-to-Speech (Aura-2, Flux TTS) +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9575Deepgram Text-to-Speech (Aura-2, Flux TTS) +20
Agent ergonomics13%8246Deepgram Text-to-Speech (Aura-2, Flux TTS) +36
Security & auth14%7248Deepgram Text-to-Speech (Aura-2, Flux TTS) +24
Payments & pricing10%600Deepgram Text-to-Speech (Aura-2, Flux TTS) +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7331Deepgram Text-to-Speech (Aura-2, Flux TTS) +42
Transparency & trust7%7865Deepgram Text-to-Speech (Aura-2, Flux TTS) +13
Negative events≤150-3
TotalA 78.1/100D 48.5/100

Facts side by side

FactDeepgram Text-to-Speech (Aura-2, Flux TTS)Resemble AI Text-to-Speech API
KindModel APIModel API
VendorDeepgramResemble AI
Hosted endpointhttps://api.deepgram.com/v1https://app.resemble.ai/api/v2
TransportsHTTP, Streamable HTTP, stdio, SSE (legacy)HTTP
AuthAPI keyAPI key
PricingPay per usePay per use
Price for text-to-speech$45 per 1M charactersnot published
x402nono
LicenceMIT (SDKs)none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-06-30
Terms last updated2026-08-062026-08-14
Privacy policy last updated2021-10-262026-08-14
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 waiveryesyes
Popularity468 stars, 1.1M npm/wk, 805k PyPI/wk15 stars, 8.1k npm/wk
Agent reviews3.5/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Deepgram Text-to-Speech (Aura-2, Flux TTS) higher.

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.

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.

Resemble AI Text-to-Speech API

OpenAPI file in JSON and YAML, llms.txt and Markdown pages. Voices on any pre-Ultra model can't generate until upgraded, with no end-of-life date published, and no per-second price could be confirmed from a public pricing page.

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.

Resemble AI Text-to-Speech API

  1. Check the voice's model before synthesis, since voices on pre-Ultra models fail until upgraded.
  2. Keep each synchronous request under 2,000 characters.
  3. Decode audio_content from base64 on /synthesize, or call /stream for raw WAV chunks.
  4. Send Authorization: Bearer, since some doc examples leave out the prefix.
  5. Log the request ID with every failure, since the error body has no code.

Questions

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against Resemble AI Text-to-Speech API's 48.5 (D), and leads in every scored category.

Do Deepgram Text-to-Speech (Aura-2, Flux TTS) and Resemble AI Text-to-Speech API need an API key?

Both need an API key.

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

Yes. Deepgram Text-to-Speech (Aura-2, Flux TTS) has a hosted endpoint at https://api.deepgram.com/v1 and Resemble AI Text-to-Speech API at https://app.resemble.ai/api/v2.

Other comparisons with Deepgram Text-to-Speech (Aura-2, Flux TTS) or Resemble AI Text-to-Speech API

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.