Giggy Speech to Text vs Groq 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.

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).

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.

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.

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.

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).

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.

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.

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.

Groq Speech-to-Text 58

Model reading. No OpenAPI document was found in the docs, and the Python SDK's .stats.yml carries an endpoint count with no specification URL (0). llms.txt at console.groq.com with Markdown twins of the guide, model cards and reference (10). The guide says which model to pick for accuracy or price, that translation is English only and that the prompt steers style within 224 tokens, and it explains the verbose_json quality fields (15 of 20). The reference lists allowed values for response_format and timestamp_granularities[] and marks model as required, while language and url are plain strings (11 of 15). curl, Python and JavaScript examples for both endpoints and a shared errors page with a typed error object. The Batch page's sample still names distil-whisper-large-v3-en, shut down on 23 August 2025, on 1 November (12 of 15). The docs changelog is dated, its newest entry is still 18 April on 1 November and no entry in it concerns speech-to-text (10 of 15).

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.

Groq Speech-to-Text 40

No x402, MPP or L402 (0). $0.04 an audio hour for Whisper Large v3 Turbo and $0.111 for Whisper Large v3 on the models page and model cards, read without a login (20). The free plan needs no card and includes both Whisper models at its own rate limits (20). A person signs up in the console in a browser (0).