Deepgram Speech-to-Text (Nova-3, Flux) vs IBM Watson Speech to Text

Deepgram Speech-to-Text (Nova-3, Flux) 80

Statuspage at status.deepgram.com with component history and an RSS feed (20). Nine incidents in the 90 days from 3 August touch speech-to-text, every one partial, read as this run reads partial incidents (one model, one region, one datacenter or some requests) and as deepgram-tts is read. Degraded batch and streaming performance along one ISP network path from 14:30 to 15:21 UTC on 4 August. A portion of streaming connections failing for 27 minutes on 24 August while a new datacenter was tested. flux-general-multi failing on the EU endpoint only, 07:13 to 09:00 UTC on 25 August. Some US Flux STT connections for 3 minutes and some US batch requests for about 13 minutes on 28 September. Two 1 to 2 minute bursts on 30 September. Some batch requests slow or timing out, 19:27 to 21:53 UTC on 22 October. 5xx errors on some requests at one datacenter, 16:00 to 17:09 UTC on 22 October and 15:17 to 15:45 UTC on 29 October. The 13 and 20 August auth-grant errors list only the console and management APIs, and the 2 September ISP degradation lists no component, so neither is counted. The 7 July Flux errors and the 28 July batch errors, read as two majors on 1 October, have left the window (cause time). Minor only (20). Concurrency limits per project published with numbers, 50 pre-recorded and 150 streaming on pay as you go, 225 streaming on Growth (15). Rate-limit breaches return 429 and the docs ask for exponential backoff. Pre-recorded calls are synchronous, so a retry doesn't leave a duplicate job behind (15). No SLA found for self-serve plans (0). Nova-3 and Flux are GA (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.

Deepgram Speech-to-Text (Nova-3, Flux) 95

OpenAPI file at developers.deepgram.com/openapi.json and an AsyncAPI file for the sockets (25). llms.txt (10). Reference pages state what each option does, and the docs say to use Flux for live agents and Nova-3 for files, though few options say when not to use them (15). Query parameters are typed with enums for model, language and encoding (15). Examples on every endpoint and a documented error format (15). Versioned /v1 and /v2 paths and a dated changelog (15).

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.

Deepgram Speech-to-Text (Nova-3, Flux) 73

Read as a model, as deepgram-tts is read on the same changelog and SDK. Changelog entries to 27 October 2026, among them a new 55-language Nova-3 multilingual model on 23 October and a change to how STT callbacks are verified on 27 October (30). 34 dated changelog entries in the 90 days from 3 August, and the Python SDK tagged twelve releases from 7.7.0 on 12 August to 7.16.0 on 28 October (10 of 10). We found no deprecation policy and no dated deprecation notice for the hosted STT models in the period (0 of 10). Public changelog and community support channels (10 of 15). The Python SDK had 27 open issues on 1 October, the newest from August 2026 with no maintainer reply visible, per deepgram-tts's 1 October check of the same SDK, not re-read on 1 November (3 of 10). Official SDKs current, the Python SDK at 7.16.0 on 28 October (15). SDK CI not checked in this run (5 of 10). 30 + 10 + 0 + 10 + 3 + 15 + 5 = 73.

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.

Deepgram Speech-to-Text (Nova-3, Flux) 75

API reading of the checklist. Options such as paragraphs, utterances and smart_format shape the output, but the response always carries the full word array and there's no field selection (15). The request history endpoint pages and filters by date and status (20). Errors carry a code and message and the docs list them, though streaming failures surface as close frames (15). No idempotency key, and a retried pre-recorded call is billed again (10). Only the audio is required. Official SDKs in six languages, including Python, JavaScript, Go, .NET and Java (15).

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.