{ "data": { "a": { "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": 895, "ranked": true, "rankOf": 1486, "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" } }, "answer": "OpenAI Speech to Text scores 75 (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": "openai-speech-to-text", "name": "OpenAI Speech to Text", "vendor": "OpenAI", "vendorUrl": "https://openai.com", "kind": "model", "category": "speech-to-text", "summary": "OpenAI's speech-to-text API. It transcribes uploaded audio files through `/v1/audio/transcriptions`, translates recordings into English through `/v1/audio/translations`, and transcribes live audio in Realtime transcription sessions over WebSocket or WebRTC.", "url": "https://www.anchorterminal.com/tools/openai-speech-to-text", "markdownUrl": "https://www.anchorterminal.com/tools/openai-speech-to-text.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/openai-speech-to-text.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/openai-speech-to-text.json", "dns": "openai-speech-to-text.grade.anchorterminal.com", "repo": "https://github.com/openai/openai-python", "license": "Proprietary hosted service. The service terms were not read (see open questions). The Python SDK is Apache-2.0 and the OpenAPI document is MIT", "transports": [ "http", "websocket" ], "remoteUrl": "https://api.openai.com/v1", "packages": [ { "registry": "pypi", "name": "openai" } ], "auth": "api-key", "authNotes": "Bearer API key created by a person in the platform console (https://platform.openai.com/settings/organization/api-keys). Projects can carry a model allowlist or denylist and an IP allowlist, and Admin API keys are a separate credential that cannot call the audio endpoints (https://developers.openai.com/api/docs/guides/admin-apis).", "pricing": "usage", "pricingNotes": "$0.0045 an audio minute for `gpt-transcribe` and $0.017 for `gpt-live-transcribe`, billed from prepaid credits (https://developers.openai.com/api/docs/pricing). The rate limits guide names a Free tier with a $100 monthly usage limit, and the `gpt-transcribe` model page lists limits only from the Build tier, which needs $5 of credit purchases. Whether a new account can transcribe without paying was not established.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the transcription guides, the endpoint reference, the pricing page or the OpenAPI document (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 31785, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://developers.openai.com/api/docs/guides/speech-to-text", "llmsTxt": "https://developers.openai.com/llms.txt", "openapi": "https://github.com/openai/openai-openapi/blob/main/openapi.yaml", "capabilities": [ "speech.stt", "speech.streaming", "speech.batch", "speech.diarisation", "speech.languages" ], "tags": [ "official", "hosted", "model", "streaming", "diarisation", "llms-txt", "openapi", "python", "typescript", "go", "java" ], "lastRelease": "2026-08-26", "graded": true, "anchor": { "graded": true, "score": 75, "grade": "BB", "agentReady": true, "rank": 74, "ranked": true, "rankOf": 1486, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 71, "payments": 30, "reliability": 65, "schema": 89, "security": 97, "transparency": 90 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "`gpt-transcribe` costs $0.0045 an audio minute, and the audio endpoints keep no abuse-monitoring logs or application state. Speaker labels, word timestamps and subtitles exist only on `whisper-1` and `gpt-4o-transcribe-diarize`, which shut down on 26 February 2027 with no replacement named for those functions.", "bestFor": "Suited to plain transcription of recorded files at a low price a minute and to teams already holding an OpenAI key.", "strengths": [ "`gpt-transcribe` is priced at $0.0045 an audio minute on a public page, with per-tier request limits of 5,000, 10,000 and 30,000 a minute", "The data controls page lists `/v1/audio/transcriptions` and `/v1/audio/translations` with no training, no abuse-monitoring retention and no stored application state", "A public OpenAPI 3.1 document, llms.txt and a Markdown twin of every docs page cover the audio endpoints", "Transcription usage can be pulled per API key from the organisation usage API", "Guide examples cover JavaScript, Python, Go, Java, C#, Ruby, a CLI and curl, and `file` and `model` are the only required fields" ], "weaknesses": [ "`whisper-1`, `gpt-4o-transcribe`, `gpt-4o-mini-transcribe`, `gpt-4o-transcribe-diarize` and `/v1/audio/translations` shut down on 26 February 2027", "The two named replacement models return no speaker labels, word timestamps or `srt` and `vtt` output in the reviewed documentation", "Audio was degraded for an hour on 17 September and for 5 hours 21 minutes on 29 September 2026 in API-wide incidents", "Uploads stop at 25 MB, the caller splits longer recordings, and the `gpt-transcribe` model page marks the Batch API as not supported", "The endpoint reference's first example still names the deprecated `gpt-4o-transcribe`" ], "agentNotes": [ "Send `gpt-transcribe` to `POST /v1/audio/transcriptions` for recorded files. Use `languages` (a list), not `language`, and never send both.", "Keep each upload at 25 MB or less. Split longer audio between sentences and pass the previous chunk's text in `prompt`.", "For speaker labels send `gpt-4o-transcribe-diarize` with `response_format=diarized_json` and `chunking_strategy=auto` for audio over 30 seconds. Plan for its shutdown on 26 February 2027.", "Word timestamps, `srt` and `vtt` need `whisper-1`, which cannot stream and shuts down on 26 February 2027. Move English translation to `v1/realtime/translations` before then.", "On 429 or 503 wait at least `Retry-After` when present, then back off with jitter. Do not retry `credit_balance_exhausted` or spend-limit errors." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75 } ], "editorialScores": { "ergonomics": 78, "maintenance": 71, "payments": 30, "reliability": 65, "schema": 89, "security": 97, "transparency": 85 }, "provenanceScore": 95, "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 openai", "http": "curl --request POST \\\n --url https://api.openai.com/v1/audio/transcriptions \\\n --header \"Authorization: Bearer $OPENAI_API_KEY\" \\\n --header 'Content-Type: multipart/form-data' \\\n --form file=@/path/to/file/audio.mp3 \\\n --form model=gpt-transcribe" }, "letme": { "capability": "https://letme.dev/speech.stt", "tool": "https://letme.dev/openai-speech-to-text" }, "sameCompany": [ "openai-api", "openai-embeddings", "openai-guardrails", "openai-moderation", "openai-image-api", "openai-sora", "gpt-live", "openai-realtime", "openai-agents-sdk", "openai-decisions-api", "openai-agents-api", "openai-codex", "gpt-oss-120b", "gpt-oss-20b" ], "area": "voice", "unitPrices": [ { "item": "gpt-transcribe", "unit": "audio-minute", "usd": 0.0045 }, { "item": "gpt-live-transcribe (live audio)", "unit": "audio-minute", "usd": 0.017 }, { "item": "whisper-1 (deprecated)", "unit": "audio-minute", "usd": 0.006 }, { "item": "gpt-4o-transcribe-diarize (deprecated, estimated from token prices)", "unit": "audio-minute", "usd": 0.006 } ], "provenance": { "legalEntity": "OpenAI OpCo, LLC", "domain": "openai.com", "domainRegistered": "2007-01-19", "domainNote": "openai.com was registered in 2007, before OpenAI existed.", "endpointOnVendorDomain": true, "terms": "https://openai.com/policies/services-agreement/", "privacy": "https://openai.com/policies/privacy-policy/", "statusPage": "https://status.openai.com", "changelog": "https://developers.openai.com/api/docs/changelog", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "Same entity, terms and privacy policy as the OpenAI API listing. The legal entity and the two policy URLs stand per that listing's check of 26 September. openai.com answered the services agreement with HTTP 403 on 1 November 2026.", "RDAP gives openai.com a registration date of 2007-01-19, per the OpenAI API listing.", "openai.com/.well-known/security.txt, re-read on 1 November 2026, is PGP-signed with Bugcrowd and email contacts and a disclosure policy, and has no Expires field.", "status.openai.com lists Audio and Realtime components under the API group." ], "score": 95 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "paid-only", "freeTier": true, "minutes": 5, "credential": "api-key", "hosting": [ "US", "EU", "UK", "CA", "APAC" ], "euResidency": "enterprise", "trainsOnData": "no", "zeroRetention": "enterprise", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "ISO 42001", "CSA STAR", "HIPAA (BAA available)", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/openai-speech-to-text.json", "live": { "slug": "openai-speech-to-text", "probe": { "target": "https://api.openai.com/v1", "method": "get", "lastAt": "2026-11-07T18:20:44.460880195Z", "lastOk": true, "lastStatus": 404, "lastMs": 131, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 142, "p95ms24h": 185, "samples24h": 239, "samples30d": 7205, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "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": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.openai.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:48.573028025Z" }, "versions": [ { "registry": "github", "name": "openai/openai-python", "version": "v3.47.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:52:11.246277153Z" }, { "registry": "pypi", "name": "openai", "version": "3.46.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:52:11.134987892Z" } ], "githubStars": 32064, "pypiWeekly": 91156146, "securityTxt": { "url": "https://openai.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:49.231731777Z" }, "llmsTxt": { "url": "https://developers.openai.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:36.672076509Z" }, "domain": { "domain": "openai.com", "registered": "2007-01-19", "source": "https://rdap.verisign.com/com/v1/domain/openai.com", "checkedAt": "2026-11-01T14:19:18.345389832Z" }, "github": { "repo": "openai/openai-python", "checkedAt": "2026-11-02T09:13:10.459648475Z", "stars": 32015, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T03:47:02Z", "openIssues": 40, "openPRs": 54, "issuesOpened90d": 42, "issuesClosed90d": 220, "prsMerged90d": 437, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-02T03:19:31Z" }, "replies": { "sampled": 25, "unanswered": 9, "medianDays": 3.6 } }, "updatedAt": "2026-11-07T18:21:48.573028025Z" } }, "edges": [ { "by": 35, "category": "schema", "leads": "openai-speech-to-text", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Model reading. The public OpenAPI 3.1 document in openai/openai-openapi (version 2.3.0, last committed 31 October) covers `/audio/transcriptions` and `/audio/translations` and names `gpt-transcribe` (25). llms.txt and a Markdown twin of every docs page (10). The transcription overview says which model to use for files, live audio, speaker labels, timestamps and translation, and the file guide now opens by recommending `gpt-transcribe` and saying the specialised examples use deprecated models (18 of 20). `response_format`, `timestamp_granularities` and `model` are enums in the document. `language` is a plain string, and which formats each model accepts is stated in prose only (12 of 15). Examples in seven languages and curl, and an error codes page with a cause and fix for each. The Markdown twin of the endpoint reference now lists the body parameters, including `languages` and `keywords` for `gpt-transcribe`, but its first example still names the deprecated `gpt-4o-transcribe`, and the guide lists seven input formats where the document lists nine (12 of 15, was 11). A dated changelog and deprecations page. `gpt-transcribe` has one alias and no dated snapshot to pin (12 of 15). 25 + 10 + 18 + 12 + 12 + 12 = 89." }, "scores": { "a": 54, "b": 89 } }, { "by": 34, "category": "security", "leads": "openai-speech-to-text", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Model reading, on the lines the OpenAI API and Decisions API listings use. Project keys with permissions per key, service-account keys through the Administration API and workload identity federation, per the Decisions API listing's read of 8 October. The access-control guide, re-read on 1 November, puts audio under one Model capabilities permission with chat completions, embeddings and images, so a restricted key can't be limited to the audio endpoints alone (27 of 30, as the Decisions API listing, was 26). The data controls page says API data isn't used for training unless the customer opts in (20). Both audio endpoints are listed with no abuse-monitoring retention, no application state and Zero Data Retention eligibility, re-read on 1 November (15). The Admin API has an audit log endpoint, and the OpenAPI document has `GET /organization/usage/audio_transcriptions` grouped by project, API key or model, the per-key usage view both other OpenAI listings got 15 for (15, was 13). security.txt, re-read on 1 November, is PGP-signed, names a Bugcrowd programme and a coordinated disclosure policy and has no Expires field. trust.openai.com, read on 1 November, names SOC 2 Type 2 and ISO/IEC 27001, 27017, 27018 and 27701 (20, was 12 when no trust centre was read, the award both other OpenAI listings carry). 27 + 20 + 15 + 15 + 20 = 97." }, "scores": { "a": 63, "b": 97 } }, { "by": 30, "category": "maintenance", "leads": "openai-speech-to-text", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Model reading. The last dated change to transcription is still the deprecation notice of 26 August 2026, 67 days before 1 November, after the release of `gpt-transcribe` and `gpt-live-transcribe` on 28 July (20 of 30). The deprecations page promises at least six months' notice for generally available models, and the four transcription models got six months to the day. On 14 October GA GPT-4 series models got 92 days with no reason stated, so the policy reads as a minimum of two to three months in practice, as the OpenAI API and Decisions API listings read it (8 of 12, was 12). Four of the five file transcription models were deprecated within a month of their replacements shipping, and the replacements don't cover diarisation, timestamps or subtitles (2 of 8). The dated changelog has two transcription entries in 90 days among dozens for the API (13 of 15). Python SDK replies were not sampled (5 of 10). Python SDK v3.42.0 was tagged on 31 October 2026, with v3.41.0 on 28 October and v3.40.0 on 27 October (15). CI, CodeQL and a breaking-change check run in the repository (8 of 10). 20 + 8 + 2 + 13 + 5 + 15 + 8 = 71." }, "scores": { "a": 41, "b": 71 } }, { "by": 30, "category": "transparency", "leads": "openai-speech-to-text", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The hosted models are closed with clear terms, the Python SDK Apache-2.0 and the OpenAPI document MIT, per the OpenAI API listing's check of the services agreement. openai.com answered the services agreement with 403 again on 1 November (15, was 12). The data controls page, re-read on 1 November, lists both audio endpoints with no training, no abuse-monitoring retention, no application state and Zero Data Retention eligibility. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (30 of 30, was 28). A deprecations page with notice periods by model class, dated shutdowns and replacements, including `/v1/audio/translations` to `v1/realtime/translations` (20). Data residency is documented by region and endpoint, with the audio endpoints in every listed region for storage and in the United States and Europe for processing. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (20 of 20, was 16). 15 + 30 + 20 + 20 = 85." }, "scores": { "a": 60, "b": 90 } }, { "by": 22, "category": "ergonomics", "leads": "openai-speech-to-text", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "API reading, as for the other speech-to-text listings. The default `json` response is the text, detected languages and usage, `text` returns a bare string, and segments, words and speaker labels come only when asked for on the models that have them (20 of 25). There is no transcript store to page through. Files stop at 25 MB, the caller splits longer audio, and the `gpt-transcribe` model page marks the Batch API as not supported (10 of 20). Errors carry `message`, `type`, `param` and `code`, and the error codes page gives a fix for each status (18 of 20). The call is stateless and safe to retry, and the Python SDK retries 408, 409, 429 and 5xx twice by default. No idempotency key applies to this endpoint (15 of 20). `file` and `model` are the only required fields, with guide examples for JavaScript, Python, Go, Java, C# and Ruby SDKs and a CLI (15)." }, "scores": { "a": 56, "b": 78 } }, { "by": 10, "category": "payments", "leads": "inworld-stt", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-hour prices for every plan published without a login (20). On-Demand includes up to 400 minutes of STT and lists no payment method, while async jobs need one (20). A person signs up in the Portal or through `inworld login` in a browser before a key exists (0). Total 40.", "b": "No x402, MPP or L402 on the pricing page, re-read on 1 November (0). $0.0045 an audio minute for `gpt-transcribe`, $0.017 for `gpt-live-transcribe` and $0.006 for `whisper-1` on the public pricing page (20). The rate limits guide lists a Free tier capped at $100 a month in allowed countries, while the `gpt-transcribe` model page's rate-limit table starts at Build, which needs $5 of credit. Half, the reading both other OpenAI listings use for the same pages (10, was 0). A person signs up in a browser and creates the key in the console (0). 0 + 20 + 10 + 0 = 30." }, "scores": { "a": 40, "b": 30 } } ], "facts": [ { "a": "Model API", "b": "Model API", "name": "Kind" }, { "a": "Inworld AI", "b": "OpenAI", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.openai.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, websocket", "b": "HTTP, websocket", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.0017 per minute of audio", "b": "not published", "name": "Price for speech-to-text" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary hosted service. The service terms were not read (see open questions). The Python SDK is Apache-2.0 and the OpenAPI document is MIT", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-29", "b": "2026-08-26", "name": "Last release" }, { "a": "2025-06-11", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-01-18", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "32k stars", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "OpenAI Speech to Text scores 75 (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, Inworld STT or OpenAI Speech to Text?" }, { "answer": "Both need an API key.", "question": "Do Inworld STT and OpenAI Speech to Text need an API key?" }, { "answer": "No hosted endpoint is listed for Inworld STT. OpenAI Speech to Text has a hosted endpoint at https://api.openai.com/v1.", "question": "Can an agent call Inworld STT and OpenAI Speech to Text without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Low-cost live transcription for voice agents, with speaker traits.", "slug": "inworld-stt", "watchFor": "No OpenAPI or other machine-readable contract" }, { "aheadOn": [ "Reliability, 65 against 60", "Schema \u0026 documentation, 89 against 54", "Agent ergonomics, 78 against 56", "Security \u0026 auth, 97 against 63", "Maintenance \u0026 community, 71 against 41", "Transparency \u0026 trust, 90 against 60" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "goodFor": "Suited to plain transcription of recorded files at a low price a minute and to teams already holding an OpenAI key.", "slug": "openai-speech-to-text", "watchFor": "`whisper-1`, `gpt-4o-transcribe`, `gpt-4o-mini-transcribe`, `gpt-4o-transcribe-diarize` and `/v1/audio/translations` shut down on 26 February 2027" } ], "history": { "inworld-stt": null, "openai-speech-to-text": [ { "causes": [ "product", "evidence", "correction" ], "date": "2026-11-01", "delta": 2.4, "from": 72.6, "fromGrade": "BB", "to": 75, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 72.4, "fromGrade": "BB", "to": 72.6, "toGrade": "BB" } ] }, "job": { "capability": "speech.stt", "name": "Speech-to-text" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.json", "title": "Amazon Transcribe vs Inworld STT", "url": "https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt" }, { "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/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/assemblyai-stt-vs-openai-speech-to-text.json", "title": "AssemblyAI Speech-to-Text (Universal) vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/assemblyai-stt-vs-openai-speech-to-text" }, { "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/azure-speech-to-text-vs-openai-speech-to-text.json", "title": "Azure AI Speech speech-to-text vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-openai-speech-to-text" }, { "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/cartesia-ink-stt-vs-openai-speech-to-text.json", "title": "Cartesia Ink vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-openai-speech-to-text" }, { "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/deepgram-stt-vs-openai-speech-to-text.json", "title": "Deepgram Speech-to-Text (Nova-3, Flux) vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/deepgram-stt-vs-openai-speech-to-text" }, { "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/elevenlabs-scribe-vs-openai-speech-to-text.json", "title": "ElevenLabs Scribe Speech to Text API vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-openai-speech-to-text" }, { "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/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/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/gladia-stt-vs-openai-speech-to-text.json", "title": "Gladia Speech-to-Text API + MCP vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/gladia-stt-vs-openai-speech-to-text" }, { "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/google-speech-to-text-vs-openai-speech-to-text.json", "title": "Google Cloud Speech-to-Text vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/google-speech-to-text-vs-openai-speech-to-text" }, { "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/groq-speech-to-text-vs-openai-speech-to-text.json", "title": "Groq Speech-to-Text vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/groq-speech-to-text-vs-openai-speech-to-text" }, { "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/ibm-watson-stt-vs-openai-speech-to-text.json", "title": "IBM Watson Speech to Text vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/ibm-watson-stt-vs-openai-speech-to-text" }, { "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-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" }, { "json": "https://www.anchorterminal.com/compare/minimax-stt-vs-openai-speech-to-text.json", "title": "MiniMax Speech-to-Text vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/minimax-stt-vs-openai-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-openai-speech-to-text.json", "title": "Mistral Voxtral Transcribe vs OpenAI Speech to Text", "url": "https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-openai-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-rev-ai-stt.json", "title": "OpenAI Speech to Text vs Rev AI Speech-to-Text API", "url": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-rev-ai-stt" }, { "json": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-smallest-pulse-stt.json", "title": "OpenAI Speech to Text vs Smallest.ai Pulse STT", "url": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-smallest-pulse-stt" }, { "json": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-soniox-stt.json", "title": "OpenAI Speech to Text vs Soniox Speech-to-Text", "url": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-soniox-stt" }, { "json": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-speechmatics-stt.json", "title": "OpenAI Speech to Text vs Speechmatics Speech-to-Text", "url": "https://www.anchorterminal.com/compare/openai-speech-to-text-vs-speechmatics-stt" } ], "panel": null, "scores": [ { "by": 5, "edge": "openai-speech-to-text", "inworld-stt": 60, "key": "reliability", "name": "Reliability", "openai-speech-to-text": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 35, "edge": "openai-speech-to-text", "inworld-stt": 54, "key": "schema", "name": "Schema \u0026 documentation", "openai-speech-to-text": 89, "weight": 13 }, { "by": 22, "edge": "openai-speech-to-text", "inworld-stt": 56, "key": "ergonomics", "name": "Agent ergonomics", "openai-speech-to-text": 78, "weight": 13 }, { "by": 34, "edge": "openai-speech-to-text", "inworld-stt": 63, "key": "security", "name": "Security \u0026 auth", "openai-speech-to-text": 97, "weight": 14 }, { "by": 10, "edge": "inworld-stt", "inworld-stt": 40, "key": "payments", "name": "Payments \u0026 pricing", "openai-speech-to-text": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "openai-speech-to-text", "inworld-stt": 41, "key": "maintenance", "name": "Maintenance \u0026 community", "openai-speech-to-text": 71, "weight": 7 }, { "by": 30, "edge": "openai-speech-to-text", "inworld-stt": 60, "key": "transparency", "name": "Transparency \u0026 trust", "openai-speech-to-text": 90, "weight": 7 } ], "summary": "OpenAI Speech to Text scores 75 (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.10 to $0.15", "b": "$0.27 to $1.02", "cheaper": "inworld-stt", "task": "Transcribe a one-hour meeting", "what": "60 minutes of recorded audio" } ], "tutorials": [], "verdicts": { "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.", "openai-speech-to-text": "`gpt-transcribe` costs $0.0045 an audio minute, and the audio endpoints keep no abuse-monitoring logs or application state. Speaker labels, word timestamps and subtitles exist only on `whisper-1` and `gpt-4o-transcribe-diarize`, which shut down on 26 February 2027 with no replacement named for those functions." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text", "json": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.min.md" }, "markdown": "OpenAI Speech to Text scores 75 (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- Inworld STT: grade C, 54.7/100, rank #895 of 1486. Markdown https://www.anchorterminal.com/tools/inworld-stt.md · JSON https://www.anchorterminal.com/api/v1/tools/inworld-stt.json\n- OpenAI Speech to Text: grade BB, 75/100, rank #74 of 1486. Markdown https://www.anchorterminal.com/tools/openai-speech-to-text.md · JSON https://www.anchorterminal.com/api/v1/tools/openai-speech-to-text.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### 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\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No OpenAPI or other machine-readable contract\n\n### OpenAI Speech to Text (BB)\n\nGood for: Suited to plain transcription of recorded files at a low price a minute and to teams already holding an OpenAI key.\n\nAhead on:\n- Reliability, 65 against 60\n- Schema \u0026 documentation, 89 against 54\n- Agent ergonomics, 78 against 56\n- Security \u0026 auth, 97 against 63\n- Maintenance \u0026 community, 71 against 41\n- Transparency \u0026 trust, 90 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: `whisper-1`, `gpt-4o-transcribe`, `gpt-4o-mini-transcribe`, `gpt-4o-transcribe-diarize` and `/v1/audio/translations` shut down on 26 February 2027\n\n\n## Why the edge\n\n### Schema \u0026 documentation: OpenAI Speech to Text +35\n\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- OpenAI Speech to Text (89): Model reading. The public OpenAPI 3.1 document in openai/openai-openapi (version 2.3.0, last committed 31 October) covers `/audio/transcriptions` and `/audio/translations` and names `gpt-transcribe` (25). llms.txt and a Markdown twin of every docs page (10). The transcription overview says which model to use for files, live audio, speaker labels, timestamps and translation, and the file guide now opens by recommending `gpt-transcribe` and saying the specialised examples use deprecated models (18 of 20). `response_format`, `timestamp_granularities` and `model` are enums in the document. `language` is a plain string, and which formats each model accepts is stated in prose only (12 of 15). Examples in seven languages and curl, and an error codes page with a cause and fix for each. The Markdown twin of the endpoint reference now lists the body parameters, including `languages` and `keywords` for `gpt-transcribe`, but its first example still names the deprecated `gpt-4o-transcribe`, and the guide lists seven input formats where the document lists nine (12 of 15, was 11). A dated changelog and deprecations page. `gpt-transcribe` has one alias and no dated snapshot to pin (12 of 15). 25 + 10 + 18 + 12 + 12 + 12 = 89.\n\n### Security \u0026 auth: OpenAI Speech to Text +34\n\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- OpenAI Speech to Text (97): Model reading, on the lines the OpenAI API and Decisions API listings use. Project keys with permissions per key, service-account keys through the Administration API and workload identity federation, per the Decisions API listing's read of 8 October. The access-control guide, re-read on 1 November, puts audio under one Model capabilities permission with chat completions, embeddings and images, so a restricted key can't be limited to the audio endpoints alone (27 of 30, as the Decisions API listing, was 26). The data controls page says API data isn't used for training unless the customer opts in (20). Both audio endpoints are listed with no abuse-monitoring retention, no application state and Zero Data Retention eligibility, re-read on 1 November (15). The Admin API has an audit log endpoint, and the OpenAPI document has `GET /organization/usage/audio_transcriptions` grouped by project, API key or model, the per-key usage view both other OpenAI listings got 15 for (15, was 13). security.txt, re-read on 1 November, is PGP-signed, names a Bugcrowd programme and a coordinated disclosure policy and has no Expires field. trust.openai.com, read on 1 November, names SOC 2 Type 2 and ISO/IEC 27001, 27017, 27018 and 27701 (20, was 12 when no trust centre was read, the award both other OpenAI listings carry). 27 + 20 + 15 + 15 + 20 = 97.\n\n### Maintenance \u0026 community: OpenAI Speech to Text +30\n\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- OpenAI Speech to Text (71): Model reading. The last dated change to transcription is still the deprecation notice of 26 August 2026, 67 days before 1 November, after the release of `gpt-transcribe` and `gpt-live-transcribe` on 28 July (20 of 30). The deprecations page promises at least six months' notice for generally available models, and the four transcription models got six months to the day. On 14 October GA GPT-4 series models got 92 days with no reason stated, so the policy reads as a minimum of two to three months in practice, as the OpenAI API and Decisions API listings read it (8 of 12, was 12). Four of the five file transcription models were deprecated within a month of their replacements shipping, and the replacements don't cover diarisation, timestamps or subtitles (2 of 8). The dated changelog has two transcription entries in 90 days among dozens for the API (13 of 15). Python SDK replies were not sampled (5 of 10). Python SDK v3.42.0 was tagged on 31 October 2026, with v3.41.0 on 28 October and v3.40.0 on 27 October (15). CI, CodeQL and a breaking-change check run in the repository (8 of 10). 20 + 8 + 2 + 13 + 5 + 15 + 8 = 71.\n\n### Transparency \u0026 trust: OpenAI Speech to Text +30\n\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- OpenAI Speech to Text (90): The hosted models are closed with clear terms, the Python SDK Apache-2.0 and the OpenAPI document MIT, per the OpenAI API listing's check of the services agreement. openai.com answered the services agreement with 403 again on 1 November (15, was 12). The data controls page, re-read on 1 November, lists both audio endpoints with no training, no abuse-monitoring retention, no application state and Zero Data Retention eligibility. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (30 of 30, was 28). A deprecations page with notice periods by model class, dated shutdowns and replacements, including `/v1/audio/translations` to `v1/realtime/translations` (20). Data residency is documented by region and endpoint, with the audio endpoints in every listed region for storage and in the United States and Europe for processing. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (20 of 20, was 16). 15 + 30 + 20 + 20 = 85.\n\n### Agent ergonomics: OpenAI Speech to Text +22\n\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- OpenAI Speech to Text (78): API reading, as for the other speech-to-text listings. The default `json` response is the text, detected languages and usage, `text` returns a bare string, and segments, words and speaker labels come only when asked for on the models that have them (20 of 25). There is no transcript store to page through. Files stop at 25 MB, the caller splits longer audio, and the `gpt-transcribe` model page marks the Batch API as not supported (10 of 20). Errors carry `message`, `type`, `param` and `code`, and the error codes page gives a fix for each status (18 of 20). The call is stateless and safe to retry, and the Python SDK retries 408, 409, 429 and 5xx twice by default. No idempotency key applies to this endpoint (15 of 20). `file` and `model` are the only required fields, with guide examples for JavaScript, Python, Go, Java, C# and Ruby SDKs and a CLI (15).\n\n### Payments \u0026 pricing: Inworld STT +10\n\n- Inworld STT (40): No x402, MPP or L402 (0). Per-hour prices for every plan published without a login (20). On-Demand includes up to 400 minutes of STT and lists no payment method, while async jobs need one (20). A person signs up in the Portal or through `inworld login` in a browser before a key exists (0). Total 40.\n- OpenAI Speech to Text (30): No x402, MPP or L402 on the pricing page, re-read on 1 November (0). $0.0045 an audio minute for `gpt-transcribe`, $0.017 for `gpt-live-transcribe` and $0.006 for `whisper-1` on the public pricing page (20). The rate limits guide lists a Free tier capped at $100 a month in allowed countries, while the `gpt-transcribe` model page's rate-limit table starts at Build, which needs $5 of credit. Half, the reading both other OpenAI listings use for the same pages (10, was 0). A person signs up in a browser and creates the key in the console (0). 0 + 20 + 10 + 0 = 30.\n\n## Score by category\n\n| Category | Weight | Inworld STT | OpenAI Speech to Text | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 65 | OpenAI Speech to Text +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 89 | OpenAI Speech to Text +35 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 78 | OpenAI Speech to Text +22 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 97 | OpenAI Speech to Text +34 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Inworld STT +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 41 | 71 | OpenAI Speech to Text +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 90 | OpenAI Speech to Text +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.7 · C** | **75 · BB** | |\n\n## Facts side by side\n\n| Fact | Inworld STT | OpenAI Speech to Text |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | Inworld AI | OpenAI |\n| Hosted endpoint | no (local only) | `https://api.openai.com/v1` |\n| Transports | HTTP, websocket | HTTP, websocket |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for speech-to-text | $0.0017 per minute of audio | not published |\n| x402 | no | no |\n| Licence | none | Proprietary hosted service. The service terms were not read (see open questions). The Python SDK is Apache-2.0 and the OpenAPI document is MIT |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-29 | 2026-08-26 |\n| Terms last updated | 2025-06-11 | couldn't be read |\n| Privacy policy last updated | 2026-01-18 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | none | 32k stars |\n| Agent reviews | none | 3.3/5 (4) |\n\n## What the same task costs\n\n| Task | Inworld STT | OpenAI Speech to Text |\n| --- | --- | --- |\n| Transcribe a one-hour meeting | $0.10 to $0.15 | $0.27 to $1.02 |\n\n## How the scores have moved\n\n### Inworld STT\n\nNo score change since it was listed.\n\n### OpenAI Speech to Text\n\n- +2.4 on 1 November 2026: product, new evidence, correction\n- +0.2 on 27 October 2026: checklist\n\n## Verdicts\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**OpenAI Speech to Text.** `gpt-transcribe` costs $0.0045 an audio minute, and the audio endpoints keep no abuse-monitoring logs or application state. Speaker labels, word timestamps and subtitles exist only on `whisper-1` and `gpt-4o-transcribe-diarize`, which shut down on 26 February 2027 with no replacement named for those functions.\n\n## Before you call either\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### OpenAI Speech to Text\n\n1. Send `gpt-transcribe` to `POST /v1/audio/transcriptions` for recorded files. Use `languages` (a list), not `language`, and never send both.\n2. Keep each upload at 25 MB or less. Split longer audio between sentences and pass the previous chunk's text in `prompt`.\n3. For speaker labels send `gpt-4o-transcribe-diarize` with `response_format=diarized_json` and `chunking_strategy=auto` for audio over 30 seconds. Plan for its shutdown on 26 February 2027.\n4. Word timestamps, `srt` and `vtt` need `whisper-1`, which cannot stream and shuts down on 26 February 2027. Move English translation to `v1/realtime/translations` before then.\n5. On 429 or 503 wait at least `Retry-After` when present, then back off with jitter. Do not retry `credit_balance_exhausted` or spend-limit errors.\n\n## Questions\n\n### Which is better for AI agents, Inworld STT or OpenAI Speech to Text?\n\nOpenAI Speech to Text scores 75 (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 Inworld STT and OpenAI Speech to Text need an API key?\n\nBoth need an API key.\n\n### Can an agent call Inworld STT and OpenAI Speech to Text without installing anything?\n\nNo hosted endpoint is listed for Inworld STT. OpenAI Speech to Text has a hosted endpoint at https://api.openai.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.json, and with the fewest tokens: https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"inworld-stt\", \"b\": \"openai-speech-to-text\"}`. From a terminal: `anchor compare inworld-stt openai-speech-to-text`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/inworld-stt.json and https://www.anchorterminal.com/api/v1/tools/openai-speech-to-text.json\n\n## Other comparisons with Inworld STT or OpenAI Speech to Text\n\n- [Amazon Transcribe vs Inworld STT](https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.md)\n- [Amazon Transcribe vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/amazon-transcribe-vs-openai-speech-to-text.md)\n- [AssemblyAI Speech-to-Text (Universal) vs Inworld STT](https://www.anchorterminal.com/compare/assemblyai-stt-vs-inworld-stt.md)\n- [AssemblyAI Speech-to-Text (Universal) vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/assemblyai-stt-vs-openai-speech-to-text.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- [Azure AI Speech speech-to-text vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-openai-speech-to-text.md)\n- [Cartesia Ink vs Inworld STT](https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-inworld-stt.md)\n- [Cartesia Ink vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-openai-speech-to-text.md)\n- [Deepgram Speech-to-Text (Nova-3, Flux) vs Inworld STT](https://www.anchorterminal.com/compare/deepgram-stt-vs-inworld-stt.md)\n- [Deepgram Speech-to-Text (Nova-3, Flux) vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/deepgram-stt-vs-openai-speech-to-text.md)\n- [ElevenLabs Scribe Speech to Text API vs Inworld STT](https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-inworld-stt.md)\n- [ElevenLabs Scribe Speech to Text API vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-openai-speech-to-text.md)\n- [Giggy Speech to Text vs Inworld STT](https://www.anchorterminal.com/compare/giggy-stt-vs-inworld-stt.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- [Gladia Speech-to-Text API + MCP vs Inworld STT](https://www.anchorterminal.com/compare/gladia-stt-vs-inworld-stt.md)\n- [Gladia Speech-to-Text API + MCP vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/gladia-stt-vs-openai-speech-to-text.md)\n- [Google Cloud Speech-to-Text vs Inworld STT](https://www.anchorterminal.com/compare/google-speech-to-text-vs-inworld-stt.md)\n- [Google Cloud Speech-to-Text vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/google-speech-to-text-vs-openai-speech-to-text.md)\n- [Groq Speech-to-Text vs Inworld STT](https://www.anchorterminal.com/compare/groq-speech-to-text-vs-inworld-stt.md)\n- [Groq Speech-to-Text vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/groq-speech-to-text-vs-openai-speech-to-text.md)\n- [IBM Watson Speech to Text vs Inworld STT](https://www.anchorterminal.com/compare/ibm-watson-stt-vs-inworld-stt.md)\n- [IBM Watson Speech to Text vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/ibm-watson-stt-vs-openai-speech-to-text.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 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- [MiniMax Speech-to-Text vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/minimax-stt-vs-openai-speech-to-text.md)\n- [Mistral Voxtral Transcribe vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-openai-speech-to-text.md)\n- [OpenAI Speech to Text vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/openai-speech-to-text-vs-rev-ai-stt.md)\n- [OpenAI Speech to Text vs Smallest.ai Pulse STT](https://www.anchorterminal.com/compare/openai-speech-to-text-vs-smallest-pulse-stt.md)\n- [OpenAI Speech to Text vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/openai-speech-to-text-vs-soniox-stt.md)\n- [OpenAI Speech to Text vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/openai-speech-to-text-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": "Inworld STT vs OpenAI Speech to Text", "url": "" } ], "description": "OpenAI Speech to Text scores 75 (BB) to Inworld STT's 54.7 (C) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Inworld STT C 54.7", "OpenAI Speech to Text BB 75", "scores" ], "h1": "Inworld STT vs OpenAI Speech to Text", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/inworld-stt-vs-openai-speech-to-text", "published": "2026-10-01", "section": "tools", "title": "Inworld STT vs OpenAI Speech to Text for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text" }, "tokens": { "markdown": 6000, "slim": 3580 }, "version": 1 }