Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs Gladia Speech-to-Text API + MCP
Amazon Transcribe scores 75.5 (BB) on agent readiness against Gladia Speech-to-Text API + MCP's 72.3 (BB), and leads in 4 of 7 scored categories. Gladia Speech-to-Text API + MCP leads on 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
- Reliability, 75 against 70
- Agent ergonomics, 80 against 75
- Security & auth, 83 against 65
- Transparency & trust, 85 against 65
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.0 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
Gladia Speech-to-Text API + MCP BB
Best for Multilingual meetings and calls where live and async transcription in 100+ languages is needed, and for teams who want an MCP server.
Ahead on
- Schema & documentation, 95 against 90
- Payments & pricing, 60 against 45
- Maintenance & community, 70 against 60
Also in its favour
- Runs on your own machine
Watch for
Self-serve audio is used for model training by default unless the account opts out
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.
Transparency & trust Amazon Transcribe +20
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.
Gladia Speech-to-Text API + MCP 65
Closed service with an MIT SDK and MCP server and separate terms for Gladia SAS and Gladia Inc. (15). The statements disagree. The security page gives a 12-month default retention with custom policies for customers and says only Free plan data trains models, while the retention page gives 1 year on free, 3 weeks on paid and zero retention only on Enterprise, and the pricing page says Self-serve is opted in to training by default. ISO 27001 is described as in progress (15). Breaking changes are flagged with dates in the changelog, such as SDK 2.0.0 and the move to credit billing on 3 July 2026 with a 6 to 20 July rollout, but no deprecation policy was found (10). Hosting with a French provider is stated, and no sub-processor list was found (10).
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.
Gladia Speech-to-Text API + MCP 65
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Plain revocable API keys in the x-gladia-key header. Live sessions connect to a WebSocket URL minted per session by POST /v2/live, which we don't deduct for (20). The pricing page, read on 1 November, says Self-serve, the paid pay-as-you-go plan, is opted in to model training by default with a free opt-out in the profile, and Enterprise is opted out by default. The security page still says only Free plan data is used for training. We score the pricing page's default, as for AWS's default use with an opt-out (10 of 20). Retention is documented and jobs can be deleted, but zero retention needs Enterprise per the retention page (10). Job history through the list endpoint and dashboard, no audit log of key actions found (10). SOC 2 Type 1 and Type 2, a bug bounty programme that doubles as the disclosure route, no security.txt (404 on 1 November) and no public advisories found. The SDKs fixed an API key leak on cross-origin redirects in 2.1.0 (September) and limited list pagination to the configured API in 2.2.0 (13 October), both released. ISO 27001 is in progress, not held (15). 20 + 10 + 10 + 10 + 15 = 65.
Payments & pricing Gladia Speech-to-Text API + MCP +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.
Gladia Speech-to-Text API + MCP 60
No x402, MPP or L402 (0). Per-hour prices in euros published without a login, re-read on 1 November, async from 0.27€ an hour on solaria-1 and 0.16€ on solaria-3, real-time 0.68€, add-ons per hour (20). A one-time €50 credit, with no card per the 1 October check (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 Gladia Speech-to-Text API + MCP +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.
Gladia Speech-to-Text API + MCP 70
Read as a model, for deprecation notice and model churn rather than release counts, on the lines deepgram-stt was settled on in this run. SDK 2.2.0 on 13 October 2026, three fixes among them limiting list pagination to the configured API, 19 days before 1 November (30). 2.2.1 on 23 October only raises the Python certifi floor to distrust a compromised certificate authority and is a version bump with no code changes for JavaScript, so as a dependency-only release it counts half and doesn't set this line, as azure-translator's was read. In the 90 days from 3 August, changelog entries on 8, 9 and 14 September, SDK 2.1.0 (18 and 21 September), 2.2.0 and 2.2.1 (at half), and the MCP server 0.1.0 and 0.1.1 on 24 September (10). The /v2/transcription endpoints are marked deprecated in favour of /v2/pre-recorded with no removal date, structured data extraction has gone from the OpenAPI file without a changelog entry, and no deprecation policy was found (0 of 10). Public changelog, help centre and Discord (10 of 15). SDK and MCP repository issues couldn't be read, since github.com refuses our reader, so absent (0 of 10). Official JavaScript and Python SDKs current at 2.2.1 (15). The SDK repository has CI, release and OpenAPI type-update workflows, results not seen (5 of 10). 30 + 10 + 0 + 10 + 0 + 15 + 5 = 70.
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.
Gladia Speech-to-Text API + MCP 70
incident.io status page with per-component uptime bars and incident pages, and an RSS feed read on 1 November (20). One major incident in the 90 days from 3 August, a global Pre-Recorded and Real-Time incident on 23 September 2026 from 07:05 to 08:10 caused by a provider network fault, as read on 1 October. The rest are partial and read as minor, a 20-minute full outage and a timeouts incident on 22 September, slower processing on the afternoon of 23 September, and Europe-only degradations on 2, 10, 14 to 15 (elevated errors and timeouts in Europe from 09:07 on 14 September to 13:58 on 15 September), 21, 22 and 28 September and on 3, 4 and 7 October (Pre-Recorded v2 in Europe) (10). Concurrency limits published with numbers, 25 parallel async jobs plus 300 queued and 30 live sessions on paid plans, 3 and 1 on free (15). The docs say a 429 means the concurrency limit, but we found no backoff guidance or Retry-After (5). The pricing page's plan comparison, read on 1 November, lists a 99.9% uptime SLA for Enterprise (10). solaria-1 and solaria-3 are GA (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.
Schema & documentation Gladia Speech-to-Text API + MCP +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).
Gladia Speech-to-Text API + MCP 95
OpenAPI file at api.gladia.io/openapi.json (25). llms.txt (10). Reference pages state purpose per endpoint and the model page says to use solaria-3 only for async English, French, German, Spanish or Italian (15). Typed bodies with enums and required fields, audio_url the only required input for pre-recorded (15). Examples per endpoint and documented error codes (15). Versioned /v2 paths and a dated changelog (15).
Score by category
| Category | Weight | Amazon Transcribe | Gladia Speech-to-Text API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | Amazon Transcribe +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 95 | Gladia Speech-to-Text API + MCP +5 |
| Agent ergonomics | 13% | 80 | 75 | Amazon Transcribe +5 |
| Security & auth | 14% | 83 | 65 | Amazon Transcribe +18 |
| Payments & pricing | 10% | 45 | 60 | Gladia Speech-to-Text API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 70 | Gladia Speech-to-Text API + MCP +10 |
| Transparency & trust | 7% | 85 | 65 | Amazon Transcribe +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75.5/100 | BB 72.3/100 |
Facts side by side
| Fact | Amazon Transcribe | Gladia Speech-to-Text API + MCP |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Gladia |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://api.gladia.io/v2 |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | MIT (SDKs and MCP server) |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-25 | 2026-10-23 |
| 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 | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| 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 | 4 stars, 4.8k npm/wk, 126k PyPI/wk |
| Agent reviews | 4/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Amazon Transcribe higher.
| Reviewer | Amazon Transcribe | Gladia Speech-to-Text API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 3/5 All add-ons included, at two to four times rivals' base rates |
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 3/5 A 429 that names its cause and stops there |
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
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.
Gladia Speech-to-Text API + MCP
The solaria-1 model transcribes live and recorded audio in over 100 languages with code switching, behind an OpenAPI file and SDKs in two languages. Self-serve audio is used for model training unless the account opts out, and Gladia's pages disagree on retention and training defaults.
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
Gladia Speech-to-Text API + MCP
- Don't resubmit a pre-recorded job after a 200 or a
transcription.createdwebhook. It's already queued - Pick
solaria-3only for async EN, FR, DE, ES or IT audio. Anything live or multilingual needssolaria-1 - A 429 means the concurrency limit, 3 async and 1 live on the free plan. Wait for a running job to finish
- Opt the account out of model training in its profile before sending sensitive audio on Self-serve
- Split files over 135 minutes or 1,000 MB
Questions
Which is better for AI agents, Amazon Transcribe or Gladia Speech-to-Text API + MCP?
Amazon Transcribe scores 75.5 (BB) on agent readiness against Gladia Speech-to-Text API + MCP's 72.3 (BB), and leads in 4 of 7 scored categories. Gladia Speech-to-Text API + MCP leads on schema & documentation, payments & pricing and maintenance & community.
Do Amazon Transcribe and Gladia Speech-to-Text API + MCP need an API key?
Both need an API key.
Can an agent call Amazon Transcribe and Gladia Speech-to-Text API + MCP without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Gladia Speech-to-Text API + MCP at https://api.gladia.io/v2.
Other comparisons with Amazon Transcribe or Gladia Speech-to-Text API + MCP
- 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 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 Gladia Speech-to-Text API + MCP
- Azure AI Speech speech-to-text vs Gladia Speech-to-Text API + MCP
- Cartesia Ink vs Gladia Speech-to-Text API + MCP
- Deepgram Speech-to-Text (Nova-3, Flux) vs Gladia Speech-to-Text API + MCP
- ElevenLabs Scribe Speech to Text API vs Gladia Speech-to-Text API + MCP
- Giggy Speech to Text vs Gladia Speech-to-Text API + MCP
- Gladia Speech-to-Text API + MCP vs Google Cloud Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Groq Speech-to-Text
- Gladia Speech-to-Text API + MCP vs IBM Watson Speech to Text
- Gladia Speech-to-Text API + MCP vs Inworld STT
- Gladia Speech-to-Text API + MCP vs MiniMax Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Mistral Voxtral Transcribe
- Gladia Speech-to-Text API + MCP vs OpenAI Speech to Text
- Gladia Speech-to-Text API + MCP vs Rev AI Speech-to-Text API
- Gladia Speech-to-Text API + MCP vs Smallest.ai Pulse STT
- Gladia Speech-to-Text API + MCP vs Soniox Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/amazon-transcribe-vs-gladia-stt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-transcribe.json·/api/v1/tools/gladia-stt.json - From a terminal
anchor compare amazon-transcribe gladia-stt(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "gladia-stt"}at/mcp, no key