{ "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": 104, "ranked": true, "rankOf": 1510, "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-bedrock", "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-polly", "amazon-nova-sonic", "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": { "setupChecked": true, "complianceChecked": true, "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-07T19:21:51.90617018Z", "lastOk": true, "lastStatus": 404, "lastMs": 335, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 271, "p95ms24h": 364, "samples24h": 238, "samples30d": 7920, "days": [ { "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": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-transcribe", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:58.591684858Z" }, { "registry": "npm", "name": "@aws-sdk/client-transcribe-streaming", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:58.822479826Z" }, { "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-06T23:05:56.587826348Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.126", "released": "2026-11-06", "seenAt": "2026-11-06T23:05:56.461063686Z" } ], "githubStars": 178, "npmWeekly": 805969, "pypiWeekly": 637851852, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:18.354437696Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/transcribe/latest/dg/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:35.873587592Z" }, "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-07T14:05:35.461309348Z", "changedAt": "2026-10-06T16:07:55.368671496Z", "fingerprint": "ecdbccfa98c4" }, { "url": "https://aws.amazon.com/transcribe/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:00:20.595439604Z", "changedAt": "2026-11-06T13:23:08.968887269Z", "fingerprint": "9fed68fee2ee" } ], "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-07T19:21:51.90617018Z" } }, "answer": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Inworld STT's 54.7 (C), and leads in 6 of 7 scored categories. Inworld STT leads on payments \u0026 pricing.", "b": { "slug": "inworld-stt", "name": "Inworld STT", "vendor": "Inworld AI", "vendorUrl": "https://inworld.ai", "kind": "model", "category": "speech-to-text", "summary": "Inworld's speech-to-text API runs its `inworld/inworld-stt-1` model in 30 languages over synchronous HTTP, bidirectional WebSocket streaming and asynchronous jobs, returning Voice Profile signals (age, emotion, pitch, accent) and turn detection alongside the transcript.", "url": "https://www.anchorterminal.com/tools/inworld-stt", "markdownUrl": "https://www.anchorterminal.com/tools/inworld-stt.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/inworld-stt.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/inworld-stt.json", "dns": "inworld-stt.grade.anchorterminal.com", "transports": [ "http", "websocket" ], "packages": [ { "registry": "npm", "name": "@inworld/cli" } ], "auth": "api-key", "authNotes": "Every call sends `Authorization: Basic` with the Base64 `key_id:secret` credential from the Portal or the CLI. Keys belong to a workspace and are deleted to revoke. Browsers pass a one-time token in the `bearer_` WebSocket subprotocol rather than the URL.", "pricing": "usage", "pricingNotes": "$0.15 an hour of audio on the free On-Demand plan and $0.10 on the paid plans ($25 to $1,500 a month), billed per second. On-Demand includes up to 400 minutes free. Diarisation and Voice Profile are separate per-second add-ons. Asynchronous jobs need a payment method.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or pricing page (checked 2026-11-06). Plans and credits are bought in the Portal.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.inworld.ai/stt/overview", "llmsTxt": "https://docs.inworld.ai/llms.txt", "capabilities": [ "speech.stt", "speech.streaming", "speech.batch", "speech.diarisation", "speech.languages" ], "tags": [ "hosted", "usage", "free-tier", "no-card", "closed-source", "llms-txt", "streaming", "batch", "mcp", "enterprise" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 54.7, "grade": "C", "agentReady": false, "rank": 900, "ranked": true, "rankOf": 1510, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 41, "payments": 40, "reliability": 60, "schema": 54, "security": 63, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Inworld STT costs $0.10 to $0.15 an hour with 400 free minutes, and covers files, live streams and async jobs in 30 languages with Voice Profile signals. There is no machine-readable spec, no public STT changelog and no readable status history, and diarisation is still experimental.", "bestFor": "Low-cost live transcription for voice agents, with speaker traits.", "strengths": [ "$0.15 an hour on the free plan and $0.10 on paid plans, billed per second, with 400 free minutes", "Sync, WebSocket streaming and async jobs on one model, with turn detection and Voice Profile signals", "Browser tokens travel in a WebSocket subprotocol, not the URL", "Zero data retention keeps audio and transcripts in memory, and the docs include it from the Developer plan", "llms.txt, Markdown twins and a docs MCP server" ], "weaknesses": [ "No OpenAPI or other machine-readable contract", "The STT release notes path asks for a login, so changes to the model aren't publicly dated", "Status history couldn't be read, and an SLA exists only for Enterprise", "Speaker diarisation is experimental and async jobs run on a `v1alpha` operations route", "Docs and the STT product page disagree on which plans include zero data retention" ], "agentNotes": [ "Send the Base64 credential as-is in `Authorization: Basic`; don't encode it again", "Wrap the first WebSocket message in `transcribeConfig`, because a malformed first frame closes the socket with 1005 and no error", "Use `POST /stt/v1/transcribe:async` for files over about 16 MB and collect the transcript within 7 days", "Retry 429 or gRPC code 8 with exponential backoff and jitter, and stay within the plan's streaming concurrency", "Stop sending audio when nobody speaks, since streams are billed for every second sent" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.7 } ], "editorialScores": { "ergonomics": 56, "maintenance": 41, "payments": 40, "reliability": 60, "schema": 54, "security": 63, "transparency": 45 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @inworld/cli", "claudeCode": "claude mcp add inworld -- inworld mcp" }, "letme": { "capability": "https://letme.dev/speech.stt", "tool": "https://letme.dev/inworld-stt" }, "sameCompany": [ "inworld-tts", "inworld-realtime", "inworld-voice-cloning" ], "area": "voice", "unitPrices": [ { "item": "STT-1, On-Demand", "unit": "audio-minute", "usd": 0.0025, "note": "$0.15 an hour" }, { "item": "STT-1, paid plans", "unit": "audio-minute", "usd": 0.00167, "note": "$0.10 an hour on Creator to Growth" } ], "provenance": { "legalEntity": "Theai, Inc. dba Inworld AI", "domain": "inworld.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://inworld.ai/terms", "privacy": "https://inworld.ai/privacy", "statusPage": "https://status.inworld.ai", "changelog": "https://docs.inworld.ai/release-notes/realtime", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Terms of Service (effective 11 June 2025) are an agreement with Theai, Inc. dba Inworld AI under California law, with courts in Santa Clara. The Privacy Notice (last updated 18 January 2026) names Theai, Inc.", "inworld.ai/.well-known/security.txt returns 404. The security page links a vulnerability report form.", "status.inworld.ai runs the open-source issue-status app, which draws incidents from GitHub issues in inworld-ai/inworld-issue-status. Its history wasn't read, because GitHub's robots.txt couldn't be read from our environment.", "inworld.ai's robots.txt allows Claude agents on the paths read and sets `Content-Signal: ai-train=no, search=yes, ai-input=no`. docs.inworld.ai has no such signal.", "The domain's registration date wasn't established, because the RDAP lookup failed.", "firstReleased is left empty. No dated STT launch was found, and the STT release notes path asks for a Portal login." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/inworld-stt.json", "live": { "slug": "inworld-stt", "versions": [ { "registry": "npm", "name": "@inworld/cli", "version": "1.5.0", "seenAt": "2026-11-06T23:35:05.474861108Z" } ], "npmWeekly": 290, "securityTxt": { "url": "https://inworld.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:11.794771951Z" }, "llmsTxt": { "url": "https://docs.inworld.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:47.741512787Z" }, "updatedAt": "2026-11-07T16:01:11.794771951Z" } }, "edges": [ { "by": 36, "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": "No OpenAPI or other machine-readable file. The usual spec paths redirect, and the reference pages are Markdown (0). llms.txt, Markdown twins and a docs MCP server (10). Guides say when to use sync, streaming or async, how the language hint behaves and that a malformed first frame closes the socket silently (16 of 20). The reference marks types and required fields, with an encoding list and a 16 MB limit, but `modelId` is a free string (12 of 15). Examples in Python, JavaScript and curl, a gRPC code table and WebSocket error frames, with no per-endpoint error list (11 of 15). Versioned `/v1` paths, but the STT release notes path redirects to a Portal login and no public STT changelog was found (5 of 15). Total 54." }, "scores": { "a": 90, "b": 54 } }, { "by": 25, "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 service with clear terms naming Theai, Inc. dba Inworld AI (15). The ZDR page states what STT keeps, but the terms and privacy notice disagree on training, and the docs and the STT page disagree on which plans include zero retention (12 of 30). No dated STT deprecation or change notices are public (8 of 20). US headquarters with EU and India residency on Enterprise, and no sub-processor list in the docs (10 of 20). Total 45." }, "scores": { "a": 85, "b": 60 } }, { "by": 24, "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 of the checklist. Voice Profile, word timestamps and diarisation are opt-in, and responses carry a `usage` block (18 of 25). No lists to page. Async jobs return an operation to poll (8 of 20). Errors carry a numeric gRPC code and message on both endpoints, but a malformed first message closes the socket with 1005 and no frame (12 of 20). Sync calls are stateless and async calls return an operation, with no idempotency key, and empty transcripts and add-ons are billed (10 of 20). A call needs a model, an encoding and the audio. No STT SDK was found, only the CLI and its MCP server and REST examples (8 of 15). Total 56." }, "scores": { "a": 80, "b": 56 } }, { "by": 20, "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. Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless `--write` is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side, via the `bearer_` WebSocket subprotocol, not the URL (25 of 30). The Terms (11 June 2025) say Inworld won't train generally available models on customers' non-public Materials, except feedback and flagged content, while the Privacy Notice (18 January 2026) lists training AI models among its uses, per the inworld-tts check of 4 November (12 of 20). Zero data retention keeps STT audio and transcripts in memory and out of logs, included on Developer ($300 a month) and above per the docs, while the STT page says Enterprise or a Growth add-on. Async results and audio go after 7 days, and no default period is given for logs (8 of 15). Usage is attributed per key and a Performance page shows errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 63." }, "scores": { "a": 83, "b": 63 } }, { "by": 19, "category": "maintenance", "leads": "amazon-transcribe", "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. No public STT changelog. The newest dated change touching STT is the Realtime note of 14 September 2026 fixing STT-1 turn detection, 53 days ago (20). The CLI, which carries the STT command and MCP tool, shipped 1.4.0 to 1.5.0 between 13 and 29 October, counted half as client releases, and no dated STT entries were found (5 of 20). Discord and support@inworld.ai, with no evidence of answers read (6 of 15). No official STT SDK; the CLI is current (5 of 15). CLI on npm under MIT, current, CI not read (5 of 10). Total 41." }, "scores": { "a": 60, "b": 41 } }, { "by": 15, "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 of the checklist. status.inworld.ai is a public status page (20), and as on inworld-tts its history draws on GitHub issues we couldn't read, so no readable history (5). Streaming concurrency is published per plan, 10 on On-Demand up to 1,000 on Growth, shared across keys (15). 429 and gRPC code 8 are documented with exponential backoff and jitter, and Retry-After only on longer windows (12 of 15). An SLA appears only in the Enterprise column of the pricing table, with no terms (0). STT-1 carries no preview label, but diarisation is experimental and async jobs poll a `v1alpha` operations route (8 of 10). 20 + 5 + 15 + 12 + 0 + 8 = 60." }, "scores": { "a": 75, "b": 60 } } ], "facts": [ { "a": "Model API", "b": "Model API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Inworld AI", "name": "Vendor" }, { "a": "https://transcribe.us-east-1.amazonaws.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, websocket", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$0.0017 per minute of audio", "name": "Price for speech-to-text" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 (SDKs)", "b": "none", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-25", "b": "2026-10-29", "name": "Last release" }, { "a": "2026-10-01", "b": "2025-06-11", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-01-18", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "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 Inworld STT's 54.7 (C), and leads in 6 of 7 scored categories. Inworld STT leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Amazon Transcribe or Inworld STT?" }, { "answer": "Both need an API key.", "question": "Do Amazon Transcribe and Inworld STT need an API key?" }, { "answer": "Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com. No hosted endpoint is listed for Inworld STT.", "question": "Can an agent call Amazon Transcribe and Inworld STT without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 60", "Schema \u0026 documentation, 90 against 54", "Agent ergonomics, 80 against 56", "Security \u0026 auth, 83 against 63", "Maintenance \u0026 community, 60 against 41", "Transparency \u0026 trust, 85 against 60" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "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": [ "Payments \u0026 pricing, 40 against 30" ], "also": null, "goodFor": "Low-cost live transcription for voice agents, with speaker traits.", "slug": "inworld-stt", "watchFor": "No OpenAPI or other machine-readable contract" } ], "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" } ], "inworld-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-giggy-stt.json", "title": "Amazon Transcribe vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt" }, { "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-ibm-watson-stt.json", "title": "Amazon Transcribe vs IBM Watson Speech to Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-ibm-watson-stt" }, { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-minimax-stt.json", "title": "Amazon Transcribe vs MiniMax Speech-to-Text", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-minimax-stt" }, { "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-smallest-pulse-stt.json", "title": "Amazon Transcribe vs Smallest.ai Pulse STT", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-smallest-pulse-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-inworld-stt.json", "title": "AssemblyAI Speech-to-Text (Universal) vs Inworld STT", "url": "https://www.anchorterminal.com/compare/assemblyai-stt-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.json", "title": "Azure AI Speech speech-to-text vs Inworld STT", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-inworld-stt.json", "title": "Cartesia Ink vs Inworld STT", "url": "https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/deepgram-stt-vs-inworld-stt.json", "title": "Deepgram Speech-to-Text (Nova-3, Flux) vs Inworld STT", "url": "https://www.anchorterminal.com/compare/deepgram-stt-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-inworld-stt.json", "title": "ElevenLabs Scribe Speech to Text API vs Inworld STT", "url": "https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/giggy-stt-vs-inworld-stt.json", "title": "Giggy Speech to Text vs Inworld STT", "url": "https://www.anchorterminal.com/compare/giggy-stt-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/gladia-stt-vs-inworld-stt.json", "title": "Gladia Speech-to-Text API + MCP vs Inworld STT", "url": "https://www.anchorterminal.com/compare/gladia-stt-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/google-speech-to-text-vs-inworld-stt.json", "title": "Google Cloud Speech-to-Text vs Inworld STT", "url": "https://www.anchorterminal.com/compare/google-speech-to-text-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/groq-speech-to-text-vs-inworld-stt.json", "title": "Groq Speech-to-Text vs Inworld STT", "url": "https://www.anchorterminal.com/compare/groq-speech-to-text-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/ibm-watson-stt-vs-inworld-stt.json", "title": "IBM Watson Speech to Text vs Inworld STT", "url": "https://www.anchorterminal.com/compare/ibm-watson-stt-vs-inworld-stt" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-minimax-stt.json", "title": "Inworld STT vs MiniMax Speech-to-Text", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-minimax-stt" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe.json", "title": "Inworld STT vs Mistral Voxtral Transcribe", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.json", "title": "Inworld STT vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-rev-ai-stt.json", "title": "Inworld STT vs Rev AI Speech-to-Text API", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-rev-ai-stt" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-smallest-pulse-stt.json", "title": "Inworld STT vs Smallest.ai Pulse STT", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-smallest-pulse-stt" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-soniox-stt.json", "title": "Inworld STT vs Soniox Speech-to-Text", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-soniox-stt" }, { "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-speechmatics-stt.json", "title": "Inworld STT vs Speechmatics Speech-to-Text", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-speechmatics-stt" } ], "panel": null, "scores": [ { "amazon-transcribe": 75, "by": 15, "edge": "amazon-transcribe", "inworld-stt": 60, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-transcribe": 90, "by": 36, "edge": "amazon-transcribe", "inworld-stt": 54, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-transcribe": 80, "by": 24, "edge": "amazon-transcribe", "inworld-stt": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "amazon-transcribe": 83, "by": 20, "edge": "amazon-transcribe", "inworld-stt": 63, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "amazon-transcribe": 30, "by": 10, "edge": "inworld-stt", "inworld-stt": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-transcribe": 60, "by": 19, "edge": "amazon-transcribe", "inworld-stt": 41, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-transcribe": 85, "by": 25, "edge": "amazon-transcribe", "inworld-stt": 60, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Inworld STT's 54.7 (C), and leads in 6 of 7 scored categories. Inworld STT leads on payments \u0026 pricing. Both do speech-to-text.", "tasks": [ { "a": "$0.36 to $0.60", "b": "$0.10 to $0.15", "cheaper": "inworld-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.", "inworld-stt": "Inworld STT costs $0.10 to $0.15 an hour with 400 free minutes, and covers files, live streams and async jobs in 30 languages with Voice Profile signals. There is no machine-readable spec, no public STT changelog and no readable status history, and diarisation is still experimental." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt", "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.min.md" }, "markdown": "Amazon Transcribe scores 73.6 (BB) on agent readiness against Inworld STT's 54.7 (C), and leads in 6 of 7 scored categories. Inworld STT leads on payments \u0026 pricing. Both do speech-to-text.\n\n- Amazon Transcribe: grade BB, 73.6/100, rank #104 of 1510. Markdown https://www.anchorterminal.com/tools/amazon-transcribe.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-transcribe.json\n- Inworld STT: grade C, 54.7/100, rank #900 of 1510. Markdown https://www.anchorterminal.com/tools/inworld-stt.md · JSON https://www.anchorterminal.com/api/v1/tools/inworld-stt.json\n- Best speech-to-text APIs for AI agents: https://www.anchorterminal.com/best/speech-to-text/index.md\n- All 320 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 60\n- Schema \u0026 documentation, 90 against 54\n- Agent ergonomics, 80 against 56\n- Security \u0026 auth, 83 against 63\n- Maintenance \u0026 community, 60 against 41\n- Transparency \u0026 trust, 85 against 60\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\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### Inworld STT (C)\n\nGood for: Low-cost live transcription for voice agents, with speaker traits.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: No OpenAPI or other machine-readable contract\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Amazon Transcribe +36\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- Inworld STT (54): No OpenAPI or other machine-readable file. The usual spec paths redirect, and the reference pages are Markdown (0). llms.txt, Markdown twins and a docs MCP server (10). Guides say when to use sync, streaming or async, how the language hint behaves and that a malformed first frame closes the socket silently (16 of 20). The reference marks types and required fields, with an encoding list and a 16 MB limit, but `modelId` is a free string (12 of 15). Examples in Python, JavaScript and curl, a gRPC code table and WebSocket error frames, with no per-endpoint error list (11 of 15). Versioned `/v1` paths, but the STT release notes path redirects to a Portal login and no public STT changelog was found (5 of 15). Total 54.\n\n### Transparency \u0026 trust: Amazon Transcribe +25\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- Inworld STT (60): Closed service with clear terms naming Theai, Inc. dba Inworld AI (15). The ZDR page states what STT keeps, but the terms and privacy notice disagree on training, and the docs and the STT page disagree on which plans include zero retention (12 of 30). No dated STT deprecation or change notices are public (8 of 20). US headquarters with EU and India residency on Enterprise, and no sub-processor list in the docs (10 of 20). Total 45.\n\n### Agent ergonomics: Amazon Transcribe +24\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- Inworld STT (56): API reading of the checklist. Voice Profile, word timestamps and diarisation are opt-in, and responses carry a `usage` block (18 of 25). No lists to page. Async jobs return an operation to poll (8 of 20). Errors carry a numeric gRPC code and message on both endpoints, but a malformed first message closes the socket with 1005 and no frame (12 of 20). Sync calls are stateless and async calls return an operation, with no idempotency key, and empty transcripts and add-ons are billed (10 of 20). A call needs a model, an encoding and the audio. No STT SDK was found, only the CLI and its MCP server and REST examples (8 of 15). Total 56.\n\n### Security \u0026 auth: Amazon Transcribe +20\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- Inworld STT (63): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless `--write` is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side, via the `bearer_` WebSocket subprotocol, not the URL (25 of 30). The Terms (11 June 2025) say Inworld won't train generally available models on customers' non-public Materials, except feedback and flagged content, while the Privacy Notice (18 January 2026) lists training AI models among its uses, per the inworld-tts check of 4 November (12 of 20). Zero data retention keeps STT audio and transcripts in memory and out of logs, included on Developer ($300 a month) and above per the docs, while the STT page says Enterprise or a Growth add-on. Async results and audio go after 7 days, and no default period is given for logs (8 of 15). Usage is attributed per key and a Performance page shows errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 63.\n\n### Maintenance \u0026 community: Amazon Transcribe +19\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- Inworld STT (41): Read as a model. No public STT changelog. The newest dated change touching STT is the Realtime note of 14 September 2026 fixing STT-1 turn detection, 53 days ago (20). The CLI, which carries the STT command and MCP tool, shipped 1.4.0 to 1.5.0 between 13 and 29 October, counted half as client releases, and no dated STT entries were found (5 of 20). Discord and support@inworld.ai, with no evidence of answers read (6 of 15). No official STT SDK; the CLI is current (5 of 15). CLI on npm under MIT, current, CI not read (5 of 10). Total 41.\n\n### Reliability: Amazon Transcribe +15\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- Inworld STT (60): Hosted reading of the checklist. status.inworld.ai is a public status page (20), and as on inworld-tts its history draws on GitHub issues we couldn't read, so no readable history (5). Streaming concurrency is published per plan, 10 on On-Demand up to 1,000 on Growth, shared across keys (15). 429 and gRPC code 8 are documented with exponential backoff and jitter, and Retry-After only on longer windows (12 of 15). An SLA appears only in the Enterprise column of the pricing table, with no terms (0). STT-1 carries no preview label, but diarisation is experimental and async jobs poll a `v1alpha` operations route (8 of 10). 20 + 5 + 15 + 12 + 0 + 8 = 60.\n\n## Score by category\n\n| Category | Weight | Amazon Transcribe | Inworld STT | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 60 | Amazon Transcribe +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 54 | Amazon Transcribe +36 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 56 | Amazon Transcribe +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 83 | 63 | Amazon Transcribe +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Inworld STT +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 41 | Amazon Transcribe +19 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 85 | 60 | Amazon Transcribe +25 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **73.6 · BB** | **54.7 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon Transcribe | Inworld STT |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | Amazon Web Services | Inworld AI |\n| Hosted endpoint | `https://transcribe.us-east-1.amazonaws.com` | no (local only) |\n| Transports | HTTP | HTTP, websocket |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for speech-to-text | not published | $0.0017 per minute of audio |\n| x402 | no | no |\n| Licence | Apache-2.0 (SDKs) | none |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-25 | 2026-10-29 |\n| Terms last updated | 2026-10-01 | 2025-06-11 |\n| Privacy policy last updated | 2026-05-18 | 2026-01-18 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\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 | Inworld STT |\n| --- | --- | --- |\n| Transcribe a one-hour meeting | $0.36 to $0.60 | $0.10 to $0.15 |\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### Inworld STT\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**Inworld STT.** Inworld STT costs $0.10 to $0.15 an hour with 400 free minutes, and covers files, live streams and async jobs in 30 languages with Voice Profile signals. There is no machine-readable spec, no public STT changelog and no readable status history, and diarisation is still experimental.\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### Inworld STT\n\n1. Send the Base64 credential as-is in `Authorization: Basic`; don't encode it again\n2. Wrap the first WebSocket message in `transcribeConfig`, because a malformed first frame closes the socket with 1005 and no error\n3. Use `POST /stt/v1/transcribe:async` for files over about 16 MB and collect the transcript within 7 days\n4. Retry 429 or gRPC code 8 with exponential backoff and jitter, and stay within the plan's streaming concurrency\n5. Stop sending audio when nobody speaks, since streams are billed for every second sent\n\n## Questions\n\n### Which is better for AI agents, Amazon Transcribe or Inworld STT?\n\nAmazon Transcribe scores 73.6 (BB) on agent readiness against Inworld STT's 54.7 (C), and leads in 6 of 7 scored categories. Inworld STT leads on payments \u0026 pricing.\n\n### Do Amazon Transcribe and Inworld STT need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Transcribe and Inworld STT without installing anything?\n\nAmazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com. No hosted endpoint is listed for Inworld STT.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-transcribe\", \"b\": \"inworld-stt\"}`. From a terminal: `anchor compare amazon-transcribe inworld-stt`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-transcribe.json and https://www.anchorterminal.com/api/v1/tools/inworld-stt.json\n\n## Other comparisons with Amazon Transcribe or Inworld STT\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 Giggy Speech to Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-giggy-stt.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 IBM Watson Speech to Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-ibm-watson-stt.md)\n- [Amazon Transcribe vs MiniMax Speech-to-Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-minimax-stt.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 Smallest.ai Pulse STT](https://www.anchorterminal.com/compare/amazon-transcribe-vs-smallest-pulse-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 Inworld STT](https://www.anchorterminal.com/compare/assemblyai-stt-vs-inworld-stt.md)\n- [Azure AI Speech speech-to-text vs Inworld STT](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.md)\n- [Cartesia Ink vs Inworld STT](https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-inworld-stt.md)\n- [Deepgram Speech-to-Text (Nova-3, Flux) vs Inworld STT](https://www.anchorterminal.com/compare/deepgram-stt-vs-inworld-stt.md)\n- [ElevenLabs Scribe Speech to Text API vs Inworld STT](https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-inworld-stt.md)\n- [Giggy Speech to Text vs Inworld STT](https://www.anchorterminal.com/compare/giggy-stt-vs-inworld-stt.md)\n- [Gladia Speech-to-Text API + MCP vs Inworld STT](https://www.anchorterminal.com/compare/gladia-stt-vs-inworld-stt.md)\n- [Google Cloud Speech-to-Text vs Inworld STT](https://www.anchorterminal.com/compare/google-speech-to-text-vs-inworld-stt.md)\n- [Groq Speech-to-Text vs Inworld STT](https://www.anchorterminal.com/compare/groq-speech-to-text-vs-inworld-stt.md)\n- [IBM Watson Speech to Text vs Inworld STT](https://www.anchorterminal.com/compare/ibm-watson-stt-vs-inworld-stt.md)\n- [Inworld STT vs MiniMax Speech-to-Text](https://www.anchorterminal.com/compare/inworld-stt-vs-minimax-stt.md)\n- [Inworld STT vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe.md)\n- [Inworld STT vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.md)\n- [Inworld STT vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/inworld-stt-vs-rev-ai-stt.md)\n- [Inworld STT vs Smallest.ai Pulse STT](https://www.anchorterminal.com/compare/inworld-stt-vs-smallest-pulse-stt.md)\n- [Inworld STT vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/inworld-stt-vs-soniox-stt.md)\n- [Inworld STT vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/inworld-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-07", "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 Inworld STT", "url": "" } ], "description": "Amazon Transcribe scores 73.6 (BB) to Inworld STT's 54.7 (C) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Transcribe BB 73.6", "Inworld STT C 54.7", "scores" ], "h1": "Amazon Transcribe vs Inworld STT", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-transcribe-vs-inworld-stt", "published": "2026-10-01", "section": "tools", "title": "Amazon Transcribe vs Inworld STT for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt" }, "tokens": { "markdown": 6050, "slim": 3730 }, "version": 1 }