AssemblyAI Speech-to-Text (Universal) vs Giggy Speech to Text

AssemblyAI Speech-to-Text (Universal) 77

Closed service with clear terms (15). Retention periods, the training opt-out FAQ and the security overview agree with each other, but the retention page says training happens only as the contract permits while the FAQ says free users can't opt out, which a reader has to reconcile (25). Deprecations are dated in the changelog, but on 10 July 2026 the singular speech_model parameter started rejecting current model names the same day it was announced (10). Subprocessor list at /legal/subprocessors and US and EU endpoints (20).

Giggy Speech to Text 30

Closed hosted service. The terms exist at /terms but draw by script and could not be read, so their clarity is unknown; the SDK, Pipecat and MCP repositories are ISC and the n8n node MIT (5 of 30). What could be read agrees with itself, no training on user data, an optional 12-hour retention flag, a seven-day window for Batch audio, and the EEA compute flag. The privacy policy, any DPA and a retention period for transcripts were not found or not readable (12 of 30). No deprecation policy or dated notices, only a statement that the legacy origin remains supported (3 of 20). No subprocessors or data locations are named; the EEA-adequate compute option implies processing outside the EEA by default without saying where (3 of 20). 5+12+3+3 = 23.

AssemblyAI Speech-to-Text (Universal) 85

Statuspage at status.assemblyai.com with component history, read from history.atom on 1 November (20). Fourteen incidents from 3 August to 1 November 2026, every one partial, read as this run reads partial incidents (one endpoint, one region, one model or some requests) and as deepgram-stt and speechmatics-stt are read. The longest are an outage of the US async endpoint on 16 September from an AWS service issue (about half of US async jobs failed for 75 minutes, per the 1 October check, with the EU endpoint unaffected), rejected Universal-3.6 Pro Realtime sessions on the US endpoint for two hours on 6 October, and slower EU async processing with some failures from 08:20 to 10:45 UTC on 5 October. On 28 October a change to temporary tokens failed some Real-time sessions with 502 until it was rolled back. The 31 July us-east streaming fault left the window on 30 October. Minor only (20). Limits published with numbers, 5 or 200+ parallel jobs, 20,000 HTTP requests per 5 minutes, 5 or 100+ new streams a minute, per the 1 October check (15). Overload handling is partly documented. Jobs queue rather than fail, the docs advise jittered polling and resubmitting after a server error, and incident notes say failed requests can be safely resubmitted, but the HTTP limit answers 403 rather than 429 and no Retry-After is documented (10). A 99.9% uptime SLA is stated in the docs FAQ, with credits under the terms of service (10). Async, streaming and Sync APIs are GA (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Giggy Speech to Text 50

Hosted reading, as for deepgram-stt and cartesia-ink-stt. Giggy's own status page at https://giggy.ai/status lists one component, Text to speech, operational on 4 November 2026 with 98.61 per cent observed availability and 99.85 per cent completion over 14 days, refreshed every 30 minutes. It has no speech-to-text component and no incident log, so it shows nothing about this surface (5 of 20). No readable incident history, so the floor (5). Rate limits are published per credential, 60 Batch generation POSTs, 120 event-stream GETs, 600 reads and 120 MCP requests a minute, with eight live contexts per controller; Fast and Streaming POSTs have no per-credential limit and Batch queue capacity isn't given (15). 429 carries Retry-After with RateLimit-* headers, and the docs give a safe-retry rule for uploads, read the generation by UUID after a timeout or 504 and never upload the same recording again. REST transcription has no idempotency key, but the MCP transcribe_audio tool takes one (15). No SLA on the pricing page or in the docs; the terms could not be read (0). No beta or preview label on the API, the SDKs or the MCP server (10). 5+5+15+15+0+10 = 50.

AssemblyAI Speech-to-Text (Universal) 95

OpenAPI 3.1 at /docs/openapi.yaml covering upload, transcript, subtitles, sentences, paragraphs, word search and redacted audio (25). llms.txt at /docs/llms.txt (10). Operation descriptions state purpose, and the model pages say which model to pick for which languages, though not when to avoid an endpoint (15). Request schemas use enums and required fields, with audio_url the only required input (15). 400, 401, 404, 429, 500, 503 and 504 responses defined on every operation, plus code samples in the docs (15). Versioned /v2 paths and a dated public changelog (15).

Giggy Speech to Text 68

Model reading, with the API reference. The docs and llms.txt link an OpenAPI 3.1 file at https://api.giggy.ai/v1/openapi.json, but api.giggy.ai's robots.txt could not be read, so the file wasn't fetched. We credit only what the reference pages show of it, typed mode values, the privacy booleans and a typed error body, and there is no AsyncAPI file for the live socket (12 of 25). llms.txt and llms-full.txt (10). The docs say when to use each mode and transport, that MCP is not a live transport, that an OpenAI base-URL swap does not work for STT, and which options have no equivalent, more than most listings say about when not to use something (17 of 20). mode is an enum of three values and the input format is fixed, but language is a free code or name with no published list, and the MCP input schemas were read only from the repository's docs, not from the server (11 of 15). Examples in the SDK READMEs, the examples repository and a Postman collection, and an error table of ten statuses with type, code, message, status, request_id and param fields, though only one code value is named (11 of 15). Paths are under /v1 and the SDK and Pipecat repositories keep CHANGELOG.md files, dated in two of them, but there is no service changelog (7 of 15). 12+10+17+11+11+7 = 68.

AssemblyAI Speech-to-Text (Universal) 80

API reading of the checklist. Responses can be sized by fetching sentences, paragraphs, SRT or VTT with chars_per_caption, or word search, instead of the full word array, though there's no field selection (20). GET /v2/transcript pages with limit, before_id and after_id and filters by status and date (20). Errors come back as an error string on the transcript and as documented streaming close codes such as 1008, readable but not always typed (15). No idempotency key, and a resubmitted job is a new billed job. The retry guide covers server errors only (10). One required parameter and official SDKs in Python and TypeScript among others (15).

Giggy Speech to Text 68

API reading, as for the other speech-to-text listings. The transcript is compact, text, detected languages, audio duration and model metadata, with no word array to trim; on an MCP reading five tools would score 25 (20 of 25). Nothing to page through and no output options, no timestamps, subtitles or speaker labels, and recorded input must be PCM16 mono 16 kHz WAV, so the caller converts everything else; a 12-hour recording goes up in one request (10 of 20). Errors are structured with a type, code, message, status, request ID and parameter, and the reference says what each status means and what to do after a 504, but no list of code values was found and the SDK error classes expose only the status and the raw body (13 of 20). Upload retries are left to the caller with clear rules, read the generation first and never re-upload after a timeout; REST has no idempotency key and client_request_id is documented as no guarantee, while MCP transcribe_audio takes an idempotency_key. The SDKs never retry, and closing an unfinished live socket cancels it (13 of 20). Only the audio is required, with official Python and Node SDKs, but raw REST and MCP default to paid Fast while the SDKs default to free Batch (12 of 15). 20+10+13+13+12 = 68.

AssemblyAI Speech-to-Text (Universal) 40

No x402, MPP or L402 (0). Per-hour prices for every model and add-on published without a login (20). Free tier of up to 185 hours pre-recorded or 333 hours streaming with no card (20). A person has to sign up in a browser to get a key (0).

Giggy Speech to Text 30

No x402, MPP or L402 (0). Per-hour prices for Batch, Fast and Streaming and every credit pack published without a login (20). Free Batch transcription and Personal free credits topped up to 10,000 a month, but no page read says whether a card is needed, so half, as other listings read an unstated card requirement (10 of 20). A person signs up in a browser and creates the key there; no programmatic key route was found (0). 0+20+10+0 = 30.

AssemblyAI Speech-to-Text (Universal) 79

Read as a model, for deprecation notice and support rather than release counts and issue replies, on the lines deepgram-stt, gladia-stt and speechmatics-stt use in this run. Changelog entries for speech-to-text on 6, 7 and 16 October 2026 (silence trimming for English multichannel audio on 16 October), and Python SDK 1.6.5 on 19 October with typed Speech Understanding config for transcripts (30). Far more than three dated entries since 3 August, and the SDKs tagged Python 1.5.2 to 1.8.2 and Node 4.40.0 to 4.42.0 in the period (10 of 10). No deprecation policy, but removals carry dates. Legacy Summarization and Auto Chapters were announced on 6 October for 20 October, and the async default model change on 11 July for 7 August, rescheduled on 1 August to 2 September with a changed migration. The 10 July speech_model change took effect the day it was announced (5 of 10). Public changelog and a support address (10 of 15). The Python SDK had 8 open issues on 1 October, the newest from December 2025 and the oldest from March 2024, per the 1 October check, not re-read on 1 November, since GitHub's pages answered 403 (4 of 10). Official SDKs current, Python 1.8.2 on 23 October and Node 4.42.0 on 26 October (15). Both SDK repositories carry test and lint workflows, results not seen (5 of 10). 30 + 10 + 5 + 10 + 4 + 15 + 5 = 79.

Giggy Speech to Text 69

Read as a model, on the lines deepgram-stt and cartesia-ink-stt use (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The Python and Node SDKs released 0.2.1 and the Pipecat adapter 0.3.3 on 1 November 2026, and the examples and MCP repositories changed on 3 November (30). Since 7 October the Node SDK has four tagged releases, the Python SDK six and the Pipecat adapter six, the STT ones from 12 October (10). No deprecation policy or dated notice. The legacy https://giggy.ai/v1 origin and older SDK transports are kept 'for existing integrations' with no end date (2 of 10). No service changelog; the support and contact pages drew by script, and GitHub issues is the support URL in the plugin manifest (5 of 15). GitHub issues and reply times could not be read, since the GitHub API was not available to this session (0 of 10). Official SDKs current, giggy and @giggy-ai/sdk at 0.2.1 on PyPI and npm (15). CI workflows in five repositories and publish workflows, the n8n node through npm OIDC with provenance, and two runtime dependencies in each SDK; run results not seen (7 of 10). 30+10+2+5+0+15+7 = 69.