{ "data": { "a": { "slug": "amazon-transcribe", "name": "Amazon Transcribe", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/transcribe/", "kind": "model", "category": "speech-to-text", "summary": "Amazon Transcribe is AWS's speech-to-text API, with batch jobs that read audio from Amazon S3 and real-time streaming over HTTP/2 or WebSocket, signed with IAM credentials.", "url": "https://www.anchorterminal.com/tools/amazon-transcribe", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-transcribe.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-transcribe.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-transcribe.json", "dns": "amazon-transcribe.grade.anchorterminal.com", "repo": "https://github.com/awslabs/aws-sdk-python", "license": "Apache-2.0 (SDKs)", "transports": [ "http" ], "remoteUrl": "https://transcribe.us-east-1.amazonaws.com", "packages": [ { "registry": "pypi", "name": "boto3" }, { "registry": "pypi", "name": "aws-sdk-transcribe-streaming" }, { "registry": "npm", "name": "@aws-sdk/client-transcribe" }, { "registry": "npm", "name": "@aws-sdk/client-transcribe-streaming" } ], "auth": "api-key", "authNotes": "AWS Signature Version 4 with IAM access keys or a role. Batch goes to `transcribe.\u003cregion\u003e.amazonaws.com`, streaming to `transcribestreaming.\u003cregion\u003e.amazonaws.com` (WebSocket needs a presigned URL).", "pricing": "usage", "pricingNotes": "US East is $0.006 a minute batch and $0.01 a minute streaming, billed per second with no minimum and up to two channels included. Diarisation, custom vocabularies and language ID are included. PII redaction adds $0.0024 a minute and custom language models $0.006. Accounts opened before 2025-07-15 get 60 free minutes a month for 12 months. Newer accounts get up to $200 in Free Tier credits, and AWS says most new customers can sign up without a payment method (https://aws.amazon.com/transcribe/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No machine payment. Billing runs through a cloud account with a card or invoice.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 185, "npmWeekly": 505959, "pypiWeekly": 200552, "asOf": "2026-09-30" }, "docsUrl": "https://docs.aws.amazon.com/transcribe/latest/dg/what-is.html", "llmsTxt": "https://docs.aws.amazon.com/transcribe/latest/dg/llms.txt", "capabilities": [ "speech.stt", "speech.streaming", "speech.batch", "speech.diarisation", "speech.languages" ], "tags": [ "hosted", "closed-source", "python", "typescript", "enterprise", "streaming", "batch", "async-jobs", "llms-txt", "free-tier", "no-card" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 73.6, "grade": "BB", "agentReady": true, "rank": 92, "ranked": true, "rankOf": 1349, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 60, "payments": 30, "reliability": 75, "schema": 90, "security": 83, "transparency": 85 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Batch transcription costs $0.006 a minute and streaming $0.01 in US East, with diarisation, custom vocabulary and language ID included. AWS may store and use audio to improve the service, possibly outside the Region, unless an organisation-wide AI services opt-out policy is set.", "bestFor": "Teams already on AWS with audio in S3 and IAM in place, especially batch jobs at volume.", "strengths": [ "$0.006 a minute batch and $0.01 streaming in US East, with diarisation, custom vocabulary and language ID included", "A reused `TranscriptionJobName` fails with `ConflictException`, so a retried submission can't create a second job", "IAM policies can limit a credential to single actions and resources, and custom models can use a customer-managed KMS key", "Covered by the Amazon Machine Learning Language SLA, with credits from 10 per cent below 99.9 per cent monthly uptime", "Two batch API model updates in the 90 days to 1 November (3 and 18 September 2026), and JavaScript SDK clients released 30 October" ], "weaknesses": [ "AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set", "Listed in the open me-south-1 (Bahrain) disruption, where AWS said on 15 September 2026 that Region-only data can't be restored", "Batch input must sit in S3, and the WebSocket stream needs a presigned SigV4 URL", "Batch throttling returns `LimitExceededException` as a 400 with no Retry-After", "The Python streaming SDK the listing named is deprecated, and its replacement is pre-alpha and needs Python 3.12" ], "agentNotes": [ "Give every job a unique `TranscriptionJobName`. A retry with the same name fails with `ConflictException` rather than starting a second job", "Poll `GetTranscriptionJob` or listen on EventBridge, and set `OutputBucketName`, because job records are deleted after 90 days", "Back off on `LimitExceededException`. It arrives as a 400, not a 429", "Set the organisation's AI services opt-out policy before sending customer audio", "For Python streaming install `aws-sdk-transcribe-streaming` on Python 3.12 or later, not the deprecated `amazon-transcribe` package" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 73.6 } ], "editorialScores": { "ergonomics": 80, "maintenance": 60, "payments": 30, "reliability": 75, "schema": 90, "security": 83, "transparency": 75 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install boto3 aws-sdk-transcribe-streaming # or: npm i @aws-sdk/client-transcribe", "http": "curl -X POST \"https://transcribe.us-east-1.amazonaws.com/\" \\\n --aws-sigv4 \"aws:amz:us-east-1:transcribe\" --user \"$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY\" \\\n -H \"X-Amz-Target: Transcribe.StartTranscriptionJob\" -H \"content-type: application/x-amz-json-1.1\" \\\n -d '{\"TranscriptionJobName\":\"call-001\",\"LanguageCode\":\"en-US\",\"Media\":{\"MediaFileUri\":\"s3://my-bucket/call.wav\"}}'" }, "letme": { "capability": "https://letme.dev/speech.stt", "tool": "https://letme.dev/amazon-transcribe" }, "sameCompany": [ "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-polly", "agentcore-memory", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "voice", "unitPrices": [ { "item": "Batch", "unit": "audio-minute", "usd": 0.006, "note": "US East, per second" }, { "item": "Streaming", "unit": "audio-minute", "usd": 0.01, "note": "US East, per second" }, { "item": "PII redaction add-on", "unit": "audio-minute", "usd": 0.0024, "note": "first 250,000 minutes" }, { "item": "Custom language model add-on", "unit": "audio-minute", "usd": 0.006, "note": "first 250,000 minutes" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The endpoints are on amazonaws.com (registered 2005-08-18) and api.aws, both AWS domains. The security.txt on aws.amazon.com expired on 2026-09-24 and was renewed by 17 October 2026, with Expires 2027-10-16 (re-read on 1 November). The Service Terms show Last Updated 30 October 2026.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/transcribe/latest/dg/doc-history.html", "securityTxt": "valid", "checked": "2026-11-01", "score": 94 }, "requirements": { "card": "paid-only", "freeTier": true, "minutes": 15, "credential": "cloud-iam", "hosting": [ "US", "CA", "EU", "UK", "APAC" ], "euResidency": "yes", "trainsOnData": "opt-out", "zeroRetention": "unknown", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "CSA STAR", "HIPAA (BAA available)", "FedRAMP", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-transcribe.json", "live": { "slug": "amazon-transcribe", "probe": { "target": "https://transcribe.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-11-04T21:39:12.849642901Z", "lastOk": true, "lastStatus": 404, "lastMs": 259, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 291, "p95ms24h": 385, "samples24h": 247, "samples30d": 8090, "days": [ { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 223, "ok": 223 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-transcribe", "version": "3.1161.0", "seenAt": "2026-11-04T19:57:42.656284836Z" }, { "registry": "npm", "name": "@aws-sdk/client-transcribe-streaming", "version": "3.1161.0", "seenAt": "2026-11-04T19:57:43.43987705Z" }, { "registry": "pypi", "name": "amazon-transcribe", "version": "0.6.4", "released": "2025-05-05", "seenAt": "2026-10-17T01:33:24.189537414Z" }, { "registry": "pypi", "name": "aws-sdk-transcribe-streaming", "version": "0.12.0", "released": "2026-10-08", "seenAt": "2026-11-04T19:57:40.784915342Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.123", "released": "2026-10-30", "seenAt": "2026-11-04T19:57:40.491283739Z" } ], "githubStars": 177, "npmWeekly": 799976, "pypiWeekly": 619007329, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:54:48.445218801Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/transcribe/latest/dg/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:22:06.642902927Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-11-01T14:09:08.477101866Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/transcribe/latest/dg/doc-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-11-04T08:20:23.60424062Z", "changedAt": "2026-10-06T16:07:55.368671496Z", "fingerprint": "ecdbccfa98c4" }, { "url": "https://aws.amazon.com/transcribe/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-04T08:15:58.051288755Z", "changedAt": "2026-10-16T22:18:05.108019819Z", "fingerprint": "3c49eb9e86f5" } ], "github": { "repo": "awslabs/aws-sdk-python", "checkedAt": "2026-11-02T08:33:28.439316307Z", "stars": 177, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T18:57:36Z", "openIssues": 9, "openPRs": 3, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 16, "unanswered": 9, "medianDays": 39 } }, "updatedAt": "2026-11-04T21:39:12.849642901Z" } }, "answer": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Giggy Speech to Text's 54.5 (C), and leads in 5 of 7 scored categories. Giggy Speech to Text leads on maintenance \u0026 community.", "b": { "slug": "giggy-stt", "name": "Giggy Speech to Text", "vendor": "Giggy", "vendorUrl": "https://giggy.ai", "kind": "model", "category": "speech-to-text", "summary": "Giggy's hosted speech-to-text API transcribes 16 kHz mono WAV recordings in free Batch, prepaid Fast and Streaming modes, and live audio over a WebSocket, with Python and Node SDKs and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/giggy-stt", "markdownUrl": "https://www.anchorterminal.com/tools/giggy-stt.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/giggy-stt.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/giggy-stt.json", "dns": "giggy-stt.grade.anchorterminal.com", "repo": "https://github.com/giggy-ai/giggy-js", "license": "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", "transports": [ "http", "sse", "websocket", "streamable-http" ], "remoteUrl": "https://api.giggy.ai/v1", "packages": [ { "registry": "pypi", "name": "giggy" }, { "registry": "npm", "name": "@giggy-ai/sdk" }, { "registry": "pypi", "name": "pipecat-giggy" } ], "auth": "api-key", "authNotes": "Self-serve API key prefixed `giggy_sk_`, shown once when created or rotated, rejected immediately after revocation, up to ten active per Personal space or Workspace and tied for good to the space that created it. REST sends it in `xi-api-key`; the WebSocket upgrade and the MCP server take `Authorization: Bearer`. No key scopes or expiry were found, and no query-string option is documented (https://giggy.ai/docs/api-reference).", "pricing": "freemium", "pricingNotes": "Batch transcription is free, queued, for recordings of 0.5 seconds to 25 minutes. Fast costs 4,000 credits ($0.04) and Streaming 8,000 credits ($0.08) per input audio hour on Pro, Studio or Scale credits, rounded up to one credit per request. Credits come in one-time packs from $3 and expire a year after purchase. Personal accounts get free credits topped up to 10,000 a month. Whether a card is needed was not stated on any page read (https://giggy.ai/pricing).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the speech API docs, the API reference, llms.txt or llms-full.txt read on 2026-11-04. Credits are bought in prepaid packs; the payment method is not named on any page read.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-04" }, "docsUrl": "https://giggy.ai/docs/speech-api", "llmsTxt": "https://giggy.ai/llms.txt", "openapi": "https://api.giggy.ai/v1/openapi.json", "registryName": "io.github.GRQDigitalCapital/giggy-mcp", "capabilities": [ "speech.stt", "speech.batch", "speech.streaming", "speech.languages" ], "tags": [ "official", "hosted", "model", "closed-source", "streaming", "batch", "async-jobs", "free-tier", "python", "typescript", "openapi", "llms-txt", "mcp", "websocket", "new" ], "lastRelease": "2026-11-01", "graded": true, "anchor": { "graded": true, "score": 54.5, "grade": "C", "agentReady": false, "rank": 806, "ranked": true, "rankOf": 1349, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 69, "payments": 30, "reliability": 50, "schema": 68, "security": 57, "transparency": 30 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": 0, "verdict": "Fast transcription costs $0.04 an input audio hour and Batch is free up to 25 minutes, with published rate limits, Retry-After and a rule to check a generation before resubmitting. Input must be 16 kHz mono WAV, there are no timestamps or speaker labels, the status page covers text-to-speech only, and no company is named on pages we could read.", "bestFor": "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.", "strengths": [ "Fast is $0.04 and Streaming $0.08 per input audio hour on Pro credits, and Batch is free for recordings of 0.5 seconds to 25 minutes", "Per-credential rate limits are published with numbers, 429 carries `Retry-After`, and `RateLimit-*` headers report what is left", "The docs say to read a generation by UUID after a timeout or 504 instead of uploading again, and the SDKs never retry paid requests", "llms.txt, llms-full.txt and SDK READMEs state what the API does not do, including no diarisation, timestamps or OpenAI-compatible STT", "Official Python and Node SDKs at 0.2.1, a Pipecat adapter with live STT and a remote MCP server, all released within the last four weeks" ], "weaknesses": [ "Recorded input must be PCM16 mono 16 kHz WAV, so MP3, M4A, stereo or other sample rates need converting before upload", "No word timestamps, speaker labels, confidence scores or redaction, per the speech API docs", "The status page has one component, Text to speech, and no incident history, so speech-to-text availability isn't shown", "REST transcription has no idempotency key, and `client_request_id` is documented as not making a retried upload safe", "The terms, privacy policy, support and contact pages draw by script, and no company, address or security contact was found on any page read" ], "agentNotes": [ "Pass `mode=batch` explicitly for free transcription. Raw REST and MCP default to paid Fast when `mode` is omitted.", "Convert audio to PCM16 mono 16 kHz WAV first and send it as the raw body with `Content-Type: audio/wav`.", "Keep the `generation_uuid` from the 202 and poll `GET /v1/generations/{uuid}`. Never re-upload after a timeout or 504 before reading that generation.", "Fetch the transcript from the signed `generation.result.url` after completion, without the API key. It can disappear after retention cleanup.", "On the live WebSocket, replace earlier text with each cumulative `transcription` event and publish final text only after `input_complete`." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.5 } ], "editorialScores": { "ergonomics": 68, "maintenance": 69, "payments": 30, "reliability": 50, "schema": 68, "security": 57, "transparency": 23 }, "provenanceScore": 36, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "python -m pip install giggy==0.2.1 # or: npm install @giggy-ai/sdk", "http": "curl -X POST \"https://api.giggy.ai/v1/audio/transcriptions?mode=batch\u0026language=en\" \\\n -H \"xi-api-key: $GIGGY_API_KEY\" -H \"Content-Type: audio/wav\" \\\n --data-binary @recording.wav", "config": { "mcpServers": { "giggy-speech": { "headers": { "Authorization": "Bearer ${GIGGY_API_KEY}" }, "type": "http", "url": "https://giggy.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/speech.stt", "tool": "https://letme.dev/giggy-stt" }, "area": "voice", "unitPrices": [ { "item": "Fast, Pro, Studio or Scale credits", "unit": "audio-minute", "usd": 0.000667, "note": "published as $0.04 per input audio hour, rounded up to one credit per request" }, { "item": "Streaming, Pro, Studio or Scale credits", "unit": "audio-minute", "usd": 0.001333, "note": "published as $0.08 per input audio hour" }, { "item": "Fast, Starter pack", "unit": "audio-minute", "usd": 0.000765, "note": "$3 for 261,300 credits, $0.0459 an hour" }, { "item": "Streaming, Starter pack", "unit": "audio-minute", "usd": 0.00153, "note": "$0.0918 an hour" }, { "item": "Batch", "unit": "audio-minute", "usd": 0, "note": "free, queued, 0.5 seconds to 25 minutes a recording" } ], "provenance": { "legalEntity": "", "domain": "giggy.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://giggy.ai/terms", "privacy": "https://giggy.ai/privacy", "statusPage": "https://giggy.ai/status", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "unchecked: the legal entity. /terms, /privacy, /acceptable-use, /contact, /docs/support and /docs/privacy-rights returned only their titles and metadata, because their text is drawn by script, and /terms.md answered a client error. The about, pricing, grants and docs pages that did render name only Giggy, with 'Made in California' on the about page. The repositories' licences say 'Copyright 2026 Giggy'.", "The status page tracks one component, Text to speech, with 14-day availability and completion figures refreshed every 30 minutes and no incident history. It has no speech-to-text component.", "No service changelog was found. The SDK and Pipecat repositories carry CHANGELOG.md files, dated in the Python SDK and the Pipecat adapter.", "https://giggy.ai/.well-known/security.txt answered a client error. None of the six public repositories has a SECURITY.md.", "robots.txt on giggy.ai allows / and disallows /api/, /ops/, /app/ and /blog/*.md for `*` and for the named AI agents, with no Content-Signal line. api.giggy.ai's robots.txt could not be read (the fetch needed an approval that wasn't given), so nothing on that host was fetched, the OpenAPI file included.", "unchecked: RDAP for giggy.ai (refused for want of an approval on 4 November 2026)." ], "score": 36 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/giggy-stt.json", "live": { "slug": "giggy-stt", "probe": { "target": "https://api.giggy.ai/v1", "method": "get", "lastAt": "2026-11-04T21:39:24.734230033Z", "lastOk": true, "lastStatus": 404, "lastMs": 398, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 286, "p95ms24h": 654, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://giggy.ai/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:25:54.463598549Z" }, "versions": [ { "registry": "github", "name": "giggy-ai/giggy-js", "version": "v0.1.0", "released": "2026-10-07", "seenAt": "2026-11-04T20:18:19.850001725Z" }, { "registry": "mcp-registry", "name": "io.github.GRQDigitalCapital/giggy-mcp", "version": "1.0.2", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "@giggy-ai/sdk", "version": "0.2.1", "seenAt": "2026-11-04T20:18:17.973963585Z" }, { "registry": "pypi", "name": "giggy", "version": "0.2.1", "released": "2026-11-01", "seenAt": "2026-11-04T20:18:17.733675794Z" }, { "registry": "pypi", "name": "pipecat-giggy", "version": "0.3.3", "released": "2026-11-01", "seenAt": "2026-11-04T20:18:18.946085778Z" } ], "githubStars": 0, "npmWeekly": 209, "pypiWeekly": 32, "securityTxt": { "url": "https://giggy.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:29.107165985Z" }, "updatedAt": "2026-11-04T21:39:24.734230033Z" } }, "edges": [ { "by": 55, "category": "transparency", "leads": "amazon-transcribe", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under the AWS Service Terms, last updated 30 October 2026 (15). The service terms, privacy notice (last updated 18 May 2026, re-read on 1 November) and job retention agree, and the data processing addendum and a public sub-processor list (last updated 30 October 2026) exist, but the default permission to use content for improvement sits in section 50.3 of the service terms rather than the Transcribe guide. The DPA's text is per the 1 October check (25). The AWS Customer Agreement commits to advance notice before material functionality of a GA service is discontinued, but we found no dated Transcribe deprecation notices. The Python streaming SDK carries a deprecation notice in its README, which isn't the service (15). Sub-processors and regions disclosed, with region choice per request. Section 50.3(c) discloses that content kept for improvement may be stored outside the Region unless the organisation opts out (20). 15 + 25 + 15 + 20 = 75.", "b": "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." }, "scores": { "a": 85, "b": 30 } }, { "by": 26, "category": "security", "leads": "amazon-transcribe", "name": "Security \u0026 auth", "reasons": { "a": "Model reading of the checklist, with training and retention in place of least-privilege and injection lines. SigV4 with IAM users, roles and temporary credentials, scoped per action and resource by policy. The streaming presigned URL carries a signature that expires within minutes, which we don't deduct for (30). Section 50.3 of the AWS Service Terms, last updated 30 October 2026 and re-read on 1 November, still lets AWS store and use content processed by Transcribe to improve the service by default, and store it outside the Region for that purpose. Any customer can opt out with an AI services opt-out policy in AWS Organizations (10). Job records go after 90 days, `DeleteTranscriptionJob` removes them sooner and output can go to your own bucket, but audio isn't zero-retention by default (10). Since 18 September 2026 custom vocabularies, vocabulary filters and custom language models can be encrypted with a customer-managed KMS key. CloudTrail logs API calls per caller (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins (none of the 39 items in the feed on 1 November, the newest dated 31 October, names Transcribe), and Amazon Transcribe in SOC 1, 2 and 3 scope on AWS's list updated 11 August 2026, re-read on 1 November. The security.txt on aws.amazon.com, re-read on 1 November, expires on 16 October 2027 and points to the VDP. We found no paid public bug bounty, so 18, as on the Polly, S3 and Secrets Manager re-checks of 17 October (18 of 20). 30 + 10 + 10 + 15 + 18 = 83.", "b": "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." }, "scores": { "a": 83, "b": 57 } }, { "by": 25, "category": "reliability", "leads": "amazon-transcribe", "name": "Reliability", "reasons": { "a": "AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Transcribe feeds for us-east-1, us-west-2 and eu-west-1 carried no events on 1 November 2026 (last built 31 October). The dashboard history file, re-read on 1 November, still lists Amazon Transcribe in the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, at disruption status, with its last update on 15 September 2026, inside the 90-day window from 3 August, saying AWS can't restore resources and data hosted only in that Region. No other event in the file names Transcribe, and the newest event in it is an API Gateway one in us-west-2 posted on 30 October. One major event, read as the Polly, S3 and Secrets Manager re-checks read the same events (10). Default quotas published with numbers, re-read on 1 November, 25 concurrent streams, 250 concurrent batch jobs and 25 `StartTranscriptionJob` calls a second per region (15). Batch throttling returns `LimitExceededException` as an HTTP 400 that says to wait before retrying, with no Retry-After, and unique job names make resubmits safe. Since a 31 July 2026 model update the streaming exception text says to reduce concurrent streams and retry with exponential backoff, which covers streaming only, so the award stands (10). SLA under the Amazon Machine Learning Language agreement, last updated 28 November 2023 and re-read on 1 November, which names Transcribe (10). GA (10). 20 + 10 + 15 + 10 + 10 + 10 = 75.", "b": "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." }, "scores": { "a": 75, "b": 50 } }, { "by": 22, "category": "schema", "leads": "amazon-transcribe", "name": "Schema \u0026 documentation", "reasons": { "a": "The service model is public in aws/api-models-aws and the AWS SDKs, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, 260 lines on 1 November (10). Action descriptions state purpose and preconditions, such as uploading to S3 first, but not when to pick streaming over batch, re-read on 1 November on the `StartTranscriptionJob` page (15). Inputs are typed with enums (`LanguageCode`, `MediaFormat`), patterns and ranges (`MediaSampleRateHertz` 8,000 to 48,000) and marked required (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples section (the `StartTranscriptionJob` page, re-read on 1 November, gives only inline examples of parameter values), so examples live in the developer guide (10). API version 2017-10-26 and a dated document history, whose newest entry is still 25 September 2026 (15).", "b": "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." }, "scores": { "a": 90, "b": 68 } }, { "by": 12, "category": "ergonomics", "leads": "amazon-transcribe", "name": "Agent ergonomics", "reasons": { "a": "API reading of the checklist. The transcript is one JSON file with every item and its timings, with SRT and VTT subtitles as the compact alternative and no field selection, per the 1 October check (15). `ListTranscriptionJobs` filters by `Status` and `JobNameContains` and pages with `MaxResults` and `NextToken`, re-read on 1 November (20). Typed exceptions per action, each with a recovery hint (20). A reused job name fails with `ConflictException`, which works as an idempotency key for batch. Streaming has no resume (15). Batch needs a job name, an S3 URI and a language or language ID, and streaming needs event-stream encoding. SDKs in every major language (10).", "b": "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." }, "scores": { "a": 80, "b": 68 } }, { "by": 9, "category": "maintenance", "leads": "giggy-stt", "name": "Maintenance \u0026 community", "reasons": { "a": "Read by the listing's own service models (transcribe and transcribe-streaming), as this run's amazon-s3 re-check read models/s3. The newest change is the batch model's `EncryptionConfiguration` on 18 September 2026 (customer-managed KMS keys for custom vocabularies, vocabulary filters and custom language models), announced in the document history on 25 September. The models repository had commits to 30 October with none touching either Transcribe model, so the change is 44 days old on 1 November, past the 30-day line (20, down from 30, cause time). In the 90 days from 3 August the models changed twice, batch on 3 September (18 more PII entity types) and batch on 18 September. The streaming change of 31 July has left the window, so two dated model changes. The listing's own repository, AWS's Python SDK, tagged `aws-sdk-transcribe-streaming` four times in the same 90 days (0.9.0 on 13 August, 0.10.0 on 20 August, 0.11.0 on 24 August and 0.12.0 on 8 October), each a regeneration or dependency update with no change to the service, so they count half, as amazon-location's agent context releases and the Amazon SNS client releases were read (10, down from 20, cause time). Public document history, AWS re:Post and paid support plans (10). Official SDKs are current, `@aws-sdk/client-transcribe` and `-streaming` at 3.1161.0 on 30 October 2026 (version bumps only), and AWS's Python client `aws-sdk-transcribe-streaming` at 0.12.0 on 8 October (15). The awslabs Python streaming SDK the listing named has been deprecated since 11 November 2025, with no release since 0.6.4 in May 2025, and its replacement is marked pre-alpha and needs Python 3.12 or later (5 of 10). 20 + 10 + 10 + 15 + 5 = 60.", "b": "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." }, "scores": { "a": 60, "b": 69 } } ], "facts": [ { "a": "Model API", "b": "Model API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Giggy", "name": "Vendor" }, { "a": "https://transcribe.us-east-1.amazonaws.com", "b": "https://api.giggy.ai/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, SSE (legacy), websocket, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 (SDKs)", "b": "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", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.GRQDigitalCapital/giggy-mcp", "name": "MCP registry" }, { "a": "2026-09-25", "b": "2026-11-01", "name": "Last release" }, { "a": "2026-10-01", "b": "not read yet", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not read yet", "name": "Customer content may train models" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "185 stars, 506k npm/wk, 201k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Giggy Speech to Text's 54.5 (C), and leads in 5 of 7 scored categories. Giggy Speech to Text leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon Transcribe or Giggy Speech to Text?" }, { "answer": "Both need an API key.", "question": "Do Amazon Transcribe and Giggy Speech to Text need an API key?" }, { "answer": "Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Giggy Speech to Text at https://api.giggy.ai/v1.", "question": "Can an agent call Amazon Transcribe and Giggy Speech to Text without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 50", "Schema \u0026 documentation, 90 against 68", "Agent ergonomics, 80 against 68", "Security \u0026 auth, 83 against 57", "Transparency \u0026 trust, 85 against 30" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "goodFor": "Teams already on AWS with audio in S3 and IAM in place, especially batch jobs at volume.", "slug": "amazon-transcribe", "watchFor": "AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set" }, { "aheadOn": [ "Maintenance \u0026 community, 69 against 60" ], "also": null, "goodFor": "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.", "slug": "giggy-stt", "watchFor": "Recorded input must be PCM16 mono 16 kHz WAV, so MP3, M4A, stereo or other sample rates need converting before upload" } ], "history": { "amazon-transcribe": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": -1.7, "from": 75.3, "fromGrade": "BB", "to": 73.6, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 75.3, "fromGrade": "BB", "to": 75.3, "toGrade": "BB" }, { "causes": [ "security", "evidence", "correction" ], "date": "2026-10-17", "delta": 1.9, "from": 73.4, "fromGrade": "BB", "to": 75.3, "toGrade": "BB" } ], "giggy-stt": null }, "job": { "capability": "speech.stt", "name": "Speech-to-text" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-assemblyai-stt.json", "title": "Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-assemblyai-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-azure-speech-to-text.json", "title": "Amazon Transcribe vs Azure AI Speech speech-to-text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-azure-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-cartesia-ink-stt.json", "title": "Amazon Transcribe vs Cartesia Ink", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-cartesia-ink-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-deepgram-stt.json", "title": "Amazon Transcribe vs Deepgram Speech-to-Text (Nova-3, Flux)", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-deepgram-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-elevenlabs-scribe.json", "title": "Amazon Transcribe vs ElevenLabs Scribe Speech to Text API", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-elevenlabs-scribe" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-gladia-stt.json", "title": "Amazon Transcribe vs Gladia Speech-to-Text API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-gladia-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-google-speech-to-text.json", "title": "Amazon Transcribe vs Google Cloud Speech-to-Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-google-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-groq-speech-to-text.json", "title": "Amazon Transcribe vs Groq Speech-to-Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-groq-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-mistral-voxtral-transcribe.json", "title": "Amazon Transcribe vs Mistral Voxtral Transcribe", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-mistral-voxtral-transcribe" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-openai-speech-to-text.json", "title": "Amazon Transcribe vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-openai-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-rev-ai-stt.json", "title": "Amazon Transcribe vs Rev AI Speech-to-Text API", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-rev-ai-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-soniox-stt.json", "title": "Amazon Transcribe vs Soniox Speech-to-Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-soniox-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-speechmatics-stt.json", "title": "Amazon Transcribe vs Speechmatics Speech-to-Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-speechmatics-stt" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-stt-vs-giggy-stt.json", "title": "AssemblyAI Speech-to-Text (Universal) vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/assemblyai-stt-vs-giggy-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-giggy-stt.json", "title": "Azure AI Speech speech-to-text vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-giggy-stt" }, { "json": "https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-giggy-stt.json", "title": "Cartesia Ink vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-giggy-stt" }, { "json": "https://www.anchorterminal.com/compare/deepgram-stt-vs-giggy-stt.json", "title": "Deepgram Speech-to-Text (Nova-3, Flux) vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/deepgram-stt-vs-giggy-stt" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-giggy-stt.json", "title": "ElevenLabs Scribe Speech to Text API vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-giggy-stt" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-gladia-stt.json", "title": "Giggy Speech to Text vs Gladia Speech-to-Text API + MCP", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-gladia-stt" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-google-speech-to-text.json", "title": "Giggy Speech to Text vs Google Cloud Speech-to-Text", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-google-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-groq-speech-to-text.json", "title": "Giggy Speech to Text vs Groq Speech-to-Text", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-groq-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-mistral-voxtral-transcribe.json", "title": "Giggy Speech to Text vs Mistral Voxtral Transcribe", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-mistral-voxtral-transcribe" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-openai-speech-to-text.json", "title": "Giggy Speech to Text vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-openai-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-rev-ai-stt.json", "title": "Giggy Speech to Text vs Rev AI Speech-to-Text API", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-rev-ai-stt" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-soniox-stt.json", "title": "Giggy Speech to Text vs Soniox Speech-to-Text", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-soniox-stt" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-speechmatics-stt.json", "title": "Giggy Speech to Text vs Speechmatics Speech-to-Text", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-speechmatics-stt" } ], "panel": null, "scores": [ { "amazon-transcribe": 75, "by": 25, "edge": "amazon-transcribe", "giggy-stt": 50, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-transcribe": 90, "by": 22, "edge": "amazon-transcribe", "giggy-stt": 68, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-transcribe": 80, "by": 12, "edge": "amazon-transcribe", "giggy-stt": 68, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "amazon-transcribe": 83, "by": 26, "edge": "amazon-transcribe", "giggy-stt": 57, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "amazon-transcribe": 30, "by": 0, "edge": "", "giggy-stt": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-transcribe": 60, "by": 9, "edge": "giggy-stt", "giggy-stt": 69, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-transcribe": 85, "by": 55, "edge": "amazon-transcribe", "giggy-stt": 30, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Giggy Speech to Text's 54.5 (C), and leads in 5 of 7 scored categories. Giggy Speech to Text leads on maintenance \u0026 community. Both do speech-to-text.", "tasks": [ { "a": "$0.36 to $0.60", "b": "$0.04 to $0.09", "cheaper": "giggy-stt", "task": "Transcribe a one-hour meeting", "what": "60 minutes of recorded audio" } ], "tutorials": [], "verdicts": { "amazon-transcribe": "Batch transcription costs $0.006 a minute and streaming $0.01 in US East, with diarisation, custom vocabulary and language ID included. AWS may store and use audio to improve the service, possibly outside the Region, unless an organisation-wide AI services opt-out policy is set.", "giggy-stt": "Fast transcription costs $0.04 an input audio hour and Batch is free up to 25 minutes, with published rate limits, Retry-After and a rule to check a generation before resubmitting. Input must be 16 kHz mono WAV, there are no timestamps or speaker labels, the status page covers text-to-speech only, and no company is named on pages we could read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt", "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt.min.md" }, "markdown": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Giggy Speech to Text's 54.5 (C), and leads in 5 of 7 scored categories. Giggy Speech to Text leads on maintenance \u0026 community. Both do speech-to-text.\n\n- Amazon Transcribe: grade BB, 73.6/100, rank #92 of 1349. Markdown https://www.anchorterminal.com/tools/amazon-transcribe.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-transcribe.json\n- Giggy Speech to Text: grade C, 54.5/100, rank #806 of 1349. Markdown https://www.anchorterminal.com/tools/giggy-stt.md · JSON https://www.anchorterminal.com/api/v1/tools/giggy-stt.json\n- Best speech-to-text APIs for AI agents: https://www.anchorterminal.com/best/speech-to-text/index.md\n- All 253 stt comparisons: https://www.anchorterminal.com/compare/speech-to-text/index.md\n\n## Which one, for what\n\n### Amazon Transcribe (BB)\n\nGood for: Teams already on AWS with audio in S3 and IAM in place, especially batch jobs at volume.\n\nAhead on:\n- Reliability, 75 against 50\n- Schema \u0026 documentation, 90 against 68\n- Agent ergonomics, 80 against 68\n- Security \u0026 auth, 83 against 57\n- Transparency \u0026 trust, 85 against 30\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set\n\n### Giggy Speech to Text (C)\n\nGood 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.\n\nAhead on:\n- Maintenance \u0026 community, 69 against 60\n\nWatch for: Recorded input must be PCM16 mono 16 kHz WAV, so MP3, M4A, stereo or other sample rates need converting before upload\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Amazon Transcribe +55\n\n- Amazon Transcribe (85): Closed service under the AWS Service Terms, last updated 30 October 2026 (15). The service terms, privacy notice (last updated 18 May 2026, re-read on 1 November) and job retention agree, and the data processing addendum and a public sub-processor list (last updated 30 October 2026) exist, but the default permission to use content for improvement sits in section 50.3 of the service terms rather than the Transcribe guide. The DPA's text is per the 1 October check (25). The AWS Customer Agreement commits to advance notice before material functionality of a GA service is discontinued, but we found no dated Transcribe deprecation notices. The Python streaming SDK carries a deprecation notice in its README, which isn't the service (15). Sub-processors and regions disclosed, with region choice per request. Section 50.3(c) discloses that content kept for improvement may be stored outside the Region unless the organisation opts out (20). 15 + 25 + 15 + 20 = 75.\n- 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.\n\n### Security \u0026 auth: Amazon Transcribe +26\n\n- Amazon Transcribe (83): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. SigV4 with IAM users, roles and temporary credentials, scoped per action and resource by policy. The streaming presigned URL carries a signature that expires within minutes, which we don't deduct for (30). Section 50.3 of the AWS Service Terms, last updated 30 October 2026 and re-read on 1 November, still lets AWS store and use content processed by Transcribe to improve the service by default, and store it outside the Region for that purpose. Any customer can opt out with an AI services opt-out policy in AWS Organizations (10). Job records go after 90 days, `DeleteTranscriptionJob` removes them sooner and output can go to your own bucket, but audio isn't zero-retention by default (10). Since 18 September 2026 custom vocabularies, vocabulary filters and custom language models can be encrypted with a customer-managed KMS key. CloudTrail logs API calls per caller (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins (none of the 39 items in the feed on 1 November, the newest dated 31 October, names Transcribe), and Amazon Transcribe in SOC 1, 2 and 3 scope on AWS's list updated 11 August 2026, re-read on 1 November. The security.txt on aws.amazon.com, re-read on 1 November, expires on 16 October 2027 and points to the VDP. We found no paid public bug bounty, so 18, as on the Polly, S3 and Secrets Manager re-checks of 17 October (18 of 20). 30 + 10 + 10 + 15 + 18 = 83.\n- 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.\n\n### Reliability: Amazon Transcribe +25\n\n- Amazon Transcribe (75): AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Transcribe feeds for us-east-1, us-west-2 and eu-west-1 carried no events on 1 November 2026 (last built 31 October). The dashboard history file, re-read on 1 November, still lists Amazon Transcribe in the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, at disruption status, with its last update on 15 September 2026, inside the 90-day window from 3 August, saying AWS can't restore resources and data hosted only in that Region. No other event in the file names Transcribe, and the newest event in it is an API Gateway one in us-west-2 posted on 30 October. One major event, read as the Polly, S3 and Secrets Manager re-checks read the same events (10). Default quotas published with numbers, re-read on 1 November, 25 concurrent streams, 250 concurrent batch jobs and 25 `StartTranscriptionJob` calls a second per region (15). Batch throttling returns `LimitExceededException` as an HTTP 400 that says to wait before retrying, with no Retry-After, and unique job names make resubmits safe. Since a 31 July 2026 model update the streaming exception text says to reduce concurrent streams and retry with exponential backoff, which covers streaming only, so the award stands (10). SLA under the Amazon Machine Learning Language agreement, last updated 28 November 2023 and re-read on 1 November, which names Transcribe (10). GA (10). 20 + 10 + 15 + 10 + 10 + 10 = 75.\n- 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.\n\n### Schema \u0026 documentation: Amazon Transcribe +22\n\n- Amazon Transcribe (90): The service model is public in aws/api-models-aws and the AWS SDKs, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, 260 lines on 1 November (10). Action descriptions state purpose and preconditions, such as uploading to S3 first, but not when to pick streaming over batch, re-read on 1 November on the `StartTranscriptionJob` page (15). Inputs are typed with enums (`LanguageCode`, `MediaFormat`), patterns and ranges (`MediaSampleRateHertz` 8,000 to 48,000) and marked required (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples section (the `StartTranscriptionJob` page, re-read on 1 November, gives only inline examples of parameter values), so examples live in the developer guide (10). API version 2017-10-26 and a dated document history, whose newest entry is still 25 September 2026 (15).\n- 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.\n\n### Agent ergonomics: Amazon Transcribe +12\n\n- Amazon Transcribe (80): API reading of the checklist. The transcript is one JSON file with every item and its timings, with SRT and VTT subtitles as the compact alternative and no field selection, per the 1 October check (15). `ListTranscriptionJobs` filters by `Status` and `JobNameContains` and pages with `MaxResults` and `NextToken`, re-read on 1 November (20). Typed exceptions per action, each with a recovery hint (20). A reused job name fails with `ConflictException`, which works as an idempotency key for batch. Streaming has no resume (15). Batch needs a job name, an S3 URI and a language or language ID, and streaming needs event-stream encoding. SDKs in every major language (10).\n- 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.\n\n### Maintenance \u0026 community: Giggy Speech to Text +9\n\n- Amazon Transcribe (60): Read by the listing's own service models (transcribe and transcribe-streaming), as this run's amazon-s3 re-check read models/s3. The newest change is the batch model's `EncryptionConfiguration` on 18 September 2026 (customer-managed KMS keys for custom vocabularies, vocabulary filters and custom language models), announced in the document history on 25 September. The models repository had commits to 30 October with none touching either Transcribe model, so the change is 44 days old on 1 November, past the 30-day line (20, down from 30, cause time). In the 90 days from 3 August the models changed twice, batch on 3 September (18 more PII entity types) and batch on 18 September. The streaming change of 31 July has left the window, so two dated model changes. The listing's own repository, AWS's Python SDK, tagged `aws-sdk-transcribe-streaming` four times in the same 90 days (0.9.0 on 13 August, 0.10.0 on 20 August, 0.11.0 on 24 August and 0.12.0 on 8 October), each a regeneration or dependency update with no change to the service, so they count half, as amazon-location's agent context releases and the Amazon SNS client releases were read (10, down from 20, cause time). Public document history, AWS re:Post and paid support plans (10). Official SDKs are current, `@aws-sdk/client-transcribe` and `-streaming` at 3.1161.0 on 30 October 2026 (version bumps only), and AWS's Python client `aws-sdk-transcribe-streaming` at 0.12.0 on 8 October (15). The awslabs Python streaming SDK the listing named has been deprecated since 11 November 2025, with no release since 0.6.4 in May 2025, and its replacement is marked pre-alpha and needs Python 3.12 or later (5 of 10). 20 + 10 + 10 + 15 + 5 = 60.\n- 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.\n\n## Score by category\n\n| Category | Weight | Amazon Transcribe | Giggy Speech to Text | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 50 | Amazon Transcribe +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 68 | Amazon Transcribe +22 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 68 | Amazon Transcribe +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 83 | 57 | Amazon Transcribe +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 69 | Giggy Speech to Text +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 85 | 30 | Amazon Transcribe +55 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **73.6 · BB** | **54.5 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon Transcribe | Giggy Speech to Text |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | Amazon Web Services | Giggy |\n| Hosted endpoint | `https://transcribe.us-east-1.amazonaws.com` | `https://api.giggy.ai/v1` |\n| Transports | HTTP | HTTP, SSE (legacy), websocket, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 (SDKs) | 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.GRQDigitalCapital/giggy-mcp` |\n| Last release | 2026-09-25 | 2026-11-01 |\n| Terms last updated | 2026-10-01 | not read yet |\n| Privacy policy last updated | 2026-05-18 | not read yet |\n| Customer content may train models | yes, with an opt-out | not read yet |\n| Terms restrict automated access | yes | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | 185 stars, 506k npm/wk, 201k PyPI/wk | none |\n| Agent reviews | 4/5 (2) | none |\n\n## What the same task costs\n\n| Task | Amazon Transcribe | Giggy Speech to Text |\n| --- | --- | --- |\n| Transcribe a one-hour meeting | $0.36 to $0.60 | $0.04 to $0.09 |\n\n## How the scores have moved\n\n### Amazon Transcribe\n\n- -1.7 on 1 November 2026: time\n- no change on 27 October 2026: checklist\n- +1.9 on 17 October 2026: security, new evidence, correction\n\n### Giggy Speech to Text\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Amazon Transcribe.** Batch transcription costs $0.006 a minute and streaming $0.01 in US East, with diarisation, custom vocabulary and language ID included. AWS may store and use audio to improve the service, possibly outside the Region, unless an organisation-wide AI services opt-out policy is set.\n\n**Giggy Speech to Text.** Fast transcription costs $0.04 an input audio hour and Batch is free up to 25 minutes, with published rate limits, Retry-After and a rule to check a generation before resubmitting. Input must be 16 kHz mono WAV, there are no timestamps or speaker labels, the status page covers text-to-speech only, and no company is named on pages we could read.\n\n## Before you call either\n\n### Amazon Transcribe\n\n1. Give every job a unique `TranscriptionJobName`. A retry with the same name fails with `ConflictException` rather than starting a second job\n2. Poll `GetTranscriptionJob` or listen on EventBridge, and set `OutputBucketName`, because job records are deleted after 90 days\n3. Back off on `LimitExceededException`. It arrives as a 400, not a 429\n4. Set the organisation's AI services opt-out policy before sending customer audio\n5. For Python streaming install `aws-sdk-transcribe-streaming` on Python 3.12 or later, not the deprecated `amazon-transcribe` package\n\n### Giggy Speech to Text\n\n1. Pass `mode=batch` explicitly for free transcription. Raw REST and MCP default to paid Fast when `mode` is omitted.\n2. Convert audio to PCM16 mono 16 kHz WAV first and send it as the raw body with `Content-Type: audio/wav`.\n3. Keep the `generation_uuid` from the 202 and poll `GET /v1/generations/{uuid}`. Never re-upload after a timeout or 504 before reading that generation.\n4. Fetch the transcript from the signed `generation.result.url` after completion, without the API key. It can disappear after retention cleanup.\n5. On the live WebSocket, replace earlier text with each cumulative `transcription` event and publish final text only after `input_complete`.\n\n## Questions\n\n### Which is better for AI agents, Amazon Transcribe or Giggy Speech to Text?\n\nAmazon Transcribe scores 73.6 (BB) on agent readiness against Giggy Speech to Text's 54.5 (C), and leads in 5 of 7 scored categories. Giggy Speech to Text leads on maintenance \u0026 community.\n\n### Do Amazon Transcribe and Giggy Speech to Text need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Transcribe and Giggy Speech to Text without installing anything?\n\nYes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Giggy Speech to Text at https://api.giggy.ai/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-transcribe\", \"b\": \"giggy-stt\"}`. From a terminal: `anchor compare amazon-transcribe giggy-stt`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-transcribe.json and https://www.anchorterminal.com/api/v1/tools/giggy-stt.json\n\n## Other comparisons with Amazon Transcribe or Giggy Speech to Text\n\n- [Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)](https://www.anchorterminal.com/compare/amazon-transcribe-vs-assemblyai-stt.md)\n- [Amazon Transcribe vs Azure AI Speech speech-to-text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-azure-speech-to-text.md)\n- [Amazon Transcribe vs Cartesia Ink](https://www.anchorterminal.com/compare/amazon-transcribe-vs-cartesia-ink-stt.md)\n- [Amazon Transcribe vs Deepgram Speech-to-Text (Nova-3, Flux)](https://www.anchorterminal.com/compare/amazon-transcribe-vs-deepgram-stt.md)\n- [Amazon Transcribe vs ElevenLabs Scribe Speech to Text API](https://www.anchorterminal.com/compare/amazon-transcribe-vs-elevenlabs-scribe.md)\n- [Amazon Transcribe vs Gladia Speech-to-Text API + MCP](https://www.anchorterminal.com/compare/amazon-transcribe-vs-gladia-stt.md)\n- [Amazon Transcribe vs Google Cloud Speech-to-Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-google-speech-to-text.md)\n- [Amazon Transcribe vs Groq Speech-to-Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-groq-speech-to-text.md)\n- [Amazon Transcribe vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/amazon-transcribe-vs-mistral-voxtral-transcribe.md)\n- [Amazon Transcribe vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-openai-speech-to-text.md)\n- [Amazon Transcribe vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/amazon-transcribe-vs-rev-ai-stt.md)\n- [Amazon Transcribe vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-soniox-stt.md)\n- [Amazon Transcribe vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-speechmatics-stt.md)\n- [AssemblyAI Speech-to-Text (Universal) vs Giggy Speech to Text](https://www.anchorterminal.com/compare/assemblyai-stt-vs-giggy-stt.md)\n- [Azure AI Speech speech-to-text vs Giggy Speech to Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-giggy-stt.md)\n- [Cartesia Ink vs Giggy Speech to Text](https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-giggy-stt.md)\n- [Deepgram Speech-to-Text (Nova-3, Flux) vs Giggy Speech to Text](https://www.anchorterminal.com/compare/deepgram-stt-vs-giggy-stt.md)\n- [ElevenLabs Scribe Speech to Text API vs Giggy Speech to Text](https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-giggy-stt.md)\n- [Giggy Speech to Text vs Gladia Speech-to-Text API + MCP](https://www.anchorterminal.com/compare/giggy-stt-vs-gladia-stt.md)\n- [Giggy Speech to Text vs Google Cloud Speech-to-Text](https://www.anchorterminal.com/compare/giggy-stt-vs-google-speech-to-text.md)\n- [Giggy Speech to Text vs Groq Speech-to-Text](https://www.anchorterminal.com/compare/giggy-stt-vs-groq-speech-to-text.md)\n- [Giggy Speech to Text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/giggy-stt-vs-mistral-voxtral-transcribe.md)\n- [Giggy Speech to Text vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/giggy-stt-vs-openai-speech-to-text.md)\n- [Giggy Speech to Text vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/giggy-stt-vs-rev-ai-stt.md)\n- [Giggy Speech to Text vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/giggy-stt-vs-soniox-stt.md)\n- [Giggy Speech to Text vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/giggy-stt-vs-speechmatics-stt.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Transcribe vs Giggy Speech to Text", "url": "" } ], "description": "Amazon Transcribe scores 73.6 (BB) to Giggy Speech to Text's 54.5 (C) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Transcribe BB 73.6", "Giggy Speech to Text C 54.5", "scores" ], "h1": "Amazon Transcribe vs Giggy Speech to Text", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-transcribe-vs-giggy-stt", "published": "2026-10-01", "section": "tools", "title": "Amazon Transcribe vs Giggy Speech to Text for AI agents (2026)", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt" }, "tokens": { "markdown": 6700, "slim": 4530 }, "version": 1 }