Groq Speech-to-Text vs IBM Watson Speech to Text

Groq Speech-to-Text 90

Hosted reading. The status page at groqstatus.com (incident.io) lists whisper-large-v3 and whisper-large-v3-turbo as separate production components (20). On 1 November 2026 it showed both at 100% uptime from 3 August to 1 November with "No incidents", and neither its RSS feed nor the incident pages it links names either model. The window's three incidents were on other components (an enterprise preview model on 10 and 12 October, and console errors on 12 October that Groq said did not affect inference), plus maintenance on 9 and 18 October (30). The rate limits page gives numbers for both models, 20 requests a minute, 2,000 a day, 7,200 audio seconds an hour and 28,800 a day on the free plan, re-read on 1 November, and the models page gives 300 requests a minute and 200,000 audio seconds an hour (v3) and 400 and 400,000 (Turbo) on the Developer plan (15). A 429 carries retry-after, the security onboarding page says to back off exponentially on 429 and 5xx, and transcription is a stateless call (15). The enterprise Performance Tier's 99.9% availability SLA names three language models and neither Whisper model, per the 8 October check, so no SLA was found for this product (0). Both models are listed as production models (10). 20+30+15+15+0+10 = 90.

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.

Groq Speech-to-Text 48

Model reading, as for the GroqCloud listing, counting changes to this listing's own models and endpoints, as the OpenAI listings read their own models and the AWS listings their own service models. No dated change to speech-to-text was found in 2026. The Python SDK 1.7.0 (tag 25 August, uploaded to PyPI on 26 August 2026 per the 8 October check) and TypeScript SDK 1.6.0 (25 August) add chat reasoning guidance, CI workflows and lock-file updates and leave the audio code untouched. The last SDK change to the transcription code was Python 1.2.0 on 18 April 2026. A release that doesn't change this service can't set the recency line in this run, as for the Azure Translator listing, and Muse Spark Open's 15 October preview is a chat model, counted on the GroqCloud listing. So no change within 180 days was found (0, was 20). The deprecations page promises an email and a named replacement and states no minimum notice. The one speech-to-text retirement on it is distil-whisper-large-v3-en on 23 August 2025, and the newest announcement is 24 August 2026, for Compound (4 of 12). Neither Whisper model was retired or renamed in the last 90 days (8 of 8). A dated docs changelog with a feed exists, its newest entry is 18 April and none of its entries concern speech-to-text (8 of 15). SDK issue replies not sampled (5 of 10). Official groq 1.7.0 on PyPI and groq-sdk 1.6.0 on npm, per the tags (15). CI, release automation and lock-file vulnerability fixes in 1.7.0 (8 of 10). 0+4+8+8+5+15+8 = 48.

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.

Groq Speech-to-Text 79

Model reading, scored like the GroqCloud listing. Bearer keys belong to one project, each project has its own rate limits per model, and the security onboarding page covers rotation and immediate revocation. No way to limit a key to the audio endpoints was found (26 of 30). The services agreement, last modified 22 June 2026, says Groq may not use inputs or outputs for training or fine-tuning unless the customer grants permission (20). Inputs and outputs are not retained by default, logs kept for reliability or abuse last up to 30 days, and the data page lists both audio endpoints as eligible for zero data retention, a setting in Data Controls (15). Usage data and request logs per project and a read-only Reader role. No audit log of administrative actions was found (10 of 15). security.txt on groq.com holds a Contact line only, with no expiry date. The DPA commits to SOC 2 Type II audits, and the trust centre at trust.groq.com is drawn by script and was not read (8 of 20).

IBM Watson Speech to Text 68

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. IAM API keys per instance with Reader, Writer and Manager roles and short-lived bearer tokens (30). The WebSocket interface takes the token as an access_token query parameter, so 10 off (20 of 30). Request and response data are logged by default to improve the service, and any account can opt out per account or per request (10 of 20). Async results expire after a week by default (results_ttl shortens it), a delete method exists, and DELETE /v1/user_data removes data by customer ID (10 of 15). Activity Tracker events record changes to the service's state (10 of 15). Valid security.txt to 6 December 2026, PSIRT and HackerOne, HIPAA readiness on Premium. Certifications weren't read (18 of 20). Total 68.

Groq Speech-to-Text 75

API reading, as for the other speech-to-text listings. The default response is the text alone, text returns a bare string, and segments and word timestamps come only with verbose_json. srt and vtt are listed as unsupported (18 of 25). There is no transcript store to page through. Volume goes through the Batch API by url, and a file over 25 MB (free) or 100 MB (Developer) has to be chunked by the caller (12 of 20). The errors page gives 13 status codes with a recovery line each and an error object of message and type, with no machine-readable code field (15 of 20). The call is stateless and safe to retry, and the SDKs retry connection errors, 408, 409, 429 and 5xx by default. No idempotency key exists or is needed (15 of 20). model and one of file or url are the only required fields, with official Python and TypeScript SDKs and OpenAI SDK compatibility (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.

Groq Speech-to-Text 85

The hosted service is closed under the Groq Services Agreement. Both models are OpenAI's published Whisper weights, linked from each model card, served with Groq's own quantisation, and the SDKs are Apache-2.0 (20 of 30). The data page, the services agreement and the DPA agree on retention and on the training ban. The agreement limits zero retention to 'Eligible Customers' while the data page says all customers may enable it, and the privacy policy effective 12 November 2025 says it does not cover customer data sent to GroqCloud (26 of 30). A deprecations page with dated history and replacements, with no minimum notice period (14 of 20). Customer data is kept in Google Cloud storage in the United States, and the DPA gives 15 days' notice of sub-processor changes to subscribers. The sub-processor list is in the trust centre we could not read (12 of 20).

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.