Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs ElevenLabs Scribe Speech to Text API
Amazon Transcribe and ElevenLabs Scribe Speech to Text API score within a point of each other on agent readiness, 75.5 (BB) and 75.5 (BB). ElevenLabs Scribe Speech to Text API leads on reliability, schema & documentation, 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
- Agent ergonomics, 80 against 75
- Security & auth, 83 against 65
- Transparency & trust, 85 against 71
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set
ElevenLabs Scribe Speech to Text API BB
Best for Batch transcription where diarisation, entity detection and keyterms matter, and for teams already on ElevenLabs for speech.
Ahead on
- Reliability, 80 against 75
- Schema & documentation, 95 against 90
- Payments & pricing, 60 against 45
- Maintenance & community, 77 against 60
Also in its favour
- Runs on your own machine
Watch for
Audio may be used for training unless the account opts out, and the opt-out isn't retroactive
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.
ElevenLabs Scribe Speech to Text API 65
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys can be restricted to chosen endpoints, given a credit quota and limited to IP addresses or CIDR ranges, user keys can expire after 15 minutes to 30 days, service accounts hold keys that don't belong to a person, and leaked keys found by GitHub secret scanning are disabled, re-read on 1 November. Realtime browser clients use single-use tokens, which we don't deduct for (30). The Privacy Policy (updated 9 October 2026, re-read on 1 November) says ElevenLabs may train on personal data, with an opt-out under Data use that only covers data sent after it's set (10). Speech-to-text audio and transcripts are kept by default and zero retention through enable_logging=false is Enterprise only, though the zero retention page now names every /v1/speech-to-text/ endpoint (5). The Developers page has a Request Log that lists every API request with search, filters and CSV export, and usage can be broken down by API key, though we found no audit log of key actions below Enterprise (10 of 15, was 5). A valid security.txt (expiring 6 October 2027, re-read on 1 November) pointing to a vulnerability disclosure programme, and the Eleven v4 launch page states SOC 2 Type II, ISO 27001 and PCI DSS Level 1 certification for every ElevenLabs model. We count those as vendor claims because we saw no report, and the trust centre wasn't re-read. No bug bounty or public advisories found (10 of 20, was 5, as the ElevenLabs text-to-speech listing reads the same evidence). 30 + 10 + 5 + 10 + 10 = 65.
Maintenance & community ElevenLabs Scribe Speech to Text API +17
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.
ElevenLabs Scribe Speech to Text API 77
Read as a model, as the ElevenLabs text-to-speech listing is, in place of the 1 October release-count reading. Newest change is SDK 2.75.0, tagged in the Python and JavaScript repositories on 27 October 2026 (23:02 UTC), and the 26 October changelog entry changed realtime silence thresholds and added transcription webhook retries. Speech to Text also changed on 12 October (turn_prediction commit strategy) and 19 October (edited_text) (30). Weekly dated entries, 16 between 3 August and 26 October (10). scribe_v1 is still marked deprecated in favour of scribe_v2 with no date or notice period (0 of 10). Public changelog and support channels (10 of 15). The Python SDK had 19 open issues on 1 October, several opened in August 2026, per the ElevenLabs text-to-speech listing's 1 October check of the same repository, not re-read on 1 November (5 of 10). Official Python and TypeScript SDKs current at 2.75.0. The local elevenlabs-mcp package, the only one with a transcription tool, has been deprecated since 20 August 2026 in favour of the hosted server, its last release 0.12.2 on 4 August (15). Fern-generated SDKs, read as the ElevenLabs text-to-speech listing reads them (7 of 10). 30 + 10 + 0 + 10 + 5 + 15 + 7 = 77.
Payments & pricing ElevenLabs Scribe Speech to Text API +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.
ElevenLabs Scribe Speech to Text API 60
No x402, MPP or L402 (0). Per-hour prices and plan allowances published without a login, re-read on 1 November, $0.22 an hour for Scribe v2 and Scribe v2 Medical and $0.39 for Scribe v2 Realtime (20). Free plan with 4 hours 30 minutes of batch a month and no card, per the 1 October check; the pricing page read on 1 November doesn't say whether the free plan needs one (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40. 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 Transcribe +14
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.
ElevenLabs Scribe Speech to Text API 71
Closed service with clear terms and MIT SDKs (15). The Privacy Policy, updated 9 October 2026 and re-read on 1 November, allows training on personal data with a forward-only opt-out, and the zero retention page now says every /v1/speech-to-text/ endpoint is covered for Enterprise customers. We found no speech-to-text statement that contradicts them, though a reader still pieces the position together from three pages (15). scribe_v1 is marked deprecated without a date or a written policy (5). EU, India and Singapore residency hosts are documented, but no named sub-processor list was found (15). 15 + 15 + 5 + 15 = 50.
Reliability ElevenLabs Scribe Speech to Text API +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.
ElevenLabs Scribe Speech to Text API 80
incident.io status page with a Speech to Text component and dated component history (20). Re-read on 1 November from the history page, which dates each component's impact, as the ElevenLabs text-to-speech, voice cloning and agents listings were read; the incidents feed was re-posted on 21 October and leaves older incidents out. Six incidents touched the Speech to Text component in the 90 days from 3 August. Elevated TTS and STT error rates from 06:39 to 07:13 UTC on 3 August and TTS and STT latency from 15:15 to 17:53 UTC on 26 August, both at degraded performance. Two latency incidents on 4 September, the EU residency from 11:41 to 12:12 UTC and the global residency from 13:55 to 21:01 UTC for "a small subset of requests", and STT latency from 15:42 to 16:05 UTC on 28 September, all degraded. From 16:00 to 19:44 UTC on 29 September a usage datastore fault caused latency, conversation failures and 429s on STT requests, marked partial outage on Speech to Text and Conversations. The 1 October note called it one major of 94 minutes; the page dates the STT impact at 3 hours 44 minutes, and it is read as partial, as the ElevenLabs agents listing read the same incident. A one-minute entry named "Test" on 16 October isn't counted. Nothing has touched STT since 29 September. Minor only (20 of 30, was 10). Concurrency per plan published with numbers, re-read on 1 November, 8 on Free to 60 on Scale for batch and 6 to 45 for realtime, with current-concurrent-requests and maximum-concurrent-requests headers (15). The error reference names three 429 codes, rate_limit_exceeded, concurrent_limit_exceeded and system_busy, and asks for exponential backoff (15). No SLA found for self-serve plans, and the API pricing page puts SLAs under Enterprise (0). Scribe v2, Scribe v2 Realtime and Scribe v2 Medical carry no alpha or beta label (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.
Schema & documentation ElevenLabs Scribe Speech to Text API +5
Amazon Transcribe 90
The service model is public in aws/api-models-aws and the AWS SDKs, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, 260 lines on 1 November (10). Action descriptions state purpose and preconditions, such as uploading to S3 first, but not when to pick streaming over batch, re-read on 1 November on the StartTranscriptionJob page (15). Inputs are typed with enums (LanguageCode, MediaFormat), patterns and ranges (MediaSampleRateHertz 8,000 to 48,000) and marked required (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples section (the StartTranscriptionJob page, re-read on 1 November, gives only inline examples of parameter values), so examples live in the developer guide (10). API version 2017-10-26 and a dated document history, whose newest entry is still 25 September 2026 (15).
ElevenLabs Scribe Speech to Text API 95
OpenAPI file at api.elevenlabs.io/openapi.json, per the 1 October check, not re-read on 1 November because api.elevenlabs.io's robots.txt disallows every path (25). llms.txt with a Markdown twin of each page, re-read on 1 November (10). Reference pages state what each parameter does, and the docs separate batch, realtime and medical use, though they rarely say when not to use one (15). Multipart fields are typed with enums such as timestamps_granularity, and model_id is required (15). Examples on each endpoint and an error reference with codes and meanings, re-read on 1 November (15). Versioned /v1 paths and a dated weekly changelog, the newest entry 26 October (15). 25 + 10 + 15 + 15 + 15 + 15 = 95.
Score by category
| Category | Weight | Amazon Transcribe | ElevenLabs Scribe Speech to Text API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 80 | ElevenLabs Scribe Speech to Text API +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 95 | ElevenLabs Scribe Speech to Text API +5 |
| Agent ergonomics | 13% | 80 | 75 | Amazon Transcribe +5 |
| Security & auth | 14% | 83 | 65 | Amazon Transcribe +18 |
| Payments & pricing | 10% | 45 | 60 | ElevenLabs Scribe Speech to Text API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 77 | ElevenLabs Scribe Speech to Text API +17 |
| Transparency & trust | 7% | 85 | 71 | Amazon Transcribe +14 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75.5/100 | BB 75.5/100 |
Facts side by side
| Fact | Amazon Transcribe | ElevenLabs Scribe Speech to Text API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | ElevenLabs |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://api.elevenlabs.io/v1 |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| 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-27 |
| Terms last updated | 2026-10-01 | 2026-03-31 |
| Privacy policy last updated | 2026-05-18 | 2026-05-20 |
| Customer content may train models | yes, with an opt-out | yes, with an opt-out |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 185 stars, 506k npm/wk, 201k PyPI/wk | 3.1k stars, 1.1M npm/wk, 2.2M 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 | ElevenLabs Scribe Speech to Text API |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 3/5 Three named 429 codes and a 94-minute failure |
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 4/5 $0.22 an hour, and silence is billed |
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 | ElevenLabs Scribe Speech to Text API |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.36 to $0.60 | $0.22 to $0.39 |
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.
ElevenLabs Scribe Speech to Text API
Scribe v2 transcribes 90+ languages at $0.22 an hour of batch audio, with diarisation up to 32 speakers and keys that can be scoped by endpoint, capped and set to expire. Audio may be used for training unless the account opts out, the opt-out isn't retroactive, and zero retention needs Enterprise.
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
ElevenLabs Scribe Speech to Text API
- Create a key restricted to speech-to-text with a credit quota and an expiry
- Use
source_urlfor hosted files instead of downloading and re-uploading - Set
webhook=truefor long files and turn on webhook retries so results aren't lost - Back off exponentially on any of the three 429 codes
- Opt out under Data use before sending customer audio. It only covers later uploads
Questions
Which is better for AI agents, Amazon Transcribe or ElevenLabs Scribe Speech to Text API?
Amazon Transcribe and ElevenLabs Scribe Speech to Text API score within a point of each other on agent readiness, 75.5 (BB) and 75.5 (BB). ElevenLabs Scribe Speech to Text API leads on reliability, schema & documentation, payments & pricing and maintenance & community.
Do Amazon Transcribe and ElevenLabs Scribe Speech to Text API need an API key?
Both need an API key.
Can an agent call Amazon Transcribe and ElevenLabs Scribe Speech to Text API without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and ElevenLabs Scribe Speech to Text API at https://api.elevenlabs.io/v1.
Other comparisons with Amazon Transcribe or ElevenLabs Scribe Speech to Text API
- 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 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
- Amazon Transcribe vs Speechmatics Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs ElevenLabs Scribe Speech to Text API
- Azure AI Speech speech-to-text vs ElevenLabs Scribe Speech to Text API
- Cartesia Ink vs ElevenLabs Scribe Speech to Text API
- Deepgram Speech-to-Text (Nova-3, Flux) vs ElevenLabs Scribe Speech to Text API
- ElevenLabs Scribe Speech to Text API vs Giggy Speech to Text
- ElevenLabs Scribe Speech to Text API vs Gladia Speech-to-Text API + MCP
- ElevenLabs Scribe Speech to Text API vs Google Cloud Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Groq Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs IBM Watson Speech to Text
- ElevenLabs Scribe Speech to Text API vs Inworld STT
- ElevenLabs Scribe Speech to Text API vs MiniMax Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Mistral Voxtral Transcribe
- ElevenLabs Scribe Speech to Text API vs OpenAI Speech to Text
- ElevenLabs Scribe Speech to Text API vs Rev AI Speech-to-Text API
- ElevenLabs Scribe Speech to Text API vs Smallest.ai Pulse STT
- ElevenLabs Scribe Speech to Text API vs Soniox Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/amazon-transcribe-vs-elevenlabs-scribe.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-transcribe.json·/api/v1/tools/elevenlabs-scribe.json - From a terminal
anchor compare amazon-transcribe elevenlabs-scribe(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "elevenlabs-scribe"}at/mcp, no key