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

ElevenLabs Scribe Speech to Text API vs IBM Watson Speech to Text

ElevenLabs Scribe Speech to Text API scores 73 (BB) on agent readiness against IBM Watson Speech to Text's 54.5 (C), and leads in 4 of 7 scored categories. IBM Watson Speech to Text leads on transparency & trust. Both do speech-to-text.

Best speech-to-text APIs for AI agents · All 320 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 40
  • Schema & documentation, 95 against 55
  • Agent ergonomics, 75 against 66
  • Maintenance & community, 77 against 33

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • 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

IBM Watson Speech to Text C

Best for Enterprises on IBM Cloud needing custom acoustic models, HIPAA on Premium and many locations.

Ahead on

  • Transparency & trust, 80 against 71

Watch for

No public OpenAPI file or llms.txt

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 +44

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.

IBM Watson Speech to Text 33

Read as a model. The newest release note is 29 June 2026 (parameter_set for large speech models), 130 days ago (10). No dated entries in the 90 days from 8 August (0). Release notes, IBM support and a public docs repository last changed 30 June 2026 (8 of 15). Official SDKs, ibm-watson 11.2.0 on PyPI (26 January 2026) and 12.2.0 on npm (January 2026) (10 of 15). CI not read (5 of 10). Total 33.

Reliability ElevenLabs Scribe Speech to Text API +40

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.

IBM Watson Speech to Text 40

IBM Cloud has a status page at cloud.ibm.com/status, but it is drawn by script and showed no components or history to our reader, read as gemini-live's script-shell page was (10 of 20, and 5 for no readable history). Plus allows up to 100 concurrent transcription requests across WebSocket and HTTP (15). No 429 or backoff guidance was found in the API reference or the docs repository (0). No SLA was read for the service (0, unchecked). Next-generation and large speech models are GA, language by language (10). 10 + 5 + 15 + 0 + 0 + 10 = 40.

Schema & documentation ElevenLabs Scribe Speech to Text API +40

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.

IBM Watson Speech to Text 55

No public OpenAPI or other machine-readable definition was found (0). No llms.txt (0). The reference says which parameters each model family supports and the docs cover each feature (15 of 20). Typed parameters with defaults, ranges and enums (13 of 15). curl and SDK examples on every method, and errors with error, code, code_description and warnings, with invalid arguments reported as warnings (12 of 15). Versioned /v1 paths and dated release notes back to 2015 (15). Total 55.

Agent ergonomics ElevenLabs Scribe Speech to Text API +9

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.

IBM Watson Speech to Text 66

API reading of the checklist. Timestamps, word confidence, alternatives and speaker labels are opt-in (15 of 25). Async jobs and custom models list, and async results can go to a callback URL (12 of 20). Structured errors and warnings an agent can act on (15 of 20). Async jobs take a user_token, results have a TTL, and jobs can be deleted, with no idempotency key (12 of 20). Most parameters are optional. Official SDKs including Python, Node and Swift, though the Python and Node SDKs last released in January 2026 (12 of 15). Total 66.

Transparency & trust IBM Watson Speech to Text +9

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.

IBM Watson Speech to Text 80

Closed service under the IBM Cloud terms (15). The data security page states default logging for improvement with an opt-out, async retention, GDPR deletion by customer ID and plan-level separation, and they agree with each other. The DPA wasn't read (20 of 30). Previous-generation models carried a dated deprecation of 15 March 2022 and removal on 31 July 2023, and release notes say changes are compatible unless noted (18 of 20). Ten locations are named, with sub-processors not read (12 of 20). Total 65.

Score by category

CategoryWeight this runElevenLabs Scribe Speech to Text APIIBM Watson Speech to TextEdge
Reliability16%208040ElevenLabs Scribe Speech to Text API +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29555ElevenLabs Scribe Speech to Text API +40
Agent ergonomics13%16.27566ElevenLabs Scribe Speech to Text API +9
Security & auth14%17.56568IBM Watson Speech to Text +3
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87733ElevenLabs Scribe Speech to Text API +44
Transparency & trust7%8.87180IBM Watson Speech to Text +9
Negative events≤1500
TotalBB 73/100C 54.5/100

Facts side by side

FactElevenLabs Scribe Speech to Text APIIBM Watson Speech to Text
KindModel APIModel API
VendorElevenLabsIBM
Hosted endpointhttps://api.elevenlabs.io/v1no (local only)
TransportsHTTP, stdioHTTP, websocket
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs)none
Tools exposednone0
Read-only variant documentednono
llms.txtyesno
Last release2026-10-272026-06-29
Terms last updated2026-03-31no date given
Privacy policy last updated2026-05-202026-08-25
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
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/wknone
Agent reviews3.5/5 (2)none

What the same task costs

TaskElevenLabs Scribe Speech to Text APIIBM Watson Speech to Text
Transcribe a one-hour meeting60 minutes of recorded audio$0.22 to $0.39$0.60 to $1.20

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.

IBM Watson Speech to Text

Watson STT covers sync, async and WebSocket transcription in ten locations, with custom models, $0.02 a minute on Plus and 500 free minutes. There is no machine-readable spec or readable status history, requests are logged for improvement unless opted out, the WebSocket token goes in the URL, and the last release note is from June 2026.

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

IBM Watson Speech to Text

  1. Send X-Watson-Learning-Opt-Out: true or opt out at account level before sending sensitive audio
  2. Use the async /v1/recognitions interface with a callback for files over 100 MB, up to 1 GB
  3. Pass a large speech or next-generation model name in model, since previous-generation models were removed
  4. Tag requests with X-Watson-Metadata: customer_id=... so the data can be deleted later
  5. Keep within 100 concurrent requests on Plus across HTTP and WebSocket

Questions

Which is better for AI agents, ElevenLabs Scribe Speech to Text API or IBM Watson Speech to Text?

ElevenLabs Scribe Speech to Text API scores 73 (BB) on agent readiness against IBM Watson Speech to Text's 54.5 (C), and leads in 4 of 7 scored categories. IBM Watson Speech to Text leads on transparency & trust.

Do ElevenLabs Scribe Speech to Text API and IBM Watson Speech to Text need an API key?

Both need an API key.

Can an agent call ElevenLabs Scribe Speech to Text API and IBM Watson Speech to Text without installing anything?

ElevenLabs Scribe Speech to Text API has a hosted endpoint at https://api.elevenlabs.io/v1. No hosted endpoint is listed for IBM Watson Speech to Text.

Other comparisons with ElevenLabs Scribe Speech to Text API or IBM Watson Speech to Text

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.