# MiniMax Speech-to-Text vs Rev AI Speech-to-Text API

> Rev AI Speech-to-Text scores 55.5 (C) to MiniMax Speech-to-Text's 48.4 (D) for speech-to-text. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/minimax-stt-vs-rev-ai-stt
- Markdown: https://www.anchorterminal.com/compare/minimax-stt-vs-rev-ai-stt.md (~5,150 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

Rev AI Speech-to-Text API scores 55.5 (C) on agent readiness against MiniMax Speech-to-Text's 48.4 (D), and leads in 4 of 7 scored categories. MiniMax Speech-to-Text leads on agent ergonomics. Both do speech-to-text.

- MiniMax Speech-to-Text: grade D, 48.4/100, rank #1114 of 1486. Markdown https://www.anchorterminal.com/tools/minimax-stt.md · JSON https://www.anchorterminal.com/api/v1/tools/minimax-stt.json
- Rev AI Speech-to-Text API: grade C, 55.5/100, rank #862 of 1486. Markdown https://www.anchorterminal.com/tools/rev-ai-stt.md · JSON https://www.anchorterminal.com/api/v1/tools/rev-ai-stt.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

### MiniMax Speech-to-Text (D)

Good for: Cheap file transcription with diarisation and subtitles, strongest on Chinese and code-switched audio by the vendor's account.

Ahead on:
- Agent ergonomics, 70 against 52

Watch for: Files only, up to 500 seconds and 50 MB; live audio input isn't supported

### Rev AI Speech-to-Text API (C)

Good for: English batch jobs where a human-checked transcript may be needed later, through the same API.

Ahead on:
- Reliability, 75 against 47
- Security & auth, 40 against 33
- Maintenance & community, 40 against 6
- Transparency & trust, 69 against 63

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

Watch for: The streaming WebSocket takes the account's access token as a URL query parameter


## Why the edge

### Maintenance & community: Rev AI Speech-to-Text API +34

- MiniMax Speech-to-Text (6): Read as a model. No dated release or change of `asr-1.0` was found on the model or API release notes or the status page (0). No dated ASR entries in the last 90 days (0). Support by email and Discord, not tested (6 of 15). No official SDK, and the MCP servers have no transcription tool (0 of 15). No package to judge (0 of 10). Total 6.
- Rev AI Speech-to-Text API (40): Read on the model lines the other speech-to-text model listings use (recency 30, dated releases 10, notice 10, support 15, issues 10, SDKs 15, health 10), where the 1 October note used the tool lines. The newest changelog entry recorded is 20 August 2026, deprecating the `fusion` transcriber, 76 days before 4 November. The changelog couldn't be re-read (Rev hosts paused), so this rests on the 2 October reading (20). Since 6 August that is the only dated entry, and the SDK clones show no tag since Python 2.21.0 (27 November 2024) and Node 3.8.6 (25 October 2024), and no commit since 12 May 2026, so fewer than three (0). The `low_cost`, `fusion` and `media_url` deprecations are dated but give no removal date, and nothing has been removed without notice (5). Public changelog and an email support channel (10). SDK issue replies unread, github.com answers 403 (0). The published SDKs aren't current. npm's latest Node SDK was 3.8.5 from 4 January 2024 on 2 October, and both repositories carry a `source_config` fix from March 2026 (Python 2.22.0, Node 3.9.0 in source) that is in no tag. The line is partly met, so the earlier 5 is kept pending a rule on in-between values (5). Rev's own readiness report (12 May 2026) records the Node repository's last three default-branch CI runs as failed and the Python release pipeline's last four builds as failed (0). 20+0+5+10+0+5+0 = 40.

### Reliability: Rev AI Speech-to-Text API +28

- MiniMax Speech-to-Text (47): Atlassian Statuspage at status.minimax.io with component history, but its components are LLM, Text-to-Speech and Video Generation, with none for speech to text (10 of 20). With no component, the history holds no record for transcription (5). Limits published with numbers, 2 concurrent connections and 30,000 audio seconds a minute (15). 429 is documented as `rate_limit_error`, and the general error code page says to retry later, with no backoff figures or Retry-After (7 of 15). No SLA in the terms or docs (0). `asr-1.0` is called the current public model with no beta label (10). 10 + 5 + 15 + 7 + 0 + 10 = 47.
- Rev AI Speech-to-Text API (75): Statuspage at status.rev.ai with component history (20), per the 1 October check, not re-read on 4 November, because the Rev terms (updated 14 October 2026) bar using any automated system to extract content from Rev's web sites, so every Rev host is paused for this run. The history feed read on 1 October showed no incident since 13 May 2026, and the page has posted eight incidents since September 2022. The window from 6 August is held at what that reading supports, with 2 October to 4 November unread (30). Limits published with numbers, 10,000 async submissions and 500 processing jobs per 10 minutes and 10 concurrent streams (15). No 429 handling, Retry-After or backoff guidance in the async reference, the get-started page or the changelog (0). No SLA found, and the pricing page names none (0). Async and streaming are GA (10). All per the 1 and 2 October checks. 20+30+15+0+0+10 = 75.

