Giggy Speech to Text vs Soniox Speech-to-Text

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.

Soniox Speech-to-Text 76

Closed service with clear terms, last updated 2026-06-29, and an Apache-2.0 Python SDK (15). The security page, limits page and pricing page agree on no training, no default retention and 30-day async deletion (25). Model retirements are dated and old names route to the new model (v5 to v6 on 15 December 2026), though the October 2025 retirement of the preview models was described as accelerated (15). A data residency page names region-specific domains for the US, EU, Japan and India, and no sub-processor list was found (15).

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.

Soniox Speech-to-Text 87

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. "Every API key in a project has a list of permissions": real-time STT, async STT and Files with Read and Write levels, model listing, usage and temporary keys, with permission_denied for anything else, and temporary keys that are restricted and expire. Keys go in the WebSocket handshake rather than the URL (30). Customer audio and transcripts are never used for training, per the 1 October check (20). Audio and transcripts aren't retained by default, and async files and transcripts auto-delete after 30 days or on a delete call, per the 1 October check (15). Per-request usage logs with request IDs, duration, tokens and cost (10). SOC 2 Type 2 and ISO/IEC 27001:2022, and the Python SDK's SECURITY.md gives a disclosure route with no acknowledgement time, as soniox-tts. No security.txt (404) and no bug bounty (12). 30+20+15+10+12 = 87.

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.

Soniox Speech-to-Text 77

Instatus page at status.soniox.com with per-region components and a paged history (20). Minor incidents only since 6 August, with 70 minutes of failed API key creation in the console on 24 August, failed new WebSocket connections to stt-rt.eu.soniox.com between 12:50 and 13:03 UTC on 25 August (existing connections unaffected), and 45 minutes of real-time overload in the Japan region on 8 September ("some customers", partial). October and November have no notices (20). Limits published with numbers, 100 requests a minute, 10 concurrent streams, a connection limit derived from them and a fixed 300-minute stream cap (15). The errors reference documents limit_exceeded as HTTP 429 on REST and the STT WebSocket with what to do for each limit, "retry with exponential backoff" for 503 service_unavailable, and resubmitting failed async jobs, which aren't auto-retried. No idempotency key, so safe-retry guidance without one (12), as soniox-tts. No SLA found (0). stt-rt-v6 and stt-async-v6 are active and the v5 models deprecated, with no preview label (10). 20+20+15+12+0+10 = 77.

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.

Soniox Speech-to-Text 85

docs.soniox.com/openapi.yaml, OpenAPI 3.1.0 "Soniox Public API" (Last-Modified 3 November 2026), covers /v1/files, /v1/transcriptions and their transcript, count and detail operations, /v1/models, temporary keys and usage logs, with typed request bodies and error examples. No AsyncAPI file for the WebSocket (25). llms.txt with Markdown pages (10). Guides state purpose and say when to use the real-time or async API (15). Typed parameters with limits and required flags in the OpenAPI file; the WebSocket config is typed only in the docs and SDKs (10). Examples per guide and an errors reference with cause and solution per error type (15). Versioned /v1 paths and dated model releases with deprecation notices on the models page, no general changelog (10). 25+10+15+10+15+10 = 85.

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.

Soniox Speech-to-Text 20

No x402, MPP or L402 (0). Token prices published without a login, with Soniox's own per-hour estimates (20). No free credits for new sign-ups since 2025-10-27 (0). A person signs up in a browser (0).

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.

Soniox Speech-to-Text 75

Read on the model lines the other Soniox listings use (recency 30, dated releases 10, notice 10, support 15, issues 10, SDKs 15, health 10), where the 1 October note used the tool lines. stt-rt-v6 and stt-async-v6 released on 3 November 2026, with Python SDK 2.11.0 (agent text input on RealtimeSTTConfig) and soniox-js v2026.11.03 ("Feat/v6 support") the same day (30). Since 6 August, the releases that touch STT code are Python 2.9.0 (11 August, async STT and files), 2.10.0 (2 October, realtime STT authentication), 2.11.0, soniox-js v2026.10.12 (12 October, realtime STT authentication) and v2026.11.03, plus the v6 model entry (10). For notice, the v5 models are removed on 15 December 2026, 42 days after the notice, with requests routed to v6, and WebSocket api_key authentication ends on 15 January 2027 with a migration guide; v4 had 14 days (5). A community and support page, with no reply times read (5). SDK issues unread, github.com 403 (3). Current Python and Node SDKs (15). soniox-js runs CI (.github/workflows/ci.yml), the Python repository has tests and uv.lock but no CI workflow (7). 30+10+5+5+3+15+7 = 75.