Head to head · Speech-to-text · October 2026 research run

ElevenLabs Scribe Speech to Text API vs Rev AI Speech-to-Text API

ElevenLabs Scribe Speech to Text API scores 75.5 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in every scored category. Both do speech-to-text.

Best speech-to-text APIs for AI agents · All 387 stt comparisons

Which one, for what

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 80
  • Agent ergonomics, 75 against 52
  • Security & auth, 65 against 40
  • Payments & pricing, 60 against 30
  • Maintenance & community, 77 against 40

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

Audio may be used for training unless the account opts out, and the opt-out isn't retroactive

Rev AI Speech-to-Text API C

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.

Maintenance & community ElevenLabs Scribe Speech to Text API +37

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.

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.

Payments & pricing ElevenLabs Scribe Speech to Text API +30

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.

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.

Security & auth ElevenLabs Scribe Speech to Text API +25

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.

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 ElevenLabs Scribe Speech to Text API +23

ElevenLabs Scribe Speech to Text API 75

API reading of the checklist. Timestamps can be dropped or set to word or character level, and extra formats such as SRT or plain text come back alongside JSON (20). Transcripts can be fetched by ID, but we didn't find a paginated list for them (10). Typed error codes with messages, invalid_parameters, insufficient_credits and the 429 family (20). No idempotency key, and webhook=true makes the call asynchronous without a dedupe guarantee. Since 26 October transcription webhooks are retried on failure when the webhook's retry setting is on, and requests priced below one credit are charged one credit (10). Two required fields, the model and a file or source_url. Official SDKs in Python and TypeScript (15). 20 + 10 + 20 + 10 + 15 = 75.

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.

Schema & documentation ElevenLabs Scribe Speech to Text API +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.

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.

Reliability ElevenLabs Scribe Speech to Text API +5

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.

Rev AI Speech-to-Text API 75

Statuspage at status.rev.ai with component history (20), per the 1 October check, not re-read on 4 November, because the Rev terms (updated 14 October 2026) bar using any automated system to extract content from Rev's web sites, so every Rev host is paused for this run. The history feed read on 1 October showed no incident since 13 May 2026, and the page has posted eight incidents since September 2022. The window from 6 August is held at what that reading supports, with 2 October to 4 November unread (30). Limits published with numbers, 10,000 async submissions and 500 processing jobs per 10 minutes and 10 concurrent streams (15). No 429 handling, Retry-After or backoff guidance in the async reference, the get-started page or the changelog (0). No SLA found, and the pricing page names none (0). Async and streaming are GA (10). All per the 1 and 2 October checks. 20+30+15+0+0+10 = 75.

Score by category

CategoryWeightElevenLabs Scribe Speech to Text APIRev AI Speech-to-Text APIEdge
Reliability16%8075ElevenLabs Scribe Speech to Text API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9580ElevenLabs Scribe Speech to Text API +15
Agent ergonomics13%7552ElevenLabs Scribe Speech to Text API +23
Security & auth14%6540ElevenLabs Scribe Speech to Text API +25
Payments & pricing10%6030ElevenLabs Scribe Speech to Text API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7740ElevenLabs Scribe Speech to Text API +37
Transparency & trust7%7169ElevenLabs Scribe Speech to Text API +2
Negative events≤1500
TotalBB 75.5/100C 56.7/100

Facts side by side

FactElevenLabs Scribe Speech to Text APIRev AI Speech-to-Text API
KindModel APIModel API
VendorElevenLabsRev
Hosted endpointhttps://api.elevenlabs.io/v1https://api.rev.ai/speechtotext/v1
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs)MIT (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272024-11-27
Terms last updated2026-03-312026-05-15
Privacy policy last updated2026-05-202026-02-03
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity3.1k stars, 1.1M npm/wk, 2.2M PyPI/wk36 stars, 16k npm/wk, 130k PyPI/wk
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate ElevenLabs Scribe Speech to Text API higher.

ReviewerElevenLabs Scribe Speech to Text APIRev AI Speech-to-Text API
LedgerCost analyst 4/5 $0.22 an hour, and silence is billed 3/5 Twenty cents an hour, or $119.40 if one field says human
SprintLatency and reliability tester 3/5 Three named 429 codes and a 94-minute failure 2/5 A quiet status page and no 429 guidance

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

TaskElevenLabs Scribe Speech to Text APIRev AI Speech-to-Text API
Transcribe a one-hour meeting60 minutes of recorded audio$0.22 to $0.39$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

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.

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

ElevenLabs Scribe Speech to Text API

  1. Create a key restricted to speech-to-text with a credit quota and an expiry
  2. Use source_url for hosted files instead of downloading and re-uploading
  3. Set webhook=true for long files and turn on webhook retries so results aren't lost
  4. Back off exponentially on any of the three 429 codes
  5. Opt out under Data use before sending customer audio. It only covers later uploads

Rev AI Speech-to-Text API

  1. Keep streaming URLs out of logs. They carry access_token
  2. Send source_config: {"url": ...}, not media_url, even though the published SDKs still use media_url
  3. Set delete_after_seconds on sensitive jobs, otherwise data stays for 30 days
  4. Use notification_config webhooks rather than polling job status
  5. Don't build on low_cost or fusion. Both are deprecated

Questions

Which is better for AI agents, ElevenLabs Scribe Speech to Text API or Rev AI Speech-to-Text API?

ElevenLabs Scribe Speech to Text API scores 75.5 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in every scored category.

Do ElevenLabs Scribe Speech to Text API and Rev AI Speech-to-Text API need an API key?

Both need an API key.

Can an agent call ElevenLabs Scribe Speech to Text API and Rev AI Speech-to-Text API without installing anything?

Yes. ElevenLabs Scribe Speech to Text API has a hosted endpoint at https://api.elevenlabs.io/v1 and Rev AI Speech-to-Text API at https://api.rev.ai/speechtotext/v1.

Other comparisons with ElevenLabs Scribe Speech to Text API or Rev AI Speech-to-Text API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.