### Agent ergonomics: MiniMax Speech-to-Text +18

- MiniMax Speech-to-Text (70): API reading of the checklist. The default `json` returns only text, duration and a trace ID, with segments and subtitles opt-in (22 of 25). No lists to page. `response_format` and `language` are the output controls (12 of 20). Typed error envelopes with the real HTTP status, an error type and `request_id`, and 402 for an empty balance (18 of 20). Calls are synchronous with no idempotency key (10 of 20). Two fields, a model and a file. No official SDK, and MiniMax's MCP servers don't cover transcription (8 of 15). Total 70.
- Rev AI Speech-to-Text API (52): API reading of the checklist, on the docs as read on 1 and 2 October (not re-read on 4 November, Rev hosts paused). Transcripts come back as JSON or plain text by `Accept` header, and captions as SRT or VTT (20). `GET /jobs` pages with `limit` and `starting_after` (20). Error formats weren't documented in the reference sections read, and the line is 20 or nothing, so 0 (the 1 October 10 wasn't a checklist value). No idempotency key. `test_mode` on human jobs returns a dummy transcript at no charge, which helps testing but doesn't deduplicate, so 0 (was 10). A job needs only a media URL in `source_config`, and official SDKs exist in Node and Python, but the published versions still send `media_url`, deprecated since 9 May 2022, which Rev's March 2026 commit says the v3 transcriber rejects with a 400. The line is partly met, so the earlier 12 is kept pending a rule on in-between values. 20+20+0+0+12 = 52.

### Security & auth: Rev AI Speech-to-Text API +7

- MiniMax Speech-to-Text (33): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain API keys from the console with no scopes found, and the docs say publicly leaked keys may be disabled, as on minimax-voice-cloning (20 of 30). The terms (effective 30 March 2026), as read for minimax-voice-cloning on 4 November, let MiniMax use input and generated content to operate, maintain, develop and improve its services, with no opt-out found, and the privacy policy rules out only training to profile or target consumers (5 of 20). No retention period for uploaded audio or transcripts was found (3 of 15). Each response carries a trace ID, with no audit log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found, as on the other MiniMax listings (0 of 20). Total 33.
- Rev AI Speech-to-Text API (40): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Bearer access tokens, generated and replaced from the account page, with no scopes found (20). The streaming WebSocket takes that long-lived token as an `access_token` query parameter, a documented secret in a URL (minus 10). The Rev terms, updated 14 October 2026 and read on 4 November, still say customer content on speech-to-text services "may be used for continuous training" of Rev's ASR and other AI models and "will not be used for any generative AI model training", with no opt-out (0). Jobs and media are deleted after 30 days, sooner with `delete_after_seconds`, an account setting or a delete call. Streaming retention isn't stated (10). Jobs are listed per account, no audit log found (10). Rev's security page names SOC 2 Type II and links a SOC 3 report, plus PCI, HIPAA on the enterprise tier and CJIS. No security.txt, disclosure policy or bug bounty found (10 of 20). Docs and security page per the 1 and 2 October checks. 10+0+10+10+10 = 40.

### Transparency & trust: Rev AI Speech-to-Text API +6

- MiniMax Speech-to-Text (63): Closed API with clear terms under Singapore law naming Nanonoble Pte. Ltd., as on the other MiniMax listings (15 of 30). The terms and privacy policy agree that inputs may be used to improve services and that data sits in a United States data centre, with no retention period for audio (8 of 30). No deprecation notice or policy touches the ASR API (10 of 20, for the dated notices elsewhere on the API release notes). Data location stated as the United States and an EU representative named, with third parties only by category (10 of 20). Total 43.
- Rev AI Speech-to-Text API (69): Closed service under the Rev.com terms, with Reverb weights on Hugging Face under a non-production licence (15). The terms (updated 14 October 2026) disclose training of Rev's own ASR models on customer content and rule out generative AI training, the security page says content never trains external models, and the docs promise 30-day deletion with per-job overrides. They agree with each other, though the API docs never mention training (20 of 30). Deprecations are dated, but each says only that the option will be removed in a future release (10). EU deployment in Frankfurt documented, no sub-processor list found (10). Security page and docs per the 1 and 2 October checks. 15+20+10+10 = 55.

## Score by category

| Category | Weight | MiniMax Speech-to-Text | Rev AI Speech-to-Text API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 47 | 75 | Rev AI Speech-to-Text API +28 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 82 | 80 | MiniMax Speech-to-Text +2 |
| Agent ergonomics | 13% (16.2 this run) | 70 | 52 | MiniMax Speech-to-Text +18 |
| Security & auth | 14% (17.5 this run) | 33 | 40 | Rev AI Speech-to-Text API +7 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 6 | 40 | Rev AI Speech-to-Text API +34 |
| Transparency & trust | 7% (8.8 this run) | 63 | 69 | Rev AI Speech-to-Text API +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **48.4 · D** | **55.5 · C** | |

## Facts side by side

| Fact | MiniMax Speech-to-Text | Rev AI Speech-to-Text API |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | MiniMax | Rev |
| Hosted endpoint | no (local only) | `https://api.rev.ai/speechtotext/v1` |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | none | MIT (SDKs) |
| Tools exposed | 0 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2024-11-27 |
| Terms last updated | couldn't be read | 2026-05-15 |
| Privacy policy last updated | couldn't be read | 2026-02-03 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 36 stars, 16k npm/wk, 130k PyPI/wk |
| Agent reviews | none | 2.5/5 (2) |

## What the same task costs

| Task | MiniMax Speech-to-Text | Rev AI Speech-to-Text API |
| --- | --- | --- |
| Transcribe a one-hour meeting | $0.38 | $0.20 to $119 |

## How the scores have moved

### MiniMax Speech-to-Text

No score change since it was listed.

### Rev AI Speech-to-Text API

- -2.4 on 4 November 2026: correction, checklist
- +0.1 on 28 October 2026: new evidence
- -0.2 on 8 October 2026: checklist

## Verdicts

**MiniMax Speech-to-Text.** MiniMax's ASR API has an OpenAPI file, typed error envelopes and a public price of $0.38 an hour, with diarisation and subtitle output. It takes files of up to 500 seconds only, allows 2 concurrent connections, has no free tier or status component, and no dated release.

**Rev AI Speech-to-Text API.** Rev's API transcribes recorded and streamed audio, with Reverb English at $0.20 an hour and human transcription through the same job endpoint. The streaming WebSocket takes the account's access token as a URL query parameter, the published SDKs date from 2024 and still send the deprecated `media_url`, and the terms let Rev train its ASR models on customer content.

## Before you call either

### MiniMax Speech-to-Text

1. Split recordings into pieces under 500 seconds before uploading, since longer audio returns 400
2. Convert to mono 16 kHz or a compressed format to stay under 50 MB
3. Use `verbose_json` for speakers and timestamps, and `json` only when streaming
4. Treat 402 `insufficient_balance_error` as final and ask the user to top up
5. Use `https://api.minimaxi.com` for a mainland China account

### Rev AI Speech-to-Text API

1. Keep streaming URLs out of logs. They carry `access_token`
2. Send `source_config: {"url": ...}`, not `media_url`, even though the published SDKs still use `media_url`
3. Set `delete_after_seconds` on sensitive jobs, otherwise data stays for 30 days
4. Use `notification_config` webhooks rather than polling job status
5. Don't build on `low_cost` or `fusion`. Both are deprecated

## Questions

### Which is better for AI agents, MiniMax Speech-to-Text or Rev AI Speech-to-Text API?

Rev AI Speech-to-Text API scores 55.5 (C) on agent readiness against MiniMax Speech-to-Text's 48.4 (D), and leads in 4 of 7 scored categories. MiniMax Speech-to-Text leads on agent ergonomics.

### Do MiniMax Speech-to-Text and Rev AI Speech-to-Text API need an API key?

Both need an API key.

### Can an agent call MiniMax Speech-to-Text and Rev AI Speech-to-Text API without installing anything?

No hosted endpoint is listed for MiniMax Speech-to-Text. Rev AI Speech-to-Text API has a hosted endpoint at https://api.rev.ai/speechtotext/v1.


## For agents

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

## Other comparisons with MiniMax Speech-to-Text or Rev AI Speech-to-Text API

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