Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs Speechmatics Speech-to-Text
Amazon Transcribe scores 75.5 (BB) on agent readiness against Speechmatics Speech-to-Text's 70.3 (BB), and leads in 3 of 7 scored categories. Speechmatics Speech-to-Text leads on payments & pricing and maintenance & community. Both do speech-to-text.
Best speech-to-text APIs for AI agents · All 387 stt comparisons
Which one, for what
Best for Teams already on AWS with audio in S3 and IAM in place, especially batch jobs at volume.
Ahead on
- Reliability, 75 against 70
- Security & auth, 83 against 65
- Transparency & trust, 85 against 76
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
- No incidents deducted, where Speechmatics Speech-to-Text loses 3 points for them
Watch for
AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set
Speechmatics Speech-to-Text BB
Best for Regulated or privacy-sensitive audio, multilingual batch with Melia 1, and voice agents that want speaker-attributed turns.
Ahead on
- Payments & pricing, 60 against 45
- Maintenance & community, 70 against 60
Watch for
Enhanced costs $0.38 to $0.40 an hour, above most rivals
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 Transcribe +18
Amazon Transcribe 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. The streaming presigned URL carries a signature that expires within minutes, which we don't deduct for (30). Section 50.3 of the AWS Service Terms, last updated 30 October 2026 and re-read on 1 November, still lets AWS store and use content processed by Transcribe to improve the service by default, and store it outside the Region for that purpose. Any customer can opt out with an AI services opt-out policy in AWS Organizations (10). Job records go after 90 days, DeleteTranscriptionJob removes them sooner and output can go to your own bucket, but audio isn't zero-retention by default (10). Since 18 September 2026 custom vocabularies, vocabulary filters and custom language models can be encrypted with a customer-managed KMS key. 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 items in the feed on 1 November, the newest dated 31 October, names Transcribe), and Amazon Transcribe in SOC 1, 2 and 3 scope on AWS's list updated 11 August 2026, re-read on 1 November. The security.txt on aws.amazon.com, re-read on 1 November, expires on 16 October 2027 and points to the VDP. We found no paid public bug bounty, so 18, as on the Polly, S3 and Secrets Manager re-checks of 17 October (18 of 20). 30 + 10 + 10 + 15 + 18 = 83.
Speechmatics Speech-to-Text 65
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. API keys as bearer tokens, with a separate management token for key administration (20). Browser and realtime clients pass temporary keys as ?jwt= on the WebSocket URL, with a lifetime the caller sets from 60 to 86,400 seconds, so we deduct half (minus 5). Training is opt-in only, and opting in buys a 33 per cent discount (20). Realtime audio isn't stored, batch data is deleted after 7 days or on request (15). A usage reporting service exists, but we found no per-request audit log (10). ISO/IEC 27001:2022 and SOC 2 Type II with a SafeBase trust centre. No security.txt (404 on 1 November), disclosure policy, bug bounty or public advisories found (5).
Payments & pricing Speechmatics Speech-to-Text +15
Amazon Transcribe 45
No x402, MPP or L402 (0). Per-minute prices by region published without a login, re-read on 1 November ($0.006 batch and $0.01 streaming in US East) (20). The pricing page still shows 60 free minutes a month for 12 months, which per the 1 October check applies only to accounts opened before 2025-07-15. Newer accounts get up to $200 in Free Tier credits, and Free Tier FAQ Q4, re-read on 1 November, says a payment method isn't required to sign up for most new customers, though AWS may request one to verify identity. Half, as on the Polly, S3 and Secrets Manager listings (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.
Speechmatics Speech-to-Text 60
No x402, MPP or L402 (0). Per-hour prices for every model published without a login, with credits at $1 each before discounts (20). $100 credit with no card (20). 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): 40 is 60.
Maintenance & community Speechmatics Speech-to-Text +10
Amazon Transcribe 60
Read by the listing's own service models (transcribe and transcribe-streaming), as this run's amazon-s3 re-check read models/s3. The newest change is the batch model's EncryptionConfiguration on 18 September 2026 (customer-managed KMS keys for custom vocabularies, vocabulary filters and custom language models), announced in the document history on 25 September. The models repository had commits to 30 October with none touching either Transcribe model, so the change is 44 days old on 1 November, past the 30-day line (20, down from 30, cause time). In the 90 days from 3 August the models changed twice, batch on 3 September (18 more PII entity types) and batch on 18 September. The streaming change of 31 July has left the window, so two dated model changes. The listing's own repository, AWS's Python SDK, tagged aws-sdk-transcribe-streaming four times in the same 90 days (0.9.0 on 13 August, 0.10.0 on 20 August, 0.11.0 on 24 August and 0.12.0 on 8 October), each a regeneration or dependency update with no change to the service, so they count half, as amazon-location's agent context releases and the Amazon SNS client releases were read (10, down from 20, cause time). Public document history, AWS re:Post and paid support plans (10). Official SDKs are current, @aws-sdk/client-transcribe and -streaming at 3.1161.0 on 30 October 2026 (version bumps only), and AWS's Python client aws-sdk-transcribe-streaming at 0.12.0 on 8 October (15). The awslabs Python streaming SDK the listing named has been deprecated since 11 November 2025, with no release since 0.6.4 in May 2025, and its replacement is marked pre-alpha and needs Python 3.12 or later (5 of 10). 20 + 10 + 10 + 15 + 5 = 60.
Speechmatics Speech-to-Text 70
Model reading of the checklist, deprecation notice and support in place of release counts and issue replies. Changelog entries on 29 October 2026 for Batch SaaS and Agent STT, and speechmatics-rt 1.2.2 tagged on 26 October (30). Far more than three dated entries since 3 August, nine in October on the changelog's first page alone (10 of 10). No deprecation policy, and operating_point, the region field and the Voice SDK are marked deprecated with no removal date (0 of 10). A public changelog, a support portal with chat and email, and a community channel (10 of 15). SDK issues and reply times couldn't be read (0 of 10). Python packages speechmatics-batch 1.1.0 and speechmatics-rt 1.2.2, and JavaScript batch-client and real-time-client, current (15). A test workflow in the Python SDK, results not seen (5 of 10).
Transparency & trust Amazon Transcribe +9
Amazon Transcribe 85
Closed service under the AWS Service Terms, last updated 30 October 2026 (15). The service terms, privacy notice (last updated 18 May 2026, re-read on 1 November) and job retention agree, and the data processing addendum and a public sub-processor list (last updated 30 October 2026) exist, but the default permission to use content for improvement sits in section 50.3 of the service terms rather than the Transcribe guide. The DPA's text is per the 1 October check (25). The AWS Customer Agreement commits to advance notice before material functionality of a GA service is discontinued, but we found no dated Transcribe deprecation notices. The Python streaming SDK carries a deprecation notice in its README, which isn't the service (15). Sub-processors and regions disclosed, with region choice per request. Section 50.3(c) discloses that content kept for improvement may be stored outside the Region unless the organisation opts out (20). 15 + 25 + 15 + 20 = 75.
Speechmatics Speech-to-Text 76
Closed service with clear terms and MIT SDKs (15). The pricing page, limits pages and security page agree on opt-in training, 7-day batch retention and no storage for realtime (25). The changelog announces behaviour changes in advance, such as the 23 September 2026 switch to waiting polls, but we found no deprecation policy (10). EU1, US1 and AU1 regions documented per endpoint and the service named as Azure-hosted, but no sub-processor list was found (15).
Reliability Amazon Transcribe +5
Amazon Transcribe 75
AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Transcribe feeds for us-east-1, us-west-2 and eu-west-1 carried no events on 1 November 2026 (last built 31 October). The dashboard history file, re-read on 1 November, still lists Amazon Transcribe in the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, at disruption status, with its last update on 15 September 2026, inside the 90-day window from 3 August, saying AWS can't restore resources and data hosted only in that Region. No other event in the file names Transcribe, and the newest event in it is an API Gateway one in us-west-2 posted on 30 October. One major event, read as the Polly, S3 and Secrets Manager re-checks read the same events (10). Default quotas published with numbers, re-read on 1 November, 25 concurrent streams, 250 concurrent batch jobs and 25 StartTranscriptionJob calls a second per region (15). Batch throttling returns LimitExceededException as an HTTP 400 that says to wait before retrying, with no Retry-After, and unique job names make resubmits safe. Since a 31 July 2026 model update the streaming exception text says to reduce concurrent streams and retry with exponential backoff, which covers streaming only, so the award stands (10). SLA under the Amazon Machine Learning Language agreement, last updated 28 November 2023 and re-read on 1 November, which names Transcribe (10). GA (10). 20 + 10 + 15 + 10 + 10 + 10 = 75.
Speechmatics Speech-to-Text 70
Statuspage at status.speechmatics.com with components per region and history (20). Since 3 August, minor incidents only, each touching one region, one mode or a subset of requests. Batch AU slower for 2 hours on 10 August, a subset of Batch EU1, US1 and US2 jobs failing or slow for 56 minutes on 19 August, Realtime 4003 errors in the EU and US for 37 minutes on 4 September, and TLS errors for a subset of US Realtime sessions for about 2 hours on 10 September. The rest were scheduled database maintenance, a portal maintenance and a billing credit error, and nothing was posted after 10 September (20). Limits published with numbers, 10 new batch jobs and 50 status calls a second, 20,000 concurrent jobs, and 2 or 50 realtime sessions by plan (15). Both batch limits return 429 with a reason, but the docs only suggest notifications instead of polling and give no backoff or Retry-After (5). No SLA found for self-serve plans (0). Batch, Realtime and Agent STT on /v2/agent are GA (10).
Score by category
| Category | Weight | Amazon Transcribe | Speechmatics Speech-to-Text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | Amazon Transcribe +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 90 | even |
| Agent ergonomics | 13% | 80 | 80 | even |
| Security & auth | 14% | 83 | 65 | Amazon Transcribe +18 |
| Payments & pricing | 10% | 45 | 60 | Speechmatics Speech-to-Text +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 70 | Speechmatics Speech-to-Text +10 |
| Transparency & trust | 7% | 85 | 76 | Amazon Transcribe +9 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 75.5/100 | BB 70.3/100 |
Facts side by side
| Fact | Amazon Transcribe | Speechmatics Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Speechmatics |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://eu1.asr.api.speechmatics.com/v2 |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for speech-to-text | not published | $0.0025 per minute of audio |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-25 | 2026-10-26 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | 2026-05-27 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 185 stars, 506k npm/wk, 201k PyPI/wk | 20 stars, 58k npm/wk, 48k PyPI/wk |
| Agent reviews | 4/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Amazon Transcribe higher.
| Reviewer | Amazon Transcribe | Speechmatics Speech-to-Text |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 3/5 429s with a reason and no backoff advice |
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 4/5 Seven published rates and a pause at zero |
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 Transcribe | Speechmatics Speech-to-Text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.36 to $0.60 | $0.12 to $0.40 |
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 Transcribe
Batch transcription costs $0.006 a minute and streaming $0.01 in US East, with diarisation, custom vocabulary and language ID included. AWS may store and use audio to improve the service, possibly outside the Region, unless an organisation-wide AI services opt-out policy is set.
Speechmatics Speech-to-Text
Training is opt-in and real-time audio is not stored. Enhanced transcription costs $0.38 an hour for files and $0.40 for live audio.
Before you call either
Amazon Transcribe
- Give every job a unique
TranscriptionJobName. A retry with the same name fails withConflictExceptionrather than starting a second job - Poll
GetTranscriptionJobor listen on EventBridge, and setOutputBucketName, because job records are deleted after 90 days - Back off on
LimitExceededException. It arrives as a 400, not a 429 - Set the organisation's AI services opt-out policy before sending customer audio
- For Python streaming install
aws-sdk-transcribe-streamingon Python 3.12 or later, not the deprecatedamazon-transcribepackage
Speechmatics Speech-to-Text
- Set
"model": "enhanced"explicitly. The default isstandard - Use notifications instead of polling. Polling waits 5 seconds by default since the 23 September 2026 change, and
wait=0turns that off - Fetch batch transcripts within 7 days. After that the API returns 404
expired - Pass a
fetch_dataURL for files over 1 GB - Use
/v2/agentwithlinden-1for live agents instead of the plain realtime path - Read the Batch API's Swagger file at https://docs.speechmatics.com/batch.yaml before building the multipart
configfield
Questions
Which is better for AI agents, Amazon Transcribe or Speechmatics Speech-to-Text?
Amazon Transcribe scores 75.5 (BB) on agent readiness against Speechmatics Speech-to-Text's 70.3 (BB), and leads in 3 of 7 scored categories. Speechmatics Speech-to-Text leads on payments & pricing and maintenance & community.
Do Amazon Transcribe and Speechmatics Speech-to-Text need an API key?
Both need an API key.
Can an agent call Amazon Transcribe and Speechmatics Speech-to-Text without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Speechmatics Speech-to-Text at https://eu1.asr.api.speechmatics.com/v2.
Other comparisons with Amazon Transcribe or Speechmatics Speech-to-Text
- Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)
- Amazon Transcribe vs Azure AI Speech speech-to-text
- Amazon Transcribe vs Cartesia Ink
- Amazon Transcribe vs Deepgram Speech-to-Text (Nova-3, Flux)
- Amazon Transcribe vs ElevenLabs Scribe Speech to Text API
- Amazon Transcribe vs Giggy Speech to Text
- Amazon Transcribe vs Gladia Speech-to-Text API + MCP
- Amazon Transcribe vs Google Cloud Speech-to-Text
- Amazon Transcribe vs Groq Speech-to-Text
- Amazon Transcribe vs IBM Watson Speech to Text
- Amazon Transcribe vs Inworld STT
- Amazon Transcribe vs MiniMax Speech-to-Text
- Amazon Transcribe vs Mistral Voxtral Transcribe
- Amazon Transcribe vs OpenAI Speech to Text
- Amazon Transcribe vs Rev AI Speech-to-Text API
- Amazon Transcribe vs Smallest.ai Pulse STT
- Amazon Transcribe vs Soniox Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Speechmatics Speech-to-Text
- Azure AI Speech speech-to-text vs Speechmatics Speech-to-Text
- Cartesia Ink vs Speechmatics Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Speechmatics Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Speechmatics Speech-to-Text
- Giggy Speech to Text vs Speechmatics Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Speechmatics Speech-to-Text
- Google Cloud Speech-to-Text vs Speechmatics Speech-to-Text
- Groq Speech-to-Text vs Speechmatics Speech-to-Text
- IBM Watson Speech to Text vs Speechmatics Speech-to-Text
- Inworld STT vs Speechmatics Speech-to-Text
- MiniMax Speech-to-Text vs Speechmatics Speech-to-Text
- Mistral Voxtral Transcribe vs Speechmatics Speech-to-Text
- OpenAI Speech to Text vs Speechmatics Speech-to-Text
- Rev AI Speech-to-Text API vs Speechmatics Speech-to-Text
- Smallest.ai Pulse STT vs Speechmatics Speech-to-Text
- Soniox Speech-to-Text vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/amazon-transcribe-vs-speechmatics-stt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-transcribe.json·/api/v1/tools/speechmatics-stt.json - From a terminal
anchor compare amazon-transcribe speechmatics-stt(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "speechmatics-stt"}at/mcp, no key