Google Cloud Speech-to-Text vs IBM Watson Speech to Text

Google Cloud Speech-to-Text 75

Google Cloud status page with a per-product history (20). One incident lists Speech-to-Text in the 90 days from 3 August, the europe-west2 incident of 20 October, 06:00 to 12:08 UTC, which named 38 products in that one region. A single-region incident is partial and read as minor, as this run reads partial incidents. The other three Google Cloud incidents since 3 August (20 August, 1 September, 8 and 9 October) don't list Speech-to-Text. The public page only shows broad incidents. Minor only (20). Quotas published with numbers, 300 concurrent streams, 300 sync and 150 batch requests a minute per region, streams up to 5 minutes and sync up to 1 minute (15). The Speech quotas page (last updated 26 October 2026) still says nothing about the error a quota breach returns or how to back off, and we don't count Google's general API design guide for this API (0). Speech-to-Text SLA of 99.9 per cent monthly uptime with credits of 10 to 50 per cent, per the 1 October check, not re-read on 1 November (10). Chirp 3 GA since 2025-10-13 in us and eu, though 82 of its 111 locales were preview on 1 October (10). 20 + 20 + 15 + 0 + 10 + 10 = 75.

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.

Google Cloud Speech-to-Text 80

The API surface is public as protocol buffers and a discovery document, a machine-readable contract (25). No llms.txt found (0). Method descriptions state purpose, and the model pages say which model suits which audio, but not when to avoid sync or streaming (15). Typed proto messages with enums and required fields, no free-form blobs (15). Errors follow Google's standard status codes, with samples in the docs but little per-method error detail (10). Versioned v1 and v2 with release notes (15). The V2 discovery document read on 1 November is revision 20261001, with 26 methods and 69 schemas.

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.

Google Cloud Speech-to-Text 20

No x402, MPP or L402 (0). Per-minute prices with volume tiers published without a login (20). The 60 free V1 minutes and the $300 new-account credit both need a billing account with a card (0). A person signs up in a browser (0).

IBM Watson Speech to Text 40

No x402, MPP or L402 (0). Per-minute Plus prices published in the docs without a login (20). The Lite plan gives 500 free minutes a month, and no page read says a card is needed (20). A person creates an IBM Cloud account and service instance in a browser (0). Total 40.

Google Cloud Speech-to-Text 85

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. OAuth 2.0 with service accounts and IAM roles, scoped per project, no API key in the documented V2 flow. The token can also travel in the URL. Google's OAuth guide accepts it as an access_token query parameter, the V2 discovery document (revision 20261001) lists access_token, oauth_token and key as query parameters, and on 1 November speech.googleapis.com/v2/projects/example-project/locations/global/recognizers answered 401 "missing required authentication credential" with no token and 401 "invalid authentication credentials" with a made-up ?access_token=, so the token is read from the query string. That takes the 10-point deduction, as every Google API listing does in this run (Gmail, Sheets, Drive and Calendar on 17 October, Ads, Model Armor, Secret Manager and Document AI on 1 November) (20). Audio isn't used for training unless the project opts in to data logging (20). Streaming and sync audio is processed in memory and not stored, and batch results are kept for a short window (15). Cloud Audit Logs cover Google Cloud APIs, though we didn't confirm which Speech methods they record (10). Valid security.txt, Google's vulnerability reward programme, SOC 2 and ISO 27001, and public Cloud security bulletins (20). 20 + 20 + 15 + 10 + 20 = 85.

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.

Google Cloud Speech-to-Text 25

The newest release note is still 2025-11-13, Chirp 3 preview in four more regions (page last updated 26 October 2026), 353 days ago (0). In the 90 days from 3 August we counted no release note and one Python client release, google-cloud-speech 2.41.0 on 1 October, whose only change is declaring Python 3.15 support. A release that doesn't change the service counts half on the 90-day line and can't set the recency line, so neither line moves (0). The last client release that touched the API was 2.37.0 on 26 February 2026 (endpointing sensitivity for streaming). Release notes, a public issue tracker and paid support (10). Official client libraries in seven or more languages (10). Package CI not checked (5). 0 + 0 + 10 + 10 + 5 = 25.

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.

Google Cloud Speech-to-Text 87

Closed service under the Google Cloud terms (15). The data logging page, the terms and the privacy notice agree that audio isn't used for training without opt-in, and a data processing addendum and sub-processor list exist (25). Google Cloud's terms carry a notice period before a GA capability is discontinued, but we found no dated Speech-to-Text deprecation notices (15). us and eu multi-region endpoints and a public sub-processor list (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.