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

Gladia Speech-to-Text API + MCP vs Rev AI Speech-to-Text API

Gladia Speech-to-Text API + MCP scores 72.3 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in 5 of 7 scored categories. Rev AI Speech-to-Text API leads on reliability. Both do speech-to-text.

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

Which one, for what

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

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

Self-serve audio is used for model training by default unless the account opts out

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.

Ahead on

  • Reliability, 75 against 70

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.

Payments & pricing Gladia Speech-to-Text API + MCP +30

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.

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.

Maintenance & community Gladia Speech-to-Text API + MCP +30

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.

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.

Security & auth Gladia Speech-to-Text API + MCP +25

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.

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 Gladia Speech-to-Text API + MCP +23

Gladia Speech-to-Text API + MCP 75

API reading of the checklist. Add-ons such as summaries, NER and translation are opt-in, so a plain request stays small, but there's no field selection (15). Pre-recorded jobs list with offset, limit and filters (20). Documented error codes, with a 429 for concurrency (15). No idempotency key. The docs warn that a job is already queued once the 200 or transcription.created webhook arrives, which is safe-retry guidance of a sort (10). One required parameter and official SDKs in JavaScript and Python (15). The official MCP server adds 8 tools for async jobs, which this API reading doesn't score.

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 Gladia Speech-to-Text API + MCP +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).

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 Rev AI Speech-to-Text API +5

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.

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

CategoryWeightGladia Speech-to-Text API + MCPRev AI Speech-to-Text APIEdge
Reliability16%7075Rev AI Speech-to-Text API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9580Gladia Speech-to-Text API + MCP +15
Agent ergonomics13%7552Gladia Speech-to-Text API + MCP +23
Security & auth14%6540Gladia Speech-to-Text API + MCP +25
Payments & pricing10%6030Gladia Speech-to-Text API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7040Gladia Speech-to-Text API + MCP +30
Transparency & trust7%6569Rev AI Speech-to-Text API +4
Negative events≤1500
TotalBB 72.3/100C 56.7/100

Facts side by side

FactGladia Speech-to-Text API + MCPRev AI Speech-to-Text API
KindModel APIModel API
VendorGladiaRev
Hosted endpointhttps://api.gladia.io/v2https://api.rev.ai/speechtotext/v1
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs and MCP server)MIT (SDKs)
Tools exposed8none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-232024-11-27
Terms last updatedno date given2026-05-15
Privacy policy last updatedno date given2026-02-03
Customer content may train modelsnot found in the textyes
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 noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity4 stars, 4.8k npm/wk, 126k PyPI/wk36 stars, 16k npm/wk, 130k PyPI/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Gladia Speech-to-Text API + MCP higher.

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

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.

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

Gladia Speech-to-Text API + MCP

  1. Don't resubmit a pre-recorded job after a 200 or a transcription.created webhook. It's already queued
  2. Pick solaria-3 only for async EN, FR, DE, ES or IT audio. Anything live or multilingual needs solaria-1
  3. A 429 means the concurrency limit, 3 async and 1 live on the free plan. Wait for a running job to finish
  4. Opt the account out of model training in its profile before sending sensitive audio on Self-serve
  5. Split files over 135 minutes or 1,000 MB

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, Gladia Speech-to-Text API + MCP or Rev AI Speech-to-Text API?

Gladia Speech-to-Text API + MCP scores 72.3 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in 5 of 7 scored categories. Rev AI Speech-to-Text API leads on reliability.

Do Gladia Speech-to-Text API + MCP and Rev AI Speech-to-Text API need an API key?

Both need an API key.

Can an agent call Gladia Speech-to-Text API + MCP and Rev AI Speech-to-Text API without installing anything?

Yes. Gladia Speech-to-Text API + MCP has a hosted endpoint at https://api.gladia.io/v2 and Rev AI Speech-to-Text API at https://api.rev.ai/speechtotext/v1.

Other comparisons with Gladia Speech-to-Text API + MCP 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.