{ "data": { "a": { "slug": "azure-speech-to-text", "name": "Azure AI Speech speech-to-text", "vendor": "Microsoft", "vendorUrl": "https://azure.microsoft.com/en-us/products/ai-services/speech-to-text", "kind": "model", "category": "speech-to-text", "summary": "Azure's speech-to-text service for transcribing audio.", "url": "https://www.anchorterminal.com/tools/azure-speech-to-text", "markdownUrl": "https://www.anchorterminal.com/tools/azure-speech-to-text.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-speech-to-text.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-speech-to-text.json", "dns": "azure-speech-to-text.grade.anchorterminal.com", "repo": "https://github.com/Azure-Samples/cognitive-services-speech-sdk", "license": "MIT (samples), SDK under Microsoft's own licence", "transports": [ "http" ], "remoteUrl": "https://eastus.api.cognitive.microsoft.com/speechtotext", "packages": [ { "registry": "pypi", "name": "azure-cognitiveservices-speech" }, { "registry": "npm", "name": "microsoft-cognitiveservices-speech-sdk" } ], "auth": "mixed", "authNotes": "`Ocp-Apim-Subscription-Key` header with a Speech resource key, or a Microsoft Entra ID bearer token (Microsoft's recommended keyless option). Endpoints are per region or per resource. The MAI-Transcribe-2-Streaming Realtime WebSocket also takes the key as an `api-key` header or query-string parameter.", "pricing": "freemium", "pricingNotes": "Free F0 tier with 5 audio hours a month of real-time. Pay as you go in East US is $1 an hour real-time, $0.36 fast transcription, $0.18 batch, $1.20 custom real-time. Diarisation and continuous language ID in real time add $0.30 an hour each. MAI-Transcribe-2 is $0.10 an hour until 2026-12-31. MAI-Transcribe-2-Streaming is $0.54 an hour until the end of 2026 per Microsoft AI's launch post (https://microsoft.ai/news/our-first-streaming-transcription-model/), with no Azure meter found on 2026-10-05, 2026-10-17 or 2026-11-01. Commitment tiers from $1,600 a month for 2,000 hours (https://azure.microsoft.com/en-us/pricing/details/speech/).", "priceSummary": "Freemium", "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": 3450, "npmWeekly": 475621, "pypiWeekly": 1032532, "asOf": "2026-09-30" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/speech-to-text", "openapi": "https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/cognitiveservices/data-plane/SpeechToText/stable/2025-10-15/speechtotext.json", "capabilities": [ "speech.stt", "speech.streaming", "speech.batch", "speech.diarisation", "speech.languages", "speech.translation" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "python", "typescript", "enterprise", "streaming", "batch", "async-jobs", "webhooks" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 75.1, "grade": "BB", "agentReady": true, "rank": 71, "ranked": true, "rankOf": 1486, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 90, "schema": 80, "security": 85, "transparency": 86 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Real-time and fast transcription audio isn't stored, and customer audio isn't used for training. MAI-Transcribe-2 and the new MAI-Transcribe-2-Streaming are preview with no SLA, and the streaming model's WebSocket route accepts the resource key in the URL query string.", "bestFor": "Teams on Azure who need several modes (real time, synchronous files, cheap batch, custom models) under one resource, or strict default data handling.", "strengths": [ "Real-time and fast transcription audio isn't stored, and customer audio isn't used for training", "Fast transcription returns files up to 5 hours and 500 MB in one synchronous call", "Batch at $0.18 an hour, and a free F0 tier with 5 real-time hours a month", "429 guidance with a concrete backoff pattern of 1, 2, 4 and 4 minutes", "Keys or Entra ID tokens with role-based access" ], "weaknesses": [ "MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026", "The MAI-Transcribe-2-Streaming WebSocket docs allow the resource key as an `api-key` query parameter", "REST API v3.0 and the v3.2 previews were retired on 2026-03-31, and older samples still target them", "No llms.txt, and the pricing page needs JavaScript", "An Azure subscription needs a card, even for the F0 tier" ], "agentNotes": [ "Use fast transcription (`transcriptions:transcribe`) for files under 5 hours and 500 MB, and batch for bulk jobs with `timeToLive` set", "Pin `api-version=2025-10-15`. v3.0 and the v3.2 previews are retired", "On a 429, back off 1, 2, 4 then 4 minutes. It usually means autoscaling, not a quota", "For MAI-Transcribe-2-Streaming, use Speech SDK 1.52 or later with the `/speech/universal/v2` endpoint, or send the key in the `api-key` header, never the query string", "Don't budget on MAI-Transcribe-2 at $0.10 or MAI-Transcribe-2-Streaming at $0.54 an hour after 2026-12-31" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "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.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 90, "schema": 80, "security": 85, "transparency": 80 }, "provenanceScore": 91, "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 azure-cognitiveservices-speech # or: npm i microsoft-cognitiveservices-speech-sdk", "http": "curl -X POST \"https://$AZURE_SPEECH_RESOURCE.cognitiveservices.azure.com/speechtotext/transcriptions:transcribe?api-version=2025-10-15\" \\\n -H \"Ocp-Apim-Subscription-Key: $AZURE_SPEECH_KEY\" \\\n -F \"audio=@call.wav\" -F 'definition={\"locales\":[\"en-US\"]}'" }, "letme": { "capability": "https://letme.dev/speech.stt", "tool": "https://letme.dev/azure-speech-to-text" }, "sameCompany": [ "azure-openai", "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "bing-grounding", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "voice", "unitPrices": [ { "item": "Real-time standard", "unit": "audio-minute", "usd": 0.0167, "note": "$1 an hour, East US" }, { "item": "Fast transcription", "unit": "audio-minute", "usd": 0.006, "note": "$0.36 an hour" }, { "item": "Batch standard", "unit": "audio-minute", "usd": 0.003, "note": "$0.18 an hour" }, { "item": "MAI-Transcribe-2 (preview)", "unit": "audio-minute", "usd": 0.00167, "note": "$0.10 an hour, promotional until 2026-12-31" }, { "item": "MAI-Transcribe-2-Streaming (preview)", "unit": "audio-minute", "usd": 0.009, "note": "$0.54 an hour, introductory until the end of 2026, per Microsoft AI's launch post. No Azure meter found on 2026-11-01" }, { "item": "Custom real-time", "unit": "audio-minute", "usd": 0.02, "note": "$1.20 an hour, plus endpoint hosting" }, { "item": "Real-time add-on (diarisation or language ID)", "unit": "audio-minute", "usd": 0.005, "note": "$0.30 an hour per feature" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Endpoints are on speech.microsoft.com, api.cognitive.microsoft.com and cognitiveservices.azure.com. microsoft.com publishes a security.txt, but it passed its Expires date on 2026-09-23 and was still expired on 2026-11-01.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/releasenotes", "securityTxt": "expired", "checked": "2026-11-01", "score": 91 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "unknown", "freeTier": true, "minutes": 10, "credential": "api-key", "hosting": [ "global", "US", "EU", "UK" ], "euResidency": "yes", "trainsOnData": "unknown", "zeroRetention": "yes", "certifications": [ "ISO 27001", "PCI DSS", "CSA STAR", "FedRAMP", "GDPR" ], "dpa": true, "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-speech-to-text.json", "live": { "slug": "azure-speech-to-text", "probe": { "target": "https://eastus.api.cognitive.microsoft.com/speechtotext", "method": "get", "lastAt": "2026-11-07T18:20:12.145545285Z", "lastOk": true, "lastStatus": 404, "lastMs": 509, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 352, "p95ms24h": 449, "samples24h": 239, "samples30d": 7910, "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": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://azure.status.microsoft/en-us/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T10:02:53.355601307Z" }, "versions": [ { "registry": "github", "name": "Azure-Samples/cognitive-services-speech-sdk", "version": "ingestion-v2.1.13", "released": "2026-07-10", "seenAt": "2026-11-06T23:09:34.001543505Z" }, { "registry": "npm", "name": "microsoft-cognitiveservices-speech-sdk", "version": "1.53.0", "seenAt": "2026-11-06T23:09:33.76385883Z" }, { "registry": "pypi", "name": "azure-cognitiveservices-speech", "version": "1.53.0", "released": "2026-10-21", "seenAt": "2026-11-06T23:09:33.575682302Z" } ], "githubStars": 3457, "npmWeekly": 666362, "pypiWeekly": 623310, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "domain": { "domain": "microsoft.com", "registered": "1991-05-02", "source": "https://rdap.verisign.com/com/v1/domain/microsoft.com", "checkedAt": "2026-11-01T14:14:19.336136409Z" }, "pages": [ { "url": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/releasenotes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:12:51.583411094Z", "changedAt": "2026-11-03T07:52:59.892662471Z", "fingerprint": "962a010ed30d" }, { "url": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/mai-transcribe", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:12:49.805750863Z", "changedAt": "2026-11-07T14:12:49.805750863Z", "fingerprint": "918183c3164f" }, { "url": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/rest-speech-to-text", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:12:53.894333324Z", "changedAt": "2026-10-20T00:00:55.457010036Z", "fingerprint": "be303dc8912d" }, { "url": "https://azure.microsoft.com/en-us/pricing/details/speech/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T13:59:55.654839095Z", "changedAt": "2026-10-30T05:32:17.448922931Z", "fingerprint": "bb9c72ab8aae" }, { "url": "https://privacy.microsoft.com/en-us/privacystatement", "kind": "privacy", "status": 200, "checkedAt": "2026-10-01T13:14:57.860748137Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "07484a06f35c" }, { "url": "https://www.microsoft.com/licensing/terms/", "kind": "terms", "status": 502, "checkedAt": "2026-10-01T13:17:52.720054167Z", "changedAt": "0001-01-01T00:00:00Z" } ], "github": { "repo": "azure-samples/cognitive-services-speech-sdk", "checkedAt": "2026-11-02T08:33:46.314203025Z", "stars": 3457, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T08:28:26Z", "openIssues": 2, "openPRs": 44, "issuesOpened90d": 22, "issuesClosed90d": 24, "prsMerged90d": 12, "ci": { "branch": "master", "runs": 4, "success": 1, "failure": 3, "other": 0, "latest": "failure", "latestAt": "2026-10-23T22:25:20Z" }, "replies": { "sampled": 25, "unanswered": 1, "medianDays": 1 } }, "updatedAt": "2026-11-07T18:20:12.145545285Z" } }, "answer": "Azure AI Speech speech-to-text scores 75.1 (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": 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" } }, "edges": [ { "by": 39, "category": "maintenance", "leads": "azure-speech-to-text", "name": "Maintenance \u0026 community", "reasons": { "a": "Speech SDK 1.53.0 is the latest on npm on 1 November (the JavaScript SDK's v1.53.0 tag is dated 21 October, and the samples repository moved to 1.53.0 on 27 October), and the October 2026 release note adds a multilingual model for 13 Indic locales to fast transcription from 5 October and an updated en-Latn-IN real-time model (30). Release notes for August, September and October 2026, and SDK 1.52.0 (September) and 1.53.0 (October) (20). Public release notes, a GitHub samples repository and Microsoft Q\u0026A (10). Speech SDK current in eight languages (15). The SDK itself is a closed binary, so we can't see its CI (5). 30 + 20 + 10 + 15 + 5 = 80.", "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": 80, "b": 41 } }, { "by": 30, "category": "reliability", "leads": "azure-speech-to-text", "name": "Reliability", "reasons": { "a": "Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August, so the 23 July 2026 West US review (Azure Speech in Foundry Tools among services with connectivity failures from 14:44 to 19:41 UTC, counted as one major outage on 17 October) has left it. Two reviews remain on 1 November. The 29 September incident (intermittent 500 and 503 errors for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC) is one region and partial, so minor. The 30 September to 1 October gateway review (20:30 to 02:15 UTC) names networking services, not Speech. Nothing newer is listed. Minor incidents only (20). Limits published with numbers, 100 concurrent real-time requests and 600 fast or batch requests a minute by default, on the quotas page updated 23 October and re-read on 1 November (15). 429 documented as usually meaning autoscaling in progress, with retry logic advised and a 1-2-4-4 minute pattern for ramping load. Fast transcription is synchronous, so a retry doesn't duplicate a job (15). Covered by Microsoft's online services SLA, per the 1 October check (10). Fast transcription, batch and real time are GA. MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, which doesn't change this line because the surfaces graded here are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.", "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": 90, "b": 60 } }, { "by": 26, "category": "schema", "leads": "azure-speech-to-text", "name": "Schema \u0026 documentation", "reasons": { "a": "The speech-to-text OpenAPI document for GA version 2025-10-15 is in Microsoft's public REST API specs, re-read on 1 November with 67 operations (25). No llms.txt found (0). Operation descriptions state purpose, and the speech-to-text overview says when to use real time, fast or batch (15). Batch request bodies are typed with enums and required fields, but fast transcription takes its options as a JSON string in the multipart `definition` field, documented but untyped on the wire (10). The REST reference carries examples and error responses per operation, per the 5 October check, not re-read on 1 November (15). Dated `api-version` values (current GA 2025-10-15, on the versions page updated 19 October) and monthly release notes (15). MAI-Transcribe-2-Streaming's WebSocket events are documented in prose and examples only, with no machine-readable contract, which leaves the graded REST surface unchanged. 25 + 0 + 15 + 10 + 15 + 15 = 80.", "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": 80, "b": 54 } }, { "by": 26, "category": "transparency", "leads": "azure-speech-to-text", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Microsoft's product terms, with an MIT samples repository (15). The data privacy page, the privacy statement and the product terms agree on no storage for real time, retention until deletion for batch and no training (25). The data privacy page, re-read on 1 November and still dated 26 August, doesn't name the MAI streaming model. Dated retirements, REST API v3.0 and the v3.2 previews on 2026-03-31 and MAI-Transcribe-1 deprecated on 2026-08-20, under Microsoft's published lifecycle policy. The versions page now says 2024-05-15-preview will be retired on a date to be announced (20). Regions chosen per resource and a public sub-processor list (20). 15 + 25 + 20 + 20 = 80.", "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": 86, "b": 60 } }, { "by": 22, "category": "security", "leads": "azure-speech-to-text", "name": "Security \u0026 auth", "reasons": { "a": "Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access, which Microsoft recommends (30). Less 10 because the Realtime route for MAI-Transcribe-2-Streaming, added on 1 October 2026, documents an `api-key` query-string parameter on the WebSocket URI, using the same resource key, still so on the page updated 7 October and re-read on 1 November. The speech-to-text REST, fast, batch and Speech SDK docs take the key in a header only, so the deduction is applied once. SAS URLs for batch audio are scoped tokens for the customer's own storage, not the Speech credential, and aren't deducted (20). Microsoft doesn't use customer audio to train its models, per the 1 October check, not re-read since (20). Real-time and fast transcription audio isn't stored, and batch output stays until deleted or `timeToLive` expires, per the data privacy page updated 2026-08-26 and re-read on 1 November (15). Azure Monitor and the activity log record resource actions, though we didn't confirm per-request Speech logging (10). The MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports, and public advisories. An MSRC search on 1 November found no CVE for the Azure Speech service (the Speech entries are Windows Speech components and Chromium). The microsoft.com security.txt passed its Expires date on 2026-09-23 and was still expired on 1 November, which we note without deducting, as on 5 and 17 October (20). 20 + 20 + 15 + 10 + 20 = 85.", "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": 85, "b": 63 } }, { "by": 20, "category": "payments", "leads": "inworld-stt", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-hour prices published without a login, though the page needs JavaScript and the Retail Prices API is the readable source (20). The F0 tier gives 5 real-time hours a month but an Azure subscription needs a card (0). A person signs up in a browser (0). MAI-Transcribe-2-Streaming's introductory $0.54 an hour appears only in Microsoft AI's launch post. No Azure meter for it was found in the Retail Prices API on 5 October, 17 October or 1 November, which doesn't move this line because the other per-hour prices are published. The East US meters for real time ($1), fast ($0.36) and batch ($0.18) an hour were unchanged on 1 November. 0 + 20 + 0 + 0 = 20.", "b": "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." }, "scores": { "a": 20, "b": 40 } } ], "facts": [ { "a": "Model API", "b": "Model API", "name": "Kind" }, { "a": "Microsoft", "b": "Inworld AI", "name": "Vendor" }, { "a": "https://eastus.api.cognitive.microsoft.com/speechtotext", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, websocket", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "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": "MIT (samples), SDK under Microsoft's own licence", "b": "none", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-21", "b": "2026-10-29", "name": "Last release" }, { "a": "couldn't be read", "b": "2025-06-11", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-01-18", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3.5k stars, 476k npm/wk, 1M PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.3/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Azure AI Speech speech-to-text scores 75.1 (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, Azure AI Speech speech-to-text or Inworld STT?" }, { "answer": "Azure AI Speech speech-to-text takes an API key or an OAuth sign-in. Inworld STT needs an API key.", "question": "Do Azure AI Speech speech-to-text and Inworld STT need an API key?" }, { "answer": "Azure AI Speech speech-to-text has a hosted endpoint at https://eastus.api.cognitive.microsoft.com/speechtotext. No hosted endpoint is listed for Inworld STT.", "question": "Can an agent call Azure AI Speech speech-to-text and Inworld STT without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 90 against 60", "Schema \u0026 documentation, 80 against 54", "Agent ergonomics, 75 against 56", "Security \u0026 auth, 85 against 63", "Maintenance \u0026 community, 80 against 41", "Transparency \u0026 trust, 86 against 60" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "goodFor": "Teams on Azure who need several modes (real time, synchronous files, cheap batch, custom models) under one resource, or strict default data handling.", "slug": "azure-speech-to-text", "watchFor": "MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 20" ], "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" } ], "history": { "azure-speech-to-text": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": 2, "from": 73.1, "fromGrade": "BB", "to": 75.1, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 73, "fromGrade": "BB", "to": 73.1, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 73.3, "fromGrade": "BB", "to": 73, "toGrade": "BB" } ], "inworld-stt": null }, "job": { "capability": "speech.stt", "name": "Speech-to-text" }, "others": [ { "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-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/assemblyai-stt-vs-azure-speech-to-text.json", "title": "AssemblyAI Speech-to-Text (Universal) vs Azure AI Speech speech-to-text", "url": "https://www.anchorterminal.com/compare/assemblyai-stt-vs-azure-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/azure-speech-to-text-vs-cartesia-ink-stt.json", "title": "Azure AI Speech speech-to-text vs Cartesia Ink", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-cartesia-ink-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-deepgram-stt.json", "title": "Azure AI Speech speech-to-text vs Deepgram Speech-to-Text (Nova-3, Flux)", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-deepgram-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-elevenlabs-scribe.json", "title": "Azure AI Speech speech-to-text vs ElevenLabs Scribe Speech to Text API", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-elevenlabs-scribe" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-giggy-stt.json", "title": "Azure AI Speech speech-to-text vs Giggy Speech to Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-giggy-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-gladia-stt.json", "title": "Azure AI Speech speech-to-text vs Gladia Speech-to-Text API + MCP", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-gladia-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-google-speech-to-text.json", "title": "Azure AI Speech speech-to-text vs Google Cloud Speech-to-Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-google-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-groq-speech-to-text.json", "title": "Azure AI Speech speech-to-text vs Groq Speech-to-Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-groq-speech-to-text" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-ibm-watson-stt.json", "title": "Azure AI Speech speech-to-text vs IBM Watson Speech to Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-ibm-watson-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-minimax-stt.json", "title": "Azure AI Speech speech-to-text vs MiniMax Speech-to-Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-minimax-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-mistral-voxtral-transcribe.json", "title": "Azure AI Speech speech-to-text vs Mistral Voxtral Transcribe", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-mistral-voxtral-transcribe" }, { "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/azure-speech-to-text-vs-rev-ai-stt.json", "title": "Azure AI Speech speech-to-text vs Rev AI Speech-to-Text API", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-rev-ai-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-smallest-pulse-stt.json", "title": "Azure AI Speech speech-to-text vs Smallest.ai Pulse STT", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-smallest-pulse-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-soniox-stt.json", "title": "Azure AI Speech speech-to-text vs Soniox Speech-to-Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-soniox-stt" }, { "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-speechmatics-stt.json", "title": "Azure AI Speech speech-to-text vs Speechmatics Speech-to-Text", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-speechmatics-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": [ { "azure-speech-to-text": 90, "by": 30, "edge": "azure-speech-to-text", "inworld-stt": 60, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-speech-to-text": 80, "by": 26, "edge": "azure-speech-to-text", "inworld-stt": 54, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "azure-speech-to-text": 75, "by": 19, "edge": "azure-speech-to-text", "inworld-stt": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "azure-speech-to-text": 85, "by": 22, "edge": "azure-speech-to-text", "inworld-stt": 63, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "azure-speech-to-text": 20, "by": 20, "edge": "inworld-stt", "inworld-stt": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-speech-to-text": 80, "by": 39, "edge": "azure-speech-to-text", "inworld-stt": 41, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "azure-speech-to-text": 86, "by": 26, "edge": "azure-speech-to-text", "inworld-stt": 60, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Azure AI Speech speech-to-text scores 75.1 (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 $1.20", "b": "$0.10 to $0.15", "cheaper": "", "task": "Transcribe a one-hour meeting", "what": "60 minutes of recorded audio" } ], "tutorials": [], "verdicts": { "azure-speech-to-text": "Real-time and fast transcription audio isn't stored, and customer audio isn't used for training. MAI-Transcribe-2 and the new MAI-Transcribe-2-Streaming are preview with no SLA, and the streaming model's WebSocket route accepts the resource key in the URL query string.", "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/azure-speech-to-text-vs-inworld-stt", "json": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.min.md" }, "markdown": "Azure AI Speech speech-to-text scores 75.1 (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- Azure AI Speech speech-to-text: grade BB, 75.1/100, rank #71 of 1486. Markdown https://www.anchorterminal.com/tools/azure-speech-to-text.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-speech-to-text.json\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- 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### Azure AI Speech speech-to-text (BB)\n\nGood for: Teams on Azure who need several modes (real time, synchronous files, cheap batch, custom models) under one resource, or strict default data handling.\n\nAhead on:\n- Reliability, 90 against 60\n- Schema \u0026 documentation, 80 against 54\n- Agent ergonomics, 75 against 56\n- Security \u0026 auth, 85 against 63\n- Maintenance \u0026 community, 80 against 41\n- Transparency \u0026 trust, 86 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: MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026\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 20\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No OpenAPI or other machine-readable contract\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Azure AI Speech speech-to-text +39\n\n- Azure AI Speech speech-to-text (80): Speech SDK 1.53.0 is the latest on npm on 1 November (the JavaScript SDK's v1.53.0 tag is dated 21 October, and the samples repository moved to 1.53.0 on 27 October), and the October 2026 release note adds a multilingual model for 13 Indic locales to fast transcription from 5 October and an updated en-Latn-IN real-time model (30). Release notes for August, September and October 2026, and SDK 1.52.0 (September) and 1.53.0 (October) (20). Public release notes, a GitHub samples repository and Microsoft Q\u0026A (10). Speech SDK current in eight languages (15). The SDK itself is a closed binary, so we can't see its CI (5). 30 + 20 + 10 + 15 + 5 = 80.\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: Azure AI Speech speech-to-text +30\n\n- Azure AI Speech speech-to-text (90): Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August, so the 23 July 2026 West US review (Azure Speech in Foundry Tools among services with connectivity failures from 14:44 to 19:41 UTC, counted as one major outage on 17 October) has left it. Two reviews remain on 1 November. The 29 September incident (intermittent 500 and 503 errors for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC) is one region and partial, so minor. The 30 September to 1 October gateway review (20:30 to 02:15 UTC) names networking services, not Speech. Nothing newer is listed. Minor incidents only (20). Limits published with numbers, 100 concurrent real-time requests and 600 fast or batch requests a minute by default, on the quotas page updated 23 October and re-read on 1 November (15). 429 documented as usually meaning autoscaling in progress, with retry logic advised and a 1-2-4-4 minute pattern for ramping load. Fast transcription is synchronous, so a retry doesn't duplicate a job (15). Covered by Microsoft's online services SLA, per the 1 October check (10). Fast transcription, batch and real time are GA. MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, which doesn't change this line because the surfaces graded here are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.\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### Schema \u0026 documentation: Azure AI Speech speech-to-text +26\n\n- Azure AI Speech speech-to-text (80): The speech-to-text OpenAPI document for GA version 2025-10-15 is in Microsoft's public REST API specs, re-read on 1 November with 67 operations (25). No llms.txt found (0). Operation descriptions state purpose, and the speech-to-text overview says when to use real time, fast or batch (15). Batch request bodies are typed with enums and required fields, but fast transcription takes its options as a JSON string in the multipart `definition` field, documented but untyped on the wire (10). The REST reference carries examples and error responses per operation, per the 5 October check, not re-read on 1 November (15). Dated `api-version` values (current GA 2025-10-15, on the versions page updated 19 October) and monthly release notes (15). MAI-Transcribe-2-Streaming's WebSocket events are documented in prose and examples only, with no machine-readable contract, which leaves the graded REST surface unchanged. 25 + 0 + 15 + 10 + 15 + 15 = 80.\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: Azure AI Speech speech-to-text +26\n\n- Azure AI Speech speech-to-text (86): Closed service under Microsoft's product terms, with an MIT samples repository (15). The data privacy page, the privacy statement and the product terms agree on no storage for real time, retention until deletion for batch and no training (25). The data privacy page, re-read on 1 November and still dated 26 August, doesn't name the MAI streaming model. Dated retirements, REST API v3.0 and the v3.2 previews on 2026-03-31 and MAI-Transcribe-1 deprecated on 2026-08-20, under Microsoft's published lifecycle policy. The versions page now says 2024-05-15-preview will be retired on a date to be announced (20). Regions chosen per resource and a public sub-processor list (20). 15 + 25 + 20 + 20 = 80.\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### Security \u0026 auth: Azure AI Speech speech-to-text +22\n\n- Azure AI Speech speech-to-text (85): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access, which Microsoft recommends (30). Less 10 because the Realtime route for MAI-Transcribe-2-Streaming, added on 1 October 2026, documents an `api-key` query-string parameter on the WebSocket URI, using the same resource key, still so on the page updated 7 October and re-read on 1 November. The speech-to-text REST, fast, batch and Speech SDK docs take the key in a header only, so the deduction is applied once. SAS URLs for batch audio are scoped tokens for the customer's own storage, not the Speech credential, and aren't deducted (20). Microsoft doesn't use customer audio to train its models, per the 1 October check, not re-read since (20). Real-time and fast transcription audio isn't stored, and batch output stays until deleted or `timeToLive` expires, per the data privacy page updated 2026-08-26 and re-read on 1 November (15). Azure Monitor and the activity log record resource actions, though we didn't confirm per-request Speech logging (10). The MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports, and public advisories. An MSRC search on 1 November found no CVE for the Azure Speech service (the Speech entries are Windows Speech components and Chromium). The microsoft.com security.txt passed its Expires date on 2026-09-23 and was still expired on 1 November, which we note without deducting, as on 5 and 17 October (20). 20 + 20 + 15 + 10 + 20 = 85.\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### Payments \u0026 pricing: Inworld STT +20\n\n- Azure AI Speech speech-to-text (20): No x402, MPP or L402 (0). Per-hour prices published without a login, though the page needs JavaScript and the Retail Prices API is the readable source (20). The F0 tier gives 5 real-time hours a month but an Azure subscription needs a card (0). A person signs up in a browser (0). MAI-Transcribe-2-Streaming's introductory $0.54 an hour appears only in Microsoft AI's launch post. No Azure meter for it was found in the Retail Prices API on 5 October, 17 October or 1 November, which doesn't move this line because the other per-hour prices are published. The East US meters for real time ($1), fast ($0.36) and batch ($0.18) an hour were unchanged on 1 November. 0 + 20 + 0 + 0 = 20.\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\n## Score by category\n\n| Category | Weight | Azure AI Speech speech-to-text | Inworld STT | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 90 | 60 | Azure AI Speech speech-to-text +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 54 | Azure AI Speech speech-to-text +26 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 56 | Azure AI Speech speech-to-text +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 85 | 63 | Azure AI Speech speech-to-text +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Inworld STT +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 41 | Azure AI Speech speech-to-text +39 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 86 | 60 | Azure AI Speech speech-to-text +26 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75.1 · BB** | **54.7 · C** | |\n\n## Facts side by side\n\n| Fact | Azure AI Speech speech-to-text | Inworld STT |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | Microsoft | Inworld AI |\n| Hosted endpoint | `https://eastus.api.cognitive.microsoft.com/speechtotext` | no (local only) |\n| Transports | HTTP | HTTP, websocket |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| Price for speech-to-text | not published | $0.0017 per minute of audio |\n| x402 | no | no |\n| Licence | MIT (samples), SDK under Microsoft's own licence | none |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-21 | 2026-10-29 |\n| Terms last updated | couldn't be read | 2025-06-11 |\n| Privacy policy last updated | 2026-09-01 | 2026-01-18 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 3.5k stars, 476k npm/wk, 1M PyPI/wk | none |\n| Agent reviews | 3.3/5 (8) | none |\n\n## What the same task costs\n\n| Task | Azure AI Speech speech-to-text | Inworld STT |\n| --- | --- | --- |\n| Transcribe a one-hour meeting | $0.10 to $1.20 | $0.10 to $0.15 |\n\n## How the scores have moved\n\n### Azure AI Speech speech-to-text\n\n- +2.0 on 1 November 2026: time\n- +0.1 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n\n### Inworld STT\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Azure AI Speech speech-to-text.** Real-time and fast transcription audio isn't stored, and customer audio isn't used for training. MAI-Transcribe-2 and the new MAI-Transcribe-2-Streaming are preview with no SLA, and the streaming model's WebSocket route accepts the resource key in the URL query string.\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### Azure AI Speech speech-to-text\n\n1. Use fast transcription (`transcriptions:transcribe`) for files under 5 hours and 500 MB, and batch for bulk jobs with `timeToLive` set\n2. Pin `api-version=2025-10-15`. v3.0 and the v3.2 previews are retired\n3. On a 429, back off 1, 2, 4 then 4 minutes. It usually means autoscaling, not a quota\n4. For MAI-Transcribe-2-Streaming, use Speech SDK 1.52 or later with the `/speech/universal/v2` endpoint, or send the key in the `api-key` header, never the query string\n5. Don't budget on MAI-Transcribe-2 at $0.10 or MAI-Transcribe-2-Streaming at $0.54 an hour after 2026-12-31\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, Azure AI Speech speech-to-text or Inworld STT?\n\nAzure AI Speech speech-to-text scores 75.1 (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 Azure AI Speech speech-to-text and Inworld STT need an API key?\n\nAzure AI Speech speech-to-text takes an API key or an OAuth sign-in. Inworld STT needs an API key.\n\n### Can an agent call Azure AI Speech speech-to-text and Inworld STT without installing anything?\n\nAzure AI Speech speech-to-text has a hosted endpoint at https://eastus.api.cognitive.microsoft.com/speechtotext. No hosted endpoint is listed for Inworld STT.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-speech-to-text\", \"b\": \"inworld-stt\"}`. From a terminal: `anchor compare azure-speech-to-text inworld-stt`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-speech-to-text.json and https://www.anchorterminal.com/api/v1/tools/inworld-stt.json\n\n## Other comparisons with Azure AI Speech speech-to-text or Inworld STT\n\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 Inworld STT](https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.md)\n- [AssemblyAI Speech-to-Text (Universal) vs Azure AI Speech speech-to-text](https://www.anchorterminal.com/compare/assemblyai-stt-vs-azure-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- [Azure AI Speech speech-to-text vs Cartesia Ink](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-cartesia-ink-stt.md)\n- [Azure AI Speech speech-to-text vs Deepgram Speech-to-Text (Nova-3, Flux)](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-deepgram-stt.md)\n- [Azure AI Speech speech-to-text vs ElevenLabs Scribe Speech to Text API](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-elevenlabs-scribe.md)\n- [Azure AI Speech speech-to-text vs Giggy Speech to Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-giggy-stt.md)\n- [Azure AI Speech speech-to-text vs Gladia Speech-to-Text API + MCP](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-gladia-stt.md)\n- [Azure AI Speech speech-to-text vs Google Cloud Speech-to-Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-google-speech-to-text.md)\n- [Azure AI Speech speech-to-text vs Groq Speech-to-Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-groq-speech-to-text.md)\n- [Azure AI Speech speech-to-text vs IBM Watson Speech to Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-ibm-watson-stt.md)\n- [Azure AI Speech speech-to-text vs MiniMax Speech-to-Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-minimax-stt.md)\n- [Azure AI Speech speech-to-text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-mistral-voxtral-transcribe.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- [Azure AI Speech speech-to-text vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-rev-ai-stt.md)\n- [Azure AI Speech speech-to-text vs Smallest.ai Pulse STT](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-smallest-pulse-stt.md)\n- [Azure AI Speech speech-to-text vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-soniox-stt.md)\n- [Azure AI Speech speech-to-text vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-speechmatics-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": "Azure AI Speech speech-to-text vs Inworld STT", "url": "" } ], "description": "Azure AI Speech speech-to-text scores 75.1 (BB) to Inworld STT's 54.7 (C) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Azure AI Speech speech-to-text BB 75.1", "Inworld STT C 54.7", "scores" ], "h1": "Azure AI Speech speech-to-text vs Inworld STT", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/azure-speech-to-text-vs-inworld-stt", "published": "2026-10-01", "section": "tools", "title": "Azure AI Speech speech-to-text vs Inworld STT for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt" }, "tokens": { "markdown": 5850, "slim": 3480 }, "version": 1 }