ElevenLabs Scribe Speech to Text API vs Giggy Speech to Text

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.

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.

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.

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.

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.

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.

ElevenLabs Scribe Speech to Text API 40

No x402, MPP or L402 (0). Per-hour prices and plan allowances published without a login, re-read on 1 November, $0.22 an hour for Scribe v2 and Scribe v2 Medical and $0.39 for Scribe v2 Realtime (20). Free plan with 4 hours 30 minutes of batch a month and no card, per the 1 October check; the pricing page read on 1 November doesn't say whether the free plan needs one (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40.

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.

ElevenLabs Scribe Speech to Text API 65

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys can be restricted to chosen endpoints, given a credit quota and limited to IP addresses or CIDR ranges, user keys can expire after 15 minutes to 30 days, service accounts hold keys that don't belong to a person, and leaked keys found by GitHub secret scanning are disabled, re-read on 1 November. Realtime browser clients use single-use tokens, which we don't deduct for (30). The Privacy Policy (updated 9 October 2026, re-read on 1 November) says ElevenLabs may train on personal data, with an opt-out under Data use that only covers data sent after it's set (10). Speech-to-text audio and transcripts are kept by default and zero retention through enable_logging=false is Enterprise only, though the zero retention page now names every /v1/speech-to-text/ endpoint (5). The Developers page has a Request Log that lists every API request with search, filters and CSV export, and usage can be broken down by API key, though we found no audit log of key actions below Enterprise (10 of 15, was 5). A valid security.txt (expiring 6 October 2027, re-read on 1 November) pointing to a vulnerability disclosure programme, and the Eleven v4 launch page states SOC 2 Type II, ISO 27001 and PCI DSS Level 1 certification for every ElevenLabs model. We count those as vendor claims because we saw no report, and the trust centre wasn't re-read. No bug bounty or public advisories found (10 of 20, was 5, as the ElevenLabs text-to-speech listing reads the same evidence). 30 + 10 + 5 + 10 + 10 = 65.

Giggy Speech to Text 57

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines, as for deepgram-stt and cartesia-ink-stt. Keys prefixed giggy_sk_ are shown once on creation or rotation, rejected immediately after revocation, limited to ten per space and tied to the space that made them, with REST budgets that Workspace members can set. No scopes or expiry were found. The key travels in a header only, with no query-string option documented (22 of 30). The workspace privacy guide states 'Giggy does not use user data to train models'. The privacy policy and terms draw by script and could not be read to confirm it (18 of 20). Requests can opt into 12-hour content retention and EEA-adequate compute, and a guide gives Batch audio a seven-day window, but no retention period for transcripts was found and results can vanish after an unstated 'retention cleanup' (9 of 15). Generation history per space and a request ID on errors; no audit log of key or admin actions was found (8 of 15). /.well-known/security.txt answered a client error, none of the six repositories has a SECURITY.md, and no disclosure policy, bug bounty or certification was found on the pages that rendered; the support page that may name a reporting route drew by script (0 of 20). 22+18+9+8+0 = 57.

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.

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.