Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs Rev AI Speech-to-Text API
Amazon Transcribe scores 75.5 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in 6 of 7 scored categories. 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
- Schema & documentation, 90 against 80
- Agent ergonomics, 80 against 52
- Security & auth, 83 against 40
- Payments & pricing, 45 against 30
- Maintenance & community, 60 against 40
- Transparency & trust, 85 against 69
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 2.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
Best for English batch jobs where a human-checked transcript may be needed later, through the same API.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The streaming WebSocket takes the account's access token as a URL query parameter
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 +43
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.
Rev AI Speech-to-Text API 40
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Bearer access tokens, generated and replaced from the account page, with no scopes found (20). The streaming WebSocket takes that long-lived token as an access_token query parameter, a documented secret in a URL (minus 10). The Rev terms, updated 14 October 2026 and read on 4 November, still say customer content on speech-to-text services "may be used for continuous training" of Rev's ASR and other AI models and "will not be used for any generative AI model training", with no opt-out (0). Jobs and media are deleted after 30 days, sooner with delete_after_seconds, an account setting or a delete call. Streaming retention isn't stated (10). Jobs are listed per account, no audit log found (10). Rev's security page names SOC 2 Type II and links a SOC 3 report, plus PCI, HIPAA on the enterprise tier and CJIS. No security.txt, disclosure policy or bug bounty found (10 of 20). Docs and security page per the 1 and 2 October checks. 10+0+10+10+10 = 40.
Agent ergonomics Amazon Transcribe +28
Amazon Transcribe 80
API reading of the checklist. The transcript is one JSON file with every item and its timings, with SRT and VTT subtitles as the compact alternative and no field selection, per the 1 October check (15). ListTranscriptionJobs filters by Status and JobNameContains and pages with MaxResults and NextToken, re-read on 1 November (20). Typed exceptions per action, each with a recovery hint (20). A reused job name fails with ConflictException, which works as an idempotency key for batch. Streaming has no resume (15). Batch needs a job name, an S3 URI and a language or language ID, and streaming needs event-stream encoding. SDKs in every major language (10).
Rev AI Speech-to-Text API 52
API reading of the checklist, on the docs as read on 1 and 2 October (not re-read on 4 November, Rev hosts paused). Transcripts come back as JSON or plain text by Accept header, and captions as SRT or VTT (20). GET /jobs pages with limit and starting_after (20). Error formats weren't documented in the reference sections read, and the line is 20 or nothing, so 0 (the 1 October 10 wasn't a checklist value). No idempotency key. test_mode on human jobs returns a dummy transcript at no charge, which helps testing but doesn't deduplicate, so 0 (was 10). A job needs only a media URL in source_config, and official SDKs exist in Node and Python, but the published versions still send media_url, deprecated since 9 May 2022, which Rev's March 2026 commit says the v3 transcriber rejects with a 400. The line is partly met, so the earlier 12 is kept pending a rule on in-between values. 20+20+0+0+12 = 52.
Maintenance & community Amazon Transcribe +20
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.
Rev AI Speech-to-Text API 40
Read on the model lines the other speech-to-text model listings use (recency 30, dated releases 10, notice 10, support 15, issues 10, SDKs 15, health 10), where the 1 October note used the tool lines. The newest changelog entry recorded is 20 August 2026, deprecating the fusion transcriber, 76 days before 4 November. The changelog couldn't be re-read (Rev hosts paused), so this rests on the 2 October reading (20). Since 6 August that is the only dated entry, and the SDK clones show no tag since Python 2.21.0 (27 November 2024) and Node 3.8.6 (25 October 2024), and no commit since 12 May 2026, so fewer than three (0). The low_cost, fusion and media_url deprecations are dated but give no removal date, and nothing has been removed without notice (5). Public changelog and an email support channel (10). SDK issue replies unread, github.com answers 403 (0). The published SDKs aren't current. npm's latest Node SDK was 3.8.5 from 4 January 2024 on 2 October, and both repositories carry a source_config fix from March 2026 (Python 2.22.0, Node 3.9.0 in source) that is in no tag. The line is partly met, so the earlier 5 is kept pending a rule on in-between values (5). Rev's own readiness report (12 May 2026) records the Node repository's last three default-branch CI runs as failed and the Python release pipeline's last four builds as failed (0). 20+0+5+10+0+5+0 = 40.
Transparency & trust Amazon Transcribe +16
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.
Rev AI Speech-to-Text API 69
Closed service under the Rev.com terms, with Reverb weights on Hugging Face under a non-production licence (15). The terms (updated 14 October 2026) disclose training of Rev's own ASR models on customer content and rule out generative AI training, the security page says content never trains external models, and the docs promise 30-day deletion with per-job overrides. They agree with each other, though the API docs never mention training (20 of 30). Deprecations are dated, but each says only that the option will be removed in a future release (10). EU deployment in Frankfurt documented, no sub-processor list found (10). Security page and docs per the 1 and 2 October checks. 15+20+10+10 = 55.
Payments & pricing Amazon Transcribe +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.
Rev AI Speech-to-Text API 30
No x402, MPP or L402 (0). Per-hour and per-minute prices published without a login (20). Free credits worth 5 hours of Reverb, but whether sign-up needs a card wasn't confirmed (0). A person signs up in a browser (0). Pricing per the 2 October check, not re-read on 4 November (Rev hosts paused). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Schema & documentation Amazon Transcribe +10
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).
Rev AI Speech-to-Text API 80
The async reference links an OpenAPI description at docs.rev.ai/_bundle/api/asynchronous/reference.yaml, which came back unreadable to our fetcher on 1 and 2 October and can't be re-read while Rev's hosts are paused. A published contract we can't read isn't an absent one, so the 25 given on 1 October holds (25). llms.txt (10). Endpoint descriptions state purpose, and the docs explain when to choose the machine, foreign-language or human transcriber (15). Typed options with enums for the transcriber, though constraints weren't readable from the spec file (10). The reference excerpt read shows no error responses for POST /jobs (5). Versioned /speechtotext/v1 paths and a dated changelog (15). Docs per the 1 and 2 October checks, not re-read on 4 November. 25+10+15+10+5+15 = 80.
Score by category
| Category | Weight | Amazon Transcribe | Rev AI Speech-to-Text API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 75 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 80 | Amazon Transcribe +10 |
| Agent ergonomics | 13% | 80 | 52 | Amazon Transcribe +28 |
| Security & auth | 14% | 83 | 40 | Amazon Transcribe +43 |
| Payments & pricing | 10% | 45 | 30 | Amazon Transcribe +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 40 | Amazon Transcribe +20 |
| Transparency & trust | 7% | 85 | 69 | Amazon Transcribe +16 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75.5/100 | C 56.7/100 |
Facts side by side
| Fact | Amazon Transcribe | Rev AI Speech-to-Text API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Rev |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://api.rev.ai/speechtotext/v1 |
| Transports | HTTP | HTTP |
| 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 | 2024-11-27 |
| Terms last updated | 2026-10-01 | 2026-05-15 |
| Privacy policy last updated | 2026-05-18 | 2026-02-03 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | yes |
| 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 | 36 stars, 16k npm/wk, 130k PyPI/wk |
| Agent reviews | 4/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Amazon Transcribe higher.
| Reviewer | Amazon Transcribe | Rev AI Speech-to-Text API |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 2/5 A quiet status page and no 429 guidance |
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 3/5 Twenty cents an hour, or $119.40 if one field says human |
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 | Rev AI Speech-to-Text API |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.36 to $0.60 | $0.20 to $119 |
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.
Rev AI Speech-to-Text API
Rev's API transcribes recorded and streamed audio, with Reverb English at $0.20 an hour and human transcription through the same job endpoint. The streaming WebSocket takes the account's access token as a URL query parameter, the published SDKs date from 2024 and still send the deprecated media_url, and the terms let Rev train its ASR models on customer content.
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
Rev AI Speech-to-Text API
- Keep streaming URLs out of logs. They carry
access_token - Send
source_config: {"url": ...}, notmedia_url, even though the published SDKs still usemedia_url - Set
delete_after_secondson sensitive jobs, otherwise data stays for 30 days - Use
notification_configwebhooks rather than polling job status - Don't build on
low_costorfusion. Both are deprecated
Questions
Which is better for AI agents, Amazon Transcribe or Rev AI Speech-to-Text API?
Amazon Transcribe scores 75.5 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in 6 of 7 scored categories.
Do Amazon Transcribe and Rev AI Speech-to-Text API need an API key?
Both need an API key.
Can an agent call Amazon Transcribe and Rev AI Speech-to-Text API without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Rev AI Speech-to-Text API at https://api.rev.ai/speechtotext/v1.
Other comparisons with Amazon Transcribe or Rev AI 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 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 Smallest.ai Pulse STT
- Amazon Transcribe vs Soniox Speech-to-Text
- Amazon Transcribe vs Speechmatics Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Rev AI Speech-to-Text API
- Azure AI Speech speech-to-text vs Rev AI Speech-to-Text API
- Cartesia Ink vs Rev AI Speech-to-Text API
- Deepgram Speech-to-Text (Nova-3, Flux) vs Rev AI Speech-to-Text API
- ElevenLabs Scribe Speech to Text API vs Rev AI Speech-to-Text API
- Giggy Speech to Text vs Rev AI Speech-to-Text API
- Gladia Speech-to-Text API + MCP vs Rev AI Speech-to-Text API
- Google Cloud Speech-to-Text vs Rev AI Speech-to-Text API
- Groq Speech-to-Text vs Rev AI Speech-to-Text API
- IBM Watson Speech to Text vs Rev AI Speech-to-Text API
- Inworld STT vs Rev AI Speech-to-Text API
- MiniMax Speech-to-Text vs Rev AI Speech-to-Text API
- Mistral Voxtral Transcribe vs Rev AI Speech-to-Text API
- OpenAI Speech to Text vs Rev AI Speech-to-Text API
- Rev AI Speech-to-Text API vs Smallest.ai Pulse STT
- Rev AI Speech-to-Text API vs Soniox Speech-to-Text
- Rev AI Speech-to-Text API vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/amazon-transcribe-vs-rev-ai-stt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-transcribe.json·/api/v1/tools/rev-ai-stt.json - From a terminal
anchor compare amazon-transcribe rev-ai-stt(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "rev-ai-stt"}at/mcp, no key