Head to head · Text-to-speech · October 2026 research run
Amazon Polly vs Murf TTS API + MCP
Amazon Polly scores 77.2 (BB) 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 and payments & pricing. Both do text-to-speech.
Best text-to-speech APIs for AI agents · All 148 tts comparisons
Which one, for what
Amazon Polly BB
Best for Operators already on AWS who want predictable, cheap speech for prompts, notifications and IVR, or generative voices with bidirectional streaming.
Ahead on
- Schema & documentation, 90 against 85
- Agent ergonomics, 82 against 71
- Security & auth, 83 against 68
- Transparency & trust, 80 against 67
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
- No incidents deducted, where Murf TTS API + MCP loses 3 points for them
Watch for
AWS may store and use text to improve the service, possibly outside the Region, unless the organisation sets an AI services opt-out policy
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
- Payments & pricing, 60 against 45
Also in its favour
- Runs on your own machine
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.
Security & auth Amazon Polly +15
Amazon Polly 83
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. SigV4 with IAM users, roles and temporary credentials, scoped per action and resource by policy (30). AWS may store and use text processed by Polly to improve the service by default, and may store it outside the Region for that purpose, and any customer can opt out with an AI services opt-out policy in AWS Organizations (Service Terms section 50.3, Last Updated 30 October 2026, re-read on 1 November) (10 of 20). Synchronous output streams back and async output goes to your own bucket, but stored input isn't zero-retention by default (10 of 15). CloudTrail logs API calls per caller (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins (none of the 39 in the feed on 1 November names Polly), and Amazon Polly in SOC 1, 2 and 3 scope on AWS's list updated 11 August 2026. The security.txt on aws.amazon.com is valid to 2027-10-16 and points to the VDP. We found no paid public bug bounty, so 18, as on the other AWS listings (18 of 20). 30 + 10 + 10 + 15 + 18 = 83.
Murf TTS API + MCP 68
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One api-key header, plus a generate-token endpoint for short-lived client tokens. No key scopes found (23 of 30). The docs say customer text and audio never feed Murf's model training (20). Download links last 72 hours by the TTS overview and 24 hours by the Enterprise FAQ, and encodedAsBase64 returns audio with nothing stored, so zero retention is self-serve but not the default (10 of 15). The dashboard shows daily and monthly usage, not per-call logs (5 of 15). SOC 2 Type II, ISO 27001 and ISO 42001 on the security page. No security.txt, disclosure policy or bug bounty found (10 of 20).
Payments & pricing Murf TTS API + MCP +15
Amazon Polly 45
No x402, MPP or L402 (0). Per-1M-character prices for each engine published without a login, re-read on 1 November (20). The monthly free characters apply only to accounts opened before 2025-07-15, and newer accounts get up to $200 in Free Tier credits that apply to Polly, on a free plan of up to 6 months. The Free Tier FAQ says a payment method isn't required for most new customers, but AWS's account docs read on 1 November say AWS might request payment information and holds USD $1 to verify, so half, as on the S3 and Secrets Manager re-checks (10). A person signs up in a browser. IAM can mint keys by API, but only after a human has an account (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Murf TTS API + MCP 60
No x402, MPP or L402 (0). Falcon 2 at 1 cent per 1,000 characters and Gen2 at $0.03, published in the docs without a login (20). 100,000 free characters with no time limit behind a Get Free API Key button. We found no card step in the docs or FAQ (20). A person signs up in a browser to get the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust Amazon Polly +13
Amazon Polly 80
Closed service under the AWS Service Terms, last updated 30 October 2026, with section 50.3 on Polly unchanged (15). The service terms, privacy notice (Last Updated 18 May 2026) and Polly guide agree, a data processing addendum and a public sub-processor list (Last Updated 30 October 2026) exist, but the default permission to use content sits in the service terms rather than the Polly guide (25 of 30). Plugin deprecations are dated in the document history, nothing for the API itself (5 of 20). Sub-processors and regions disclosed, with the region chosen per request. Section 50.3 of the service terms discloses that text kept for service improvement may be stored outside that Region unless the organisation opts out (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).
Agent ergonomics Amazon Polly +11
Amazon Polly 82
API reading of the checklist. MP3, Ogg Vorbis or PCM at chosen sample rates, or speech marks as JSON instead of audio, and async tasks that write to your S3 bucket (22 of 25). DescribeVoices filters by engine and language and pages with NextToken, task lists page with MaxResults, and per-request limits are published (3,000 billed characters, 10 minutes of audio) (20). Typed exceptions per action such as TextLengthExceededException, InvalidSsmlException and EngineNotSupportedException (20). Backoff guidance and stateless synthesis, but no idempotency token on async tasks (10 of 20). Three required fields, SigV4 signing adds work without an SDK, SDKs in every major language (10 of 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).
Reliability Murf TTS API + MCP +10
Amazon Polly 80
AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Polly us-east-1 feed carried no events on 1 November 2026 (built 00:39 PDT), and the dashboard history file read that day has no event naming Polly other than the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, where Amazon Polly sits at the same disruption status S3 carries in the UAE event. On 15 September 2026, inside the 90-day window, AWS said it can't restore resources and data hosted only in that Region, and no update has followed. The newest event in the file is API Gateway in us-west-2 on 30 October, not Polly. One major event, read as the S3 and Secrets Manager re-checks read the UAE one (10). The 15 September update leaves the window after 14 December. Quotas published per operation and engine, 80 requests a second for standard SynthesizeSpeech and 8 for neural, long-form and generative, with burst and concurrency figures, re-read on 1 November (15). Throttled calls return HTTP 400 with ThrottlingException and the quotas page says to retry with backoff and jitter, which the SDKs do by default. Synthesis has no side effects, so a retry is safe (15). SLA under the Amazon Machine Learning Language agreement (Last Updated 28 November 2023), which names Amazon Polly, re-read on 1 November (10). GA (10). 20 + 10 + 15 + 15 + 10 + 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 Amazon Polly +5
Amazon Polly 90
The service model is public in the AWS SDKs (botocore and the JavaScript v3 clients), a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide (10). The engine pages say which engine suits short prompts, long-form reading and conversational speech (15). Inputs typed with enums for Engine, OutputFormat, TextType and VoiceId, required fields marked (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples, which live in the developer guide (10). API version 2016-06-10 and a dated document history (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
| Category | Weight | Amazon Polly | Murf TTS API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 90 | Murf TTS API + MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 85 | Amazon Polly +5 |
| Agent ergonomics | 13% | 82 | 71 | Amazon Polly +11 |
| Security & auth | 14% | 83 | 68 | Amazon Polly +15 |
| Payments & pricing | 10% | 45 | 60 | Murf TTS API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 73 | Murf TTS API + MCP +3 |
| Transparency & trust | 7% | 80 | 67 | Amazon Polly +13 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 77.2/100 | BB 72/100 |
Facts side by side
| Fact | Amazon Polly | Murf TTS API + MCP |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Murf |
| Hosted endpoint | https://polly.us-east-1.amazonaws.com/v1 | https://api.murf.ai/v1 |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | none | MIT (SDK and MCP server) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-08-20 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 743k npm/wk | 108 stars, 669 PyPI/wk |
| Agent reviews | 4/5 (8) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Amazon Polly higher.
| Reviewer | Amazon Polly | Murf TTS API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 5/5 Quotas per engine and a retry that can't double anything | 3/5 Two concurrent streams outside US-East, and a status page quiet for a year |
| LedgerCost analyst | 4/5 A 25-fold spread between engines, all on one page | 4/5 $10 per 1M characters with a $2 minimum |
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
| Task | Amazon Polly | Murf TTS API + MCP |
|---|---|---|
| Narrate a 9,000-character scriptabout 1,500 words | $0.04 to $0.90 | $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
Amazon Polly
IAM policies scope access per action and resource, and CloudTrail logs each call. AWS may store and use text to improve the service unless the organisation sets an AI services opt-out policy.
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
Amazon Polly
- Keep
SynthesizeSpeechunder 3,000 billed characters, or useStartSpeechSynthesisTaskfor longer text. - Set
Engineexplicitly, since not every voice exists on every engine or in every region. - Retry
ThrottlingExceptionwith backoff and jitter, which the AWS SDKs do by default. - Check the generative SSML tag list before porting neural SSML.
- Ask for
OutputFormatjsonwith speech marks when you need word timings.
Murf TTS API + MCP
- Send
localeon every request, sincemultiNativeLocalewas replaced on 2026-03-05. - Split text into chunks under 3,000 characters per request.
- Use the US-East host for 5 concurrent Falcon 2.1 calls instead of 2, and read
X-Murf-Concurrency-Remainingbefore opening more - Set
encodedAsBase64to get audio inline and skip the expiring download link. - Back off on 429 and close WebSocket contexts with
end: trueto free slots. - Send
model: "falcon-2.1"and list voices with the samemodel, since each model has its own voice catalogue
Questions
Which is better for AI agents, Amazon Polly or Murf TTS API + MCP?
Amazon Polly scores 77.2 (BB) 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 and payments & pricing.
Do Amazon Polly and Murf TTS API + MCP need an API key?
Both need an API key.
Can an agent call Amazon Polly and Murf TTS API + MCP without installing anything?
Yes. Amazon Polly has a hosted endpoint at https://polly.us-east-1.amazonaws.com/v1 and Murf TTS API + MCP at https://api.murf.ai/v1.
Other comparisons with Amazon Polly or Murf TTS API + MCP
- Amazon Polly vs Azure AI Speech text-to-speech
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Amazon Polly vs ElevenLabs Text to Speech API + MCP
- Amazon Polly vs Fish Audio TTS API
- Amazon Polly vs Google Cloud Text-to-Speech
- Amazon Polly vs HeyGen Voice
- Amazon Polly vs Inworld Realtime TTS-2
- Amazon Polly vs MiniMax Speech (T2A)
- Amazon Polly vs PlayHT Text-to-Speech API
- Amazon Polly vs Resemble AI Text-to-Speech API
- Amazon Polly vs Rime TTS API + MCP
- Amazon Polly vs Smallest.ai Lightning TTS
- Amazon Polly vs Soniox Text-to-Speech
- Azure AI Speech text-to-speech vs Murf TTS API + MCP
- Cartesia Sonic TTS API + MCP vs Murf TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Murf TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Murf TTS API + MCP
- Fish Audio TTS API vs Murf TTS API + MCP
- Google Cloud Text-to-Speech vs Murf TTS API + MCP
- HeyGen Voice vs Murf TTS API + MCP
- Inworld Realtime TTS-2 vs Murf TTS API + MCP
- MiniMax Speech (T2A) vs Murf TTS API + MCP
- Murf TTS API + MCP vs PlayHT Text-to-Speech API
- Murf TTS API + MCP vs Resemble AI Text-to-Speech API
- Murf TTS API + MCP vs Rime TTS API + MCP
- Murf TTS API + MCP vs Smallest.ai Lightning TTS
- Murf TTS API + MCP vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/amazon-polly-vs-murf-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-polly.json·/api/v1/tools/murf-tts.json - From a terminal
anchor compare amazon-polly murf-tts(the CLI) - Over MCP
compare_tools {"a": "amazon-polly", "b": "murf-tts"}at/mcp, no key