# Giggy Speech to Text vs MiniMax Speech-to-Text (slim)

> Giggy Speech to Text scores 54.5 (C) to MiniMax Speech-to-Text's 48.4 (D) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/giggy-stt-vs-minimax-stt.md (~5,100 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/giggy-stt-vs-minimax-stt.json · canonical https://www.anchorterminal.com/compare/giggy-stt-vs-minimax-stt
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Giggy Speech to Text scores 54.5 (C) on agent readiness against MiniMax Speech-to-Text's 48.4 (D), and leads in 4 of 7 scored categories. MiniMax Speech-to-Text leads on schema & documentation and transparency & trust. Both do speech-to-text.

- Giggy Speech to Text: C 54.5, rank #903 of 1486 · https://www.anchorterminal.com/tools/giggy-stt.min.md
- MiniMax Speech-to-Text: D 48.4, rank #1114 of 1486 · https://www.anchorterminal.com/tools/minimax-stt.min.md
- Giggy Speech to Text, good for Agents and voice pipelines that need plain transcripts of recorded or live speech at a few cents an hour, or free for clips under 25 minutes, and can convert audio to 16 kHz mono WAV first. Ahead on Security & auth, 57 against 33; Payments & pricing, 30 against 20; Maintenance & community, 69 against 6. Also A hosted endpoint, with nothing to install.
- MiniMax Speech-to-Text, good for Cheap file transcription with diarisation and subtitles, strongest on Chinese and code-switched audio by the vendor's account. Ahead on Schema & documentation, 82 against 68; Transparency & trust, 63 against 30.

| Category | Giggy Speech to Text | MiniMax Speech-to-Text |
| --- | --- | --- |
| Reliability (16%) | 50 | 47 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 68 | 82 |
| Agent ergonomics (13%) | 68 | 70 |
| Security & auth (14%) | 57 | 33 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 69 | 6 |
| Transparency & trust (7%) | 30 | 63 |

| Fact (where they differ) | Giggy Speech to Text | MiniMax Speech-to-Text |
| --- | --- | --- |
| Vendor | Giggy | MiniMax |
| Hosted endpoint | `https://api.giggy.ai/v1` | no (local only) |
| Transports | HTTP, SSE (legacy), websocket, Streamable HTTP | HTTP |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary hosted service. The terms page draws its text by script and was not read. The Python and Node SDKs, the Pipecat adapter and the MCP repository are ISC (Copyright 2026 Giggy), the n8n node MIT | none |
| Tools exposed | none | 0 |
| MCP registry | `io.github.GRQDigitalCapital/giggy-mcp` | not listed |
| Last release | 2026-11-01 | none |
| Terms last updated | not read yet | couldn't be read |
| Privacy policy last updated | not read yet | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |

Why the edge:
- Maintenance & community, Giggy Speech to Text +63: 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.); MiniMax Speech-to-Text 6 (Read as a model. No dated release or change of `asr-1.0` was found on the model or API release notes or the status page (0). No dated ASR entries in the last 90 days (0). Support by email and Discord, not tested (6 of 15). No official SDK, and the MCP servers have no transcription tool (0 of 15). No package to judge (0 of 10). Total 6.)
- Transparency & trust, MiniMax Speech-to-Text +33: 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.); MiniMax Speech-to-Text 63 (Closed API with clear terms under Singapore law naming Nanonoble Pte. Ltd., as on the other MiniMax listings (15 of 30). The terms and privacy policy agree that inputs may be used to improve services and that data sits in a United States data centre, with no retention period for audio (8 of 30). No deprecation notice or policy touches the ASR API (10 of 20, for the dated notices elsewhere on the API release notes). Data location stated as the United States and an EU representative named, with third parties only by category (10 of 20). Total 43.)
- Security & auth, Giggy Speech to Text +24: 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.); MiniMax Speech-to-Text 33 (Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain API keys from the console with no scopes found, and the docs say publicly leaked keys may be disabled, as on minimax-voice-cloning (20 of 30). The terms (effective 30 March 2026), as read for minimax-voice-cloning on 4 November, let MiniMax use input and generated content to operate, maintain, develop and improve its services, with no opt-out found, and the privacy policy rules out only training to profile or target consumers (5 of 20). No retention period for uploaded audio or transcripts was found (3 of 15). Each response carries a trace ID, with no audit log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found, as on the other MiniMax listings (0 of 20). Total 33.)
- Schema & documentation, MiniMax Speech-to-Text +14: 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.); MiniMax Speech-to-Text 82 (OpenAPI 3.1 for `/v1/speech_to_text`, with eight documented responses (25). llms.txt and a Markdown copy of every page (10). The guide says when to stream, when to use `verbose_json`, and that subtitles and diarisation can't be combined with streaming (15 of 20). Typed multipart fields with an enum for `response_format`, and file limits stated in prose (12 of 15). Python examples and an error table giving HTTP status, `error.type` and trigger for 400, 401, 402, 413, 422, 429 and 500 (15). Versioned `/v1` path, but neither release notes page mentions the ASR API, and the API notes stop at 28 October 2025 (5 of 15). Total 82.)
- Payments & pricing, Giggy Speech to Text +10: 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.); MiniMax Speech-to-Text 20 (No x402, MPP or L402 (0). $0.38 an hour published without a login (20). Speech to text is for paid accounts only (0). A person signs up in a browser and funds a balance (0). Total 20.)

| Task | Giggy Speech to Text | MiniMax Speech-to-Text |
| --- | --- | --- |
| Transcribe a one-hour meeting | $0.04 to $0.09 | $0.38 |