# Inworld STT vs Mistral Voxtral Transcribe

> Mistral Voxtral Transcribe scores 63.1 (B) to Inworld STT's 54.7 (C) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe
- Markdown: https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe.md (~5,900 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Mistral Voxtral Transcribe scores 63.1 (B) on agent readiness against Inworld STT's 54.7 (C), and leads in 5 of 7 scored categories. Inworld STT leads on reliability. Both do speech-to-text.

- 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
- Mistral Voxtral Transcribe: grade B, 63.1/100, rank #526 of 1486. Markdown https://www.anchorterminal.com/tools/mistral-voxtral-transcribe.md · JSON https://www.anchorterminal.com/api/v1/tools/mistral-voxtral-transcribe.json
- Best speech-to-text APIs for AI agents: https://www.anchorterminal.com/best/speech-to-text/index.md
- All 320 stt comparisons: https://www.anchorterminal.com/compare/speech-to-text/index.md

## Which one, for what

### Inworld STT (C)

Good for: Low-cost live transcription for voice agents, with speaker traits.

Ahead on:
- Reliability, 60 against 53

Also in its favour:
- Free to start without a card
- No incidents deducted, where Mistral Voxtral Transcribe loses 6 points for them

Watch for: No OpenAPI or other machine-readable contract

### Mistral Voxtral Transcribe (B)

Good for: Suited to low-cost batch transcription with diarisation in the 13 supported languages, and to live captions or voice agents that can run without speaker labels.

Ahead on:
- Schema & documentation, 85 against 54
- Agent ergonomics, 77 against 56
- Security & auth, 70 against 63
- Maintenance & community, 88 against 41
- Transparency & trust, 83 against 60

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Voxtral Mini Transcribe 2 and Realtime 2602 retire on 30 April 2027, and their Voxtral 3 replacements are Public Preview with silent updates allowed


## Why the edge

### Maintenance & community: Mistral Voxtral Transcribe +47

- 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.
- Mistral Voxtral Transcribe (88): Model reading. Mistral released three Voxtral 3 transcription models (Mini Transcribe 3, Small Transcribe 3 and Mini Transcribe Realtime 3) in Public Preview on 20 October 2026, 13 days before this check (30). The lifecycle policy promises six months' notice for GA models, and Transcribe 2 and Realtime 2602 were deprecated on 31 October with retirement on 30 April 2027, 181 days (12 of 12). No transcription model was retired in the 90 days to 2 November; Voxtral Mini Transcribe (2507) retired on 31 May 2026 (8 of 8). Six dated changelog entries from 31 August to 22 October, one of them the Voxtral 3 release, read as mistral-api reads the same changelog (10 of 15). The eight newest open issues on client-python had zero or one comment per the 8 October check (5 of 10). Official `mistralai` 3.7.0 (1 November) per the client-python RELEASES.md, and `@mistralai/mistralai`, with a v2 to v3 migration guide (15). Both are generated from the OpenAPI document, with test, lint and example workflows in the repository (8 of 10). 30+12+8+10+5+15+8 = 88.

### Schema & documentation: Mistral Voxtral Transcribe +31

- 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.
- Mistral Voxtral Transcribe (85): Model reading. The public OpenAPI document covers `/v1/audio/transcriptions`, its SSE streaming form and `/v1/client/sessions`. The realtime WebSocket messages are described by SDK types and guide examples, not by the document (22 of 25). llms.txt with Markdown twins of the speech-to-text, offline, realtime and client authentication pages (10). The guides say which model each endpoint runs, that `timestamp_granularities` and `language` cannot be combined and that realtime cannot diarise, and carry an OpenAI SDK compatibility table. In the OpenAPI document `diarize`, `context_bias` and `temperature` have no description (14 of 20). `timestamp_granularities` is an enum of `segment` and `word`, `language` is a two-letter pattern and `context_bias` items have a pattern, while `model` is a free string (12 of 15). curl, Python and TypeScript examples on each guide and a shared error glossary. The OpenAPI response example still names `voxtral-mini-2507` (12 of 15). Dated model identifiers and a dated changelog (15).

### Transparency & trust: Mistral Voxtral Transcribe +23

- 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.
- Mistral Voxtral Transcribe (83): The hosted service is closed under commercial terms. The Realtime weights are published on Hugging Face under Apache-2.0 and the SDKs are Apache-2.0, while Voxtral Mini Transcribe 2 has no public weights (20 of 30). The privacy policy effective 3 September 2026 (30 rolling days), the zero data retention page and the terms agree on retention, and the terms leave the API's training default unnamed (20 of 30). A model lifecycle page with notice periods per stage (20). Opt-in EU and US regional endpoints are documented, the global endpoint commits to no location, and the provider list is in a trust centre we could not read (13 of 20).

### Agent ergonomics: Mistral Voxtral Transcribe +21

- 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.
- Mistral Voxtral Transcribe (77): API reading, as for the other speech-to-text listings. Segments, word timestamps and speaker labels are returned only when asked for, and the default response is the text, the language and usage. No subtitle or plain-text output format was found (18 of 25). There is no transcript store to page through. Volume goes through the batch API, which accepts `/v1/audio/transcriptions` (12 of 20). Errors return `type`, `param` and `code` with a fix per status in the glossary (17 of 20). The call is stateless and safe to retry, the SDKs retry with backoff, and no idempotency key exists or is needed (15 of 20). `model` is the only required field beside the audio source, and there are official Python and TypeScript SDKs plus OpenAI SDK compatibility for the batch endpoint (15).

### Reliability: Inworld STT +7

- 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.
- Mistral Voxtral Transcribe (53): Hosted reading. The docs point to status.mistral.ai, a Rootly page with component uptime bars per the 1 and 2 October reading on the other Mistral listings (20). The page has answered with a Cloudflare bot check since 8 October, robots.txt included on 2 November, so it is treated as blocked and the 90-day record for audio was not read (5, unread and not a finding against the vendor). The limits page names audio seconds a minute and audio seconds a month as the audio limits, with the numbers shown only in the Admin Panel, per the 8 October check (3 of 15). The error glossary tells callers to back off exponentially on 429, 500, 502, 503 and 504 and to read the `Retry-After` header, and the official SDKs retry with backoff. Transcription is a stateless call (15). No SLA found (0). Voxtral Mini Transcribe 2 and Realtime (2602) are deprecated but served until 30 April 2027, and `voxtral-mini-latest` still points to Transcribe 2, while the Voxtral 3 transcription models are Public Preview (10).

### Security & auth: Mistral Voxtral Transcribe +7

- 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.
- Mistral Voxtral Transcribe (70): Model reading, scored like the other Mistral listings. Keys are bound to one workspace, can carry an expiry date and a connector scope, and organisations can enforce a maximum key lifetime. Browser clients get `rt_` tokens from `POST /v1/client/sessions` that last about 900 seconds, work for one model and travel in `Sec-WebSocket-Protocol`. A key cannot be limited to transcription (26 of 30). The commercial terms effective 25 September 2026 say Mistral will not train on customer data unless the customer opted in, or did not opt out where a product defaults to opt-in, without naming the API's default. The privacy and data controls page the docs link to returned 404 (10 of 20). Input and output are kept 30 rolling days for abuse monitoring, and `/v1/audio/transcriptions` is on the zero data retention list for paid plans, on request and subject to approval (12 of 15). Audit logs cover API key actions on Enterprise plans only (10 of 15). security.txt is valid until 5 May 2027 and names a HackerOne submission form, and the docs publish three security advisories for 2026. Certifications sit in a trust centre drawn by script that we could not read (12 of 20).

## Score by category

| Category | Weight | Inworld STT | Mistral Voxtral Transcribe | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 53 | Inworld STT +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 54 | 85 | Mistral Voxtral Transcribe +31 |
| Agent ergonomics | 13% (16.2 this run) | 56 | 77 | Mistral Voxtral Transcribe +21 |
| Security & auth | 14% (17.5 this run) | 63 | 70 | Mistral Voxtral Transcribe +7 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 41 | 88 | Mistral Voxtral Transcribe +47 |
| Transparency & trust | 7% (8.8 this run) | 60 | 83 | Mistral Voxtral Transcribe +23 |
| Negative events | ≤15 | 0 | -6 | |
| **Total** | | **54.7 · C** | **63.1 · B** | |

## Facts side by side

| Fact | Inworld STT | Mistral Voxtral Transcribe |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Inworld AI | Mistral AI |
| Hosted endpoint | no (local only) | `https://api.mistral.ai/v1` |
| Transports | HTTP, websocket | HTTP, websocket |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| Price for speech-to-text | $0.0017 per minute of audio | not published |
| x402 | no | no |
| Licence | none | Proprietary hosted service under Mistral's commercial terms. Voxtral Mini 4B Realtime weights and the SDKs are Apache-2.0 |
| Tools exposed | 0 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-29 | 2026-10-20 |
| Terms last updated | 2025-06-11 | 2026-09-25 |
| Privacy policy last updated | 2026-01-18 | 2026-09-03 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 773 stars |
| Agent reviews | none | 4/5 (4) |

## What the same task costs

| Task | Inworld STT | Mistral Voxtral Transcribe |
| --- | --- | --- |
| Transcribe a one-hour meeting | $0.10 to $0.15 | $0.18 to $0.48 |

## How the scores have moved

### Inworld STT

No score change since it was listed.

### Mistral Voxtral Transcribe

- -1.1 on 2 November 2026: product, negative event
- +0.1 on 27 October 2026: checklist

## 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.

**Mistral Voxtral Transcribe.** Batch transcription costs $0.003 a minute and takes one multipart call with a file, a URL or an uploaded file ID. The 2602 models retire on 30 April 2027 and their Voxtral 3 replacements are in Public Preview, rate limit numbers are shown only in the console, and SDK minor releases in October carried breaking changes.

## Before you call either

### Inworld STT

1. Send the Base64 credential as-is in `Authorization: Basic`; don't encode it again
2. Wrap the first WebSocket message in `transcribeConfig`, because a malformed first frame closes the socket with 1005 and no error
3. Use `POST /stt/v1/transcribe:async` for files over about 16 MB and collect the transcript within 7 days
4. Retry 429 or gRPC code 8 with exponential backoff and jitter, and stay within the plan's streaming concurrency
5. Stop sending audio when nobody speaks, since streams are billed for every second sent

### Mistral Voxtral Transcribe

1. Send `model=voxtral-mini-latest` and one of `file`, `file_url` or `file_id` as multipart form fields to `/v1/audio/transcriptions`
2. Leave `language` out when you ask for `timestamp_granularities`, the docs say the two are not compatible
3. Use the batch endpoint for diarisation with the 2602 models. `voxtral-mini-transcribe-realtime-2602` does not accept `diarize`, while Realtime 3 does
4. Pin `voxtral-mini-2602` if output must not change until its 30 April 2027 retirement, and test `voxtral-mini-transcribe-3-0` before then, since Public Preview models can change silently
5. Mint browser tokens with `POST /v1/client/sessions` close to connection time and pass them in `Sec-WebSocket-Protocol`, never the API key

## Questions

### Which is better for AI agents, Inworld STT or Mistral Voxtral Transcribe?

Mistral Voxtral Transcribe scores 63.1 (B) on agent readiness against Inworld STT's 54.7 (C), and leads in 5 of 7 scored categories. Inworld STT leads on reliability.

### Do Inworld STT and Mistral Voxtral Transcribe need an API key?

Both need an API key.

### Can an agent call Inworld STT and Mistral Voxtral Transcribe without installing anything?

No hosted endpoint is listed for Inworld STT. Mistral Voxtral Transcribe has a hosted endpoint at https://api.mistral.ai/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe.json, and with the fewest tokens: https://www.anchorterminal.com/compare/inworld-stt-vs-mistral-voxtral-transcribe.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "inworld-stt", "b": "mistral-voxtral-transcribe"}`. From a terminal: `anchor compare inworld-stt mistral-voxtral-transcribe`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/inworld-stt.json and https://www.anchorterminal.com/api/v1/tools/mistral-voxtral-transcribe.json

## Other comparisons with Inworld STT or Mistral Voxtral Transcribe

- [Amazon Transcribe vs Inworld STT](https://www.anchorterminal.com/compare/amazon-transcribe-vs-inworld-stt.md)
- [Amazon Transcribe vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/amazon-transcribe-vs-mistral-voxtral-transcribe.md)
- [AssemblyAI Speech-to-Text (Universal) vs Inworld STT](https://www.anchorterminal.com/compare/assemblyai-stt-vs-inworld-stt.md)
- [AssemblyAI Speech-to-Text (Universal) vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/assemblyai-stt-vs-mistral-voxtral-transcribe.md)
- [Azure AI Speech speech-to-text vs Inworld STT](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-inworld-stt.md)
- [Azure AI Speech speech-to-text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/azure-speech-to-text-vs-mistral-voxtral-transcribe.md)
- [Cartesia Ink vs Inworld STT](https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-inworld-stt.md)
- [Cartesia Ink vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/cartesia-ink-stt-vs-mistral-voxtral-transcribe.md)
- [Deepgram Speech-to-Text (Nova-3, Flux) vs Inworld STT](https://www.anchorterminal.com/compare/deepgram-stt-vs-inworld-stt.md)
- [Deepgram Speech-to-Text (Nova-3, Flux) vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/deepgram-stt-vs-mistral-voxtral-transcribe.md)
- [ElevenLabs Scribe Speech to Text API vs Inworld STT](https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-inworld-stt.md)
- [ElevenLabs Scribe Speech to Text API vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/elevenlabs-scribe-vs-mistral-voxtral-transcribe.md)
- [Giggy Speech to Text vs Inworld STT](https://www.anchorterminal.com/compare/giggy-stt-vs-inworld-stt.md)
- [Giggy Speech to Text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/giggy-stt-vs-mistral-voxtral-transcribe.md)
- [Gladia Speech-to-Text API + MCP vs Inworld STT](https://www.anchorterminal.com/compare/gladia-stt-vs-inworld-stt.md)
- [Gladia Speech-to-Text API + MCP vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/gladia-stt-vs-mistral-voxtral-transcribe.md)
- [Google Cloud Speech-to-Text vs Inworld STT](https://www.anchorterminal.com/compare/google-speech-to-text-vs-inworld-stt.md)
- [Google Cloud Speech-to-Text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/google-speech-to-text-vs-mistral-voxtral-transcribe.md)
- [Groq Speech-to-Text vs Inworld STT](https://www.anchorterminal.com/compare/groq-speech-to-text-vs-inworld-stt.md)
- [Groq Speech-to-Text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/groq-speech-to-text-vs-mistral-voxtral-transcribe.md)
- [IBM Watson Speech to Text vs Inworld STT](https://www.anchorterminal.com/compare/ibm-watson-stt-vs-inworld-stt.md)
- [IBM Watson Speech to Text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/ibm-watson-stt-vs-mistral-voxtral-transcribe.md)
- [Inworld STT vs MiniMax Speech-to-Text](https://www.anchorterminal.com/compare/inworld-stt-vs-minimax-stt.md)
- [Inworld STT vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/inworld-stt-vs-openai-speech-to-text.md)
- [Inworld STT vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/inworld-stt-vs-rev-ai-stt.md)
- [Inworld STT vs Smallest.ai Pulse STT](https://www.anchorterminal.com/compare/inworld-stt-vs-smallest-pulse-stt.md)
- [Inworld STT vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/inworld-stt-vs-soniox-stt.md)
- [Inworld STT vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/inworld-stt-vs-speechmatics-stt.md)
- [MiniMax Speech-to-Text vs Mistral Voxtral Transcribe](https://www.anchorterminal.com/compare/minimax-stt-vs-mistral-voxtral-transcribe.md)
- [Mistral Voxtral Transcribe vs OpenAI Speech to Text](https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-openai-speech-to-text.md)
- [Mistral Voxtral Transcribe vs Rev AI Speech-to-Text API](https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-rev-ai-stt.md)
- [Mistral Voxtral Transcribe vs Smallest.ai Pulse STT](https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-smallest-pulse-stt.md)
- [Mistral Voxtral Transcribe vs Soniox Speech-to-Text](https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-soniox-stt.md)
- [Mistral Voxtral Transcribe vs Speechmatics Speech-to-Text](https://www.anchorterminal.com/compare/mistral-voxtral-transcribe-vs-speechmatics-stt.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp