{ "data": { "a": { "slug": "minimax-speech", "name": "MiniMax Speech (T2A)", "vendor": "MiniMax", "vendorUrl": "https://www.minimax.io", "kind": "model", "category": "text-to-speech", "summary": "MiniMax's text-to-speech API synthesises speech with its speech-2.8 HD and Turbo models over HTTP with optional streaming, WebSocket (including bidirectional text streaming) and an asynchronous long-text API, with 300+ system voices, pronunciation dictionaries and subtitles.", "url": "https://www.anchorterminal.com/tools/minimax-speech", "markdownUrl": "https://www.anchorterminal.com/tools/minimax-speech.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/minimax-speech.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/minimax-speech.json", "dns": "minimax-speech.grade.anchorterminal.com", "transports": [ "http", "websocket" ], "packages": [ { "registry": "pypi", "name": "minimax-mcp" }, { "registry": "npm", "name": "minimax-mcp-js" } ], "auth": "api-key", "authNotes": "Bearer API key created in the platform console under Account, API Keys. No scopes were found in the docs. Mainland China accounts use `https://api.minimaxi.com`.", "pricing": "usage", "pricingNotes": "Pay as you go from a prepaid balance. speech-2.8-hd costs $100 and speech-2.8-turbo $60 per million characters, on the sync and async APIs alike. Audio subscriptions from $5 a month add voice slots and higher request rates. No free allowance is published for speech synthesis.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, OpenAPI and AsyncAPI files or pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://platform.minimax.io/docs/api-reference/speech-t2a-http", "llmsTxt": "https://platform.minimax.io/docs/llms.txt", "openapi": "https://platform.minimax.io/docs/api-reference/speech/t2a/api/openapi.json", "capabilities": [ "speech.tts", "speech.streaming", "speech.voices", "speech.languages" ], "tags": [ "official", "hosted", "usage-priced", "prepaid", "openapi", "llms-txt", "mcp", "python", "typescript", "status-page" ], "lastRelease": "2026-01-23", "graded": true, "anchor": { "graded": true, "score": 55.1, "grade": "C", "agentReady": false, "rank": 884, "ranked": true, "rankOf": 1510, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 38, "payments": 20, "reliability": 75, "schema": 81, "security": 36, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "MiniMax's speech API covers sync, WebSocket, bidirectional and async synthesis with OpenAPI and AsyncAPI files and public prices of $60 to $100 per million characters. Text-to-Speech had only short incidents in 90 days. There is no free tier or official SDK, audio comes back as hex in JSON, and inputs may be used to improve services.", "bestFor": "Multilingual speech for narration and agents at mid-range prices, with strong Chinese voices by the vendor's account.", "strengths": [ "OpenAPI files for sync and async synthesis and AsyncAPI files for both sockets", "Statuspage with a Text-to-Speech component; three incidents in 90 days, the longest 22 minutes", "Public prices of $60 (Turbo) and $100 (HD) per million characters on sync and async alike", "Pronunciation dictionaries, pause markers, timbre mixing and subtitles", "Official MCP servers in Python and JavaScript with a speech tool" ], "weaknesses": [ "No free allowance for synthesis and no official SDK", "Sync responses carry audio as hex inside JSON, and the OpenAPI file documents only a 200 response", "API release notes stop at 28 October 2025, and the newest speech model dates from January 2026", "Terms let MiniMax use inputs to improve its services with no opt-out, and no retention period is published", "No security.txt, disclosure policy or certification found" ], "agentNotes": [ "Keep sync requests under 10,000 characters and use the async API for longer text", "Decode the hex `audio` field before saving, or stream for text over 3,000 characters", "Check `base_resp.status_code` on every response, since errors arrive inside a 200", "Stay under 60 requests a minute and back off on code 1002", "Use speech-2.8-turbo for agents and HD only where quality matters, since HD costs two thirds more" ], "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": 55.1 } ], "editorialScores": { "ergonomics": 56, "maintenance": 38, "payments": 20, "reliability": 75, "schema": 81, "security": 36, "transparency": 48 }, "provenanceScore": 82, "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": { "http": "curl -X POST https://api.minimax.io/v1/t2a_v2 \\\n -H \"Authorization: Bearer $MINIMAX_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"model\": \"speech-2.8-turbo\", \"text\": \"Hello from MiniMax.\", \"voice_setting\": {\"voice_id\": \"English_expressive_narrator\"}}'" }, "letme": { "capability": "https://letme.dev/speech.tts", "tool": "https://letme.dev/minimax-speech" }, "sameCompany": [ "minimax-api", "minimax-video", "minimax-stt", "minimax-voice-cloning", "minimax-code", "minimax-m2-5", "minimax-m2-7", "minimax-m3-1-flash" ], "area": "voice", "unitPrices": [ { "item": "speech-2.8-hd", "unit": "1m-chars", "usd": 100, "note": "sync and async" }, { "item": "speech-2.8-turbo", "unit": "1m-chars", "usd": 60, "note": "sync and async" } ], "provenance": { "legalEntity": "Nanonoble Pte. Ltd.", "domain": "minimax.io", "domainRegistered": "2021-03-27", "endpointOnVendorDomain": true, "terms": "https://platform.minimax.io/protocol/terms-of-service", "privacy": "https://platform.minimax.io/protocol/privacy-policy", "statusPage": "https://status.minimax.io", "changelog": "https://platform.minimax.io/docs/release-notes/apis", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "Nanonoble Pte. Ltd., 152 Beach Road, #14-02 Gateway East, Singapore, is named in the terms (effective 30 March 2026) and the privacy policy (updated 30 March 2026), read on 4 November 2026 from the document text the pages carry for the browser, as on the minimax-api listing. The 8 October reader recorded both pages as unreadable.", "RDAP for minimax.io gives a registration date of 2021-03-27 and a transfer on 2025-01-31, as recorded on 8 October.", "platform.minimax.io/.well-known/security.txt returns 404 (per the 8 October check), and www.minimax.io/.well-known/security.txt redirects to the home page.", "The API release notes page has no entry after 28 October 2025 on 4 November. Model releases are dated on a separate page, whose newest speech model is Speech 2.8 (23 January 2026).", "status.minimax.io/robots.txt disallows /api/, so incidents were read from the /history pages only.", "firstReleased is left empty. lastRelease is Speech 2.8, dated 23 January 2026 on the model release page." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/minimax-speech.json", "live": { "slug": "minimax-speech", "vendorStatus": { "page": "https://status.minimax.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:28.011553023Z" }, "versions": [ { "registry": "npm", "name": "minimax-mcp-js", "version": "0.0.18", "seenAt": "2026-11-06T23:46:02.528010346Z" }, { "registry": "pypi", "name": "minimax-mcp", "version": "0.0.19", "released": "2026-08-21", "seenAt": "2026-11-06T23:46:02.341494165Z" } ], "npmWeekly": 493, "pypiWeekly": 2443, "securityTxt": { "url": "https://minimax.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:57.120551174Z" }, "llmsTxt": { "url": "https://platform.minimax.io/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:04.532998601Z" }, "pages": [ { "url": "https://platform.minimax.io/docs/release-notes/apis", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:16:49.741417545Z", "changedAt": "2026-11-05T12:39:36.530148547Z", "fingerprint": "dc39bde39ad3" } ], "updatedAt": "2026-11-07T19:22:28.011553023Z" } }, "answer": "MiniMax Speech (T2A) scores 55.1 (C) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category.", "b": { "slug": "playht-tts", "name": "PlayHT Text-to-Speech API", "vendor": "PlayHT", "vendorUrl": "https://play.ht", "kind": "model", "category": "text-to-speech", "summary": "Discontinued text-to-speech API from PlayHT, formerly supporting streaming audio and batch generation.", "url": "https://www.anchorterminal.com/tools/playht-tts", "markdownUrl": "https://www.anchorterminal.com/tools/playht-tts.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/playht-tts.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/playht-tts.json", "dns": "playht-tts.grade.anchorterminal.com", "repo": "https://github.com/playht/pyht", "license": "Apache-2.0 (Python SDK)", "transports": [ "http" ], "remoteUrl": "https://api.play.ht/api/v2", "packages": [ { "registry": "npm", "name": "playht" }, { "registry": "pypi", "name": "pyht" } ], "auth": "api-key", "authNotes": "Two headers, `X-USER-ID` and `AUTHORIZATION` with the secret key, both from the dashboard. The endpoints no longer answer.", "pricing": "paid", "pricingNotes": "Sold as monthly API plans named Hacker or Pro, Startup, Growth and Enterprise, with rate limits set by plan. The plan prices couldn't be recovered from a primary source, since the API pricing tab wasn't archived and play.ht is gone. The last archived pricing page shows Studio plans only (https://web.archive.org/web/20250625003728/https://play.ht/pricing/).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "Service shut down. No x402 or machine payment was ever documented (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 218, "npmWeekly": 14219, "pypiWeekly": 6561, "asOf": "2026-09-30" }, "docsUrl": "https://docs.play.ht/reference/api-getting-started", "llmsTxt": "https://docs.play.ht/llms.txt", "capabilities": [ "speech.tts", "speech.streaming", "speech.voices", "speech.languages" ], "tags": [ "closed-source", "retired", "python", "typescript" ], "lastRelease": "2025-05-21", "graded": true, "anchor": { "graded": true, "score": 4.1, "grade": "F", "agentReady": false, "rank": 0, "ranked": false, "notRankedWhy": "Shut down 2025-12-31, so out of the ranking", "rankOf": 1510, "categoryRank": 24, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 0, "payments": 0, "reliability": 0, "schema": 31, "security": 0, "transparency": 35 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-17" }, "negative": -4, "negativeNotes": [ "2026-10-01, still the case on 2026-10-17. docs.play.ht documents `POST /api/v2/tts/stream`, the WebSocket API and batch jobs with no shutdown notice, and its llms.txt indexes them as live, while api.play.ht doesn't resolve and the platform closed on 2025-12-31. An endpoint removed while still advertised. https://docs.play.ht/reference/api-getting-started.md and https://inworld.ai/resources/migrate-from-playht" ], "verdict": "The old API reference is still readable at docs.play.ht for anyone porting code. api.play.ht doesn't resolve, so every call fails.", "strengths": [ "The old API reference is still readable at docs.play.ht for anyone porting code", "SDKs remain on GitHub under Apache-2.0" ], "weaknesses": [ "api.play.ht doesn't resolve, so every call fails", "docs.play.ht and its llms.txt document live-looking endpoints with no shutdown notice", "Accounts, audio and voice clones were reportedly deleted at shutdown with no export", "No notice from PlayHT itself found on the live site, only third-party migration guides" ], "agentNotes": [ "Don't call api.play.ht, it doesn't resolve.", "Ignore docs.play.ht code samples, its llms.txt and the OpenAPI fragments, they describe a closed service.", "Map PlayDialog or Play 3.0 Mini work to another TTS listing before writing code." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 1, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 4.1 } ], "editorialScores": { "ergonomics": 0, "maintenance": 0, "payments": 0, "reliability": 0, "schema": 31, "security": 0, "transparency": 5 }, "provenanceScore": 65, "checked": { "categories": { "ergonomics": "2026-10-17", "maintenance": "2026-10-17", "payments": "2026-10-17", "reliability": "2026-10-17", "schema": "2026-10-17", "security": "2026-10-17", "transparency": "2026-10-17" }, "last": "2026-10-17", "lastMoved": "2026-10-27", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "# Retired. api.play.ht no longer resolves.\ncurl -X POST https://api.play.ht/api/v2/tts/stream -H \"X-USER-ID: $PLAYHT_USER_ID\" -H \"AUTHORIZATION: $PLAYHT_API_KEY\" \\\n -H \"content-type: application/json\" -H \"accept: audio/mpeg\" -d '{\"text\":\"Hello\",\"voice_engine\":\"PlayDialog\"}'" }, "letme": { "capability": "https://letme.dev/speech.tts", "tool": "https://letme.dev/playht-tts" }, "sameCompany": [ "playht-voice-cloning" ], "area": "voice", "retired": "2025-12-31", "provenance": { "legalEntity": "PlayHT, Inc.", "domain": "play.ht", "domainRegistered": "2016-11-29", "endpointOnVendorDomain": true, "terms": "https://web.archive.org/web/20250222123504/https://play.ht/terms/", "privacy": "https://web.archive.org/web/20250202131353/https://play.ht/privacy/", "statusPage": "", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-17", "notes": [ "On 2026-10-17 play.ht and api.play.ht didn't resolve from our network, while docs.play.ht still served the API reference, Markdown copies with OpenAPI fragments and an llms.txt, with no shutdown notice", "On 2026-10-01 a fetch of play.ht returned the old marketing page, so the domain may resolve for some networks or that fetch came from a cache", "Terms and privacy links point to Internet Archive copies from February 2025" ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/playht-tts.json" }, "edges": [ { "by": 75, "category": "reliability", "leads": "minimax-speech", "name": "Reliability", "reasons": { "a": "Atlassian Statuspage at status.minimax.io with a Text-to-Speech component (20). Its history, re-read on 6 November, shows three incidents in the 90 days from 8 August, all titled elevated errors and labelled major, 22 minutes on 28 September, 3 minutes on 16 October and 2 minutes on 19 October, and none in November. Elevated errors with no fuller scope are read as partial, as on minimax-api and minimax-voice-cloning, so minor only (20). T2A is limited to 60 requests a minute, with higher limits on audio subscriptions (15). Error codes 1002 and 2045 say to retry later and avoid sudden increases, with no Retry-After or backoff figures (10 of 15). No SLA (0). No beta or preview label on T2A (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.", "b": "Retired. On 2026-10-17 api.play.ht and play.ht didn't resolve, so nothing answers a call. Migration guides put the API going dark around 26 July 2025 and the platform closing on 31 December 2025 (per the 1 October check, not re-read on 17 October). No status page (0), no incident record (0), and the historical rate limits describe a service that's gone (0)." }, "scores": { "a": 75, "b": 0 } }, { "by": 56, "category": "ergonomics", "leads": "minimax-speech", "name": "Agent ergonomics", "reasons": { "a": "API reading of the checklist. Audio comes back hex-encoded inside JSON by default, with subtitles opt-in and format, bitrate and sample rate settable (15 of 25). Voices are listed by type through `POST /v1/get_voice`, which has no pagination and returns 300+ system voices for `all` (10 of 20). Errors come as numeric codes in `base_resp` with a short remedy for each, inside responses documented only as 200 (13 of 20). No idempotency key, and the MCP tools carry no read-only or destructive annotations (10 of 20). Two required fields. No official SDK for speech, with MCP servers in Python and JavaScript (8 of 15). Total 56.", "b": "No live surface to call, so every line scores 0." }, "scores": { "a": 56, "b": 0 } }, { "by": 50, "category": "schema", "leads": "minimax-speech", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 for the sync and async routes and AsyncAPI files for the WebSocket and bidirectional sockets (25). llms.txt and a Markdown copy of every page (10). The text field says when to stream and how to mark pauses, and guides separate sync, WebSocket and async use (15 of 20). Enums for model and audio settings, with `model` and `text` required (13 of 15). Examples throughout and the shared table of error codes, but the OpenAPI file documents only a 200 response (10 of 15). Versioned `/v1` paths. The API release notes stop at 28 October 2025, and the last T2A entry is 23 September 2025 (8 of 15). Total 81.", "b": "What's left is the docs, still served at docs.play.ht with pages last updated on 9 September 2025 and no shutdown notice. The Markdown copy of each reference page embeds an OpenAPI 3.0.3 fragment for its one operation, with typed enums and seven response codes on the streaming endpoint, and an llms.txt indexes the guides and reference pages as Markdown. Both point at https://api.play.ht, which no longer resolves, and describe the API as live. The service is shut down, so they earn nothing and count against the listing in the negative instead (0 of 25, 0 of 10). The getting-started and streaming pages state purpose and limits (8 of 20). Typed request fields with engine names and a 20,000-character streaming cap (10 of 15). Response codes and examples on the reference pages (8 of 15). Versioned `/api/v2` path, and docs.play.ht/changelog returns 404 (5 of 15). Total 31. A model reading these pages or the llms.txt would call an API that doesn't exist." }, "scores": { "a": 81, "b": 31 } }, { "by": 38, "category": "maintenance", "leads": "minimax-speech", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a model, as minimax-voice-cloning is. The newest dated change touching speech is the MCP servers' August update, `minimax-mcp-js` 0.0.18 on 21 August 2026, 77 days before 6 November, and Speech 2.8 dates from 23 January 2026 (20 of 30). No dated API entries in the last 90 days (0). Support by email and Discord, not tested (6 of 15). No official SDK for speech; the MCP servers expose `text_to_audio` and `list_voices` (8 of 15). The Python MCP server has tests and moved to version 2 of the MCP SDK in August, with no CI workflow (4 of 10). Total 38.", "b": "No release or changelog entry in the last 90 days or the last year (0). No support channel (0). SDKs abandoned (0). No package health to judge (0)." }, "scores": { "a": 38, "b": 0 } }, { "by": 36, "category": "security", "leads": "minimax-speech", "name": "Security \u0026 auth", "reasons": { "a": "Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain API keys with no scopes found, and leaked keys may be disabled (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). The speech docs call every interface stateless, and no retention period for submitted text or generated audio was found (5 of 15). Responses carry `usage_characters` and a trace ID, with no audit log (6 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). Total 36.", "b": "No live surface. Historically a secret key plus a user ID in two headers, with no scopes. Accounts, audio and clones were reportedly deleted at shutdown with no export. Nothing left to score (0)." }, "scores": { "a": 36, "b": 0 } }, { "by": 30, "category": "transparency", "leads": "minimax-speech", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed API with clear terms under Singapore law naming Nanonoble Pte. Ltd., and MIT MCP servers (15 of 30). 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, as on minimax-voice-cloning (8 of 30). The API release notes carry a dated legacy notice of 20 June 2025 for the old text-to-voice API with service continuing, and older speech models stay accepted, with no written policy or notice period (15 of 20). Data location stated as the United States and an EU representative named, third parties only by category (10 of 20). Total 48.", "b": "SDKs remain on GitHub under Apache-2.0, while the terms survive only as Internet Archive copies (5 of 30). No live privacy policy or retention statement, and the deletion of data at shutdown is reported by third parties, not by PlayHT (0 of 30). We found no shutdown notice from PlayHT on the live site or docs today (0 of 20). No sub-processors or data locations (0 of 20)." }, "scores": { "a": 65, "b": 35 } } ], "facts": [ { "a": "Model API", "b": "Model API", "name": "Kind" }, { "a": "MiniMax", "b": "PlayHT", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.play.ht/api/v2", "name": "Hosted endpoint" }, { "a": "HTTP, websocket", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Apache-2.0 (Python SDK)", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-01-23", "b": "2025-05-21", "name": "Last release" }, { "a": "couldn't be read", "b": "2023-06-01", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2021-06-19", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "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": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "218 stars, 14k npm/wk, 6.6k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "1/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "MiniMax Speech (T2A) scores 55.1 (C) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category.", "question": "Which is better for AI agents, MiniMax Speech (T2A) or PlayHT Text-to-Speech API?" }, { "answer": "Both need an API key.", "question": "Do MiniMax Speech (T2A) and PlayHT Text-to-Speech API need an API key?" }, { "answer": "No hosted endpoint is listed for MiniMax Speech (T2A). PlayHT Text-to-Speech API has a hosted endpoint at https://api.play.ht/api/v2.", "question": "Can an agent call MiniMax Speech (T2A) and PlayHT Text-to-Speech API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 0", "Schema \u0026 documentation, 81 against 31", "Agent ergonomics, 56 against 0", "Security \u0026 auth, 36 against 0", "Payments \u0026 pricing, 20 against 0", "Maintenance \u0026 community, 38 against 0", "Transparency \u0026 trust, 65 against 35" ], "also": [ "Still running. PlayHT Text-to-Speech API has shut down", "No incidents deducted, where PlayHT Text-to-Speech API loses 4 points for them" ], "goodFor": "Multilingual speech for narration and agents at mid-range prices, with strong Chinese voices by the vendor's account.", "slug": "minimax-speech", "watchFor": "No free allowance for synthesis and no official SDK" }, { "aheadOn": null, "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Nothing new. It shut down on 2025-12-31.", "slug": "playht-tts", "watchFor": "api.play.ht doesn't resolve, so every call fails" } ], "history": { "minimax-speech": null, "playht-tts": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 3.9, "fromGrade": "F", "to": 4.1, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 4.2, "fromGrade": "F", "to": 3.9, "toGrade": "F" } ] }, "job": { "capability": "speech.tts", "name": "Text-to-speech" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-polly-vs-minimax-speech.json", "title": "Amazon Polly vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/amazon-polly-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/amazon-polly-vs-playht-tts.json", "title": "Amazon Polly vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/amazon-polly-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.json", "title": "Azure AI Speech text-to-speech vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-playht-tts.json", "title": "Azure AI Speech text-to-speech vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/cartesia-tts-vs-minimax-speech.json", "title": "Cartesia Sonic TTS API + MCP vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/cartesia-tts-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/cartesia-tts-vs-playht-tts.json", "title": "Cartesia Sonic TTS API + MCP vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/cartesia-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech.json", "title": "Deepgram Text-to-Speech (Aura-2, Flux TTS) vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/deepgram-tts-vs-playht-tts.json", "title": "Deepgram Text-to-Speech (Aura-2, Flux TTS) vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/deepgram-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-tts-vs-minimax-speech.json", "title": "ElevenLabs Text to Speech API + MCP vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/elevenlabs-tts-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-tts-vs-playht-tts.json", "title": "ElevenLabs Text to Speech API + MCP vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/elevenlabs-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/fish-audio-tts-vs-minimax-speech.json", "title": "Fish Audio TTS API vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/fish-audio-tts-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/fish-audio-tts-vs-playht-tts.json", "title": "Fish Audio TTS API vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/fish-audio-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.json", "title": "Google Cloud Text-to-Speech vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.json", "title": "Google Cloud Text-to-Speech vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/heygen-voice-vs-minimax-speech.json", "title": "HeyGen Voice vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/heygen-voice-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/heygen-voice-vs-playht-tts.json", "title": "HeyGen Voice vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/heygen-voice-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/inworld-tts-vs-minimax-speech.json", "title": "Inworld Realtime TTS-2 vs MiniMax Speech (T2A)", "url": "https://www.anchorterminal.com/compare/inworld-tts-vs-minimax-speech" }, { "json": "https://www.anchorterminal.com/compare/inworld-tts-vs-playht-tts.json", "title": "Inworld Realtime TTS-2 vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/inworld-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/minimax-speech-vs-murf-tts.json", "title": "MiniMax Speech (T2A) vs Murf TTS API + MCP", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-murf-tts" }, { "json": "https://www.anchorterminal.com/compare/minimax-speech-vs-resemble-ai-tts.json", "title": "MiniMax Speech (T2A) vs Resemble AI Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-resemble-ai-tts" }, { "json": "https://www.anchorterminal.com/compare/minimax-speech-vs-rime-tts.json", "title": "MiniMax Speech (T2A) vs Rime TTS API + MCP", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-rime-tts" }, { "json": "https://www.anchorterminal.com/compare/minimax-speech-vs-smallest-lightning-tts.json", "title": "MiniMax Speech (T2A) vs Smallest.ai Lightning TTS", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-smallest-lightning-tts" }, { "json": "https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts.json", "title": "MiniMax Speech (T2A) vs Soniox Text-to-Speech", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts" }, { "json": "https://www.anchorterminal.com/compare/murf-tts-vs-playht-tts.json", "title": "Murf TTS API + MCP vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/murf-tts-vs-playht-tts" }, { "json": "https://www.anchorterminal.com/compare/playht-tts-vs-resemble-ai-tts.json", "title": "PlayHT Text-to-Speech API vs Resemble AI Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/playht-tts-vs-resemble-ai-tts" }, { "json": "https://www.anchorterminal.com/compare/playht-tts-vs-rime-tts.json", "title": "PlayHT Text-to-Speech API vs Rime TTS API + MCP", "url": "https://www.anchorterminal.com/compare/playht-tts-vs-rime-tts" }, { "json": "https://www.anchorterminal.com/compare/playht-tts-vs-smallest-lightning-tts.json", "title": "PlayHT Text-to-Speech API vs Smallest.ai Lightning TTS", "url": "https://www.anchorterminal.com/compare/playht-tts-vs-smallest-lightning-tts" }, { "json": "https://www.anchorterminal.com/compare/playht-tts-vs-soniox-tts.json", "title": "PlayHT Text-to-Speech API vs Soniox Text-to-Speech", "url": "https://www.anchorterminal.com/compare/playht-tts-vs-soniox-tts" } ], "panel": null, "scores": [ { "by": 75, "edge": "minimax-speech", "key": "reliability", "minimax-speech": 75, "name": "Reliability", "playht-tts": 0, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 50, "edge": "minimax-speech", "key": "schema", "minimax-speech": 81, "name": "Schema \u0026 documentation", "playht-tts": 31, "weight": 13 }, { "by": 56, "edge": "minimax-speech", "key": "ergonomics", "minimax-speech": 56, "name": "Agent ergonomics", "playht-tts": 0, "weight": 13 }, { "by": 36, "edge": "minimax-speech", "key": "security", "minimax-speech": 36, "name": "Security \u0026 auth", "playht-tts": 0, "weight": 14 }, { "by": 20, "edge": "minimax-speech", "key": "payments", "minimax-speech": 20, "name": "Payments \u0026 pricing", "playht-tts": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 38, "edge": "minimax-speech", "key": "maintenance", "minimax-speech": 38, "name": "Maintenance \u0026 community", "playht-tts": 0, "weight": 7 }, { "by": 30, "edge": "minimax-speech", "key": "transparency", "minimax-speech": 65, "name": "Transparency \u0026 trust", "playht-tts": 35, "weight": 7 } ], "summary": "PlayHT Text-to-Speech API shut down on 2025-12-31. MiniMax Speech (T2A) scores 55.1 (C) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category. Both do text-to-speech.", "tasks": null, "tutorials": [], "verdicts": { "minimax-speech": "MiniMax's speech API covers sync, WebSocket, bidirectional and async synthesis with OpenAPI and AsyncAPI files and public prices of $60 to $100 per million characters. Text-to-Speech had only short incidents in 90 days. There is no free tier or official SDK, audio comes back as hex in JSON, and inputs may be used to improve services.", "playht-tts": "The old API reference is still readable at docs.play.ht for anyone porting code. api.play.ht doesn't resolve, so every call fails." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts", "json": "https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.min.md" }, "markdown": "PlayHT Text-to-Speech API shut down on 2025-12-31. MiniMax Speech (T2A) scores 55.1 (C) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category. Both do text-to-speech.\n\n- MiniMax Speech (T2A): grade C, 55.1/100, rank #884 of 1510. Markdown https://www.anchorterminal.com/tools/minimax-speech.md · JSON https://www.anchorterminal.com/api/v1/tools/minimax-speech.json\n- PlayHT Text-to-Speech API: grade F, 4.1/100, rank retired, not ranked. Markdown https://www.anchorterminal.com/tools/playht-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/playht-tts.json\n- Best text-to-speech APIs for AI agents: https://www.anchorterminal.com/best/text-to-speech/index.md\n- All 148 tts comparisons: https://www.anchorterminal.com/compare/text-to-speech/index.md\n\n## Which one, for what\n\n### MiniMax Speech (T2A) (C)\n\nGood for: Multilingual speech for narration and agents at mid-range prices, with strong Chinese voices by the vendor's account.\n\nAhead on:\n- Reliability, 75 against 0\n- Schema \u0026 documentation, 81 against 31\n- Agent ergonomics, 56 against 0\n- Security \u0026 auth, 36 against 0\n- Payments \u0026 pricing, 20 against 0\n- Maintenance \u0026 community, 38 against 0\n- Transparency \u0026 trust, 65 against 35\n\nAlso in its favour:\n- Still running. PlayHT Text-to-Speech API has shut down\n- No incidents deducted, where PlayHT Text-to-Speech API loses 4 points for them\n\nWatch for: No free allowance for synthesis and no official SDK\n\n### PlayHT Text-to-Speech API (F)\n\nGood for: Nothing new. It shut down on 2025-12-31.\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: api.play.ht doesn't resolve, so every call fails\n\n\n## Why the edge\n\n### Reliability: MiniMax Speech (T2A) +75\n\n- MiniMax Speech (T2A) (75): Atlassian Statuspage at status.minimax.io with a Text-to-Speech component (20). Its history, re-read on 6 November, shows three incidents in the 90 days from 8 August, all titled elevated errors and labelled major, 22 minutes on 28 September, 3 minutes on 16 October and 2 minutes on 19 October, and none in November. Elevated errors with no fuller scope are read as partial, as on minimax-api and minimax-voice-cloning, so minor only (20). T2A is limited to 60 requests a minute, with higher limits on audio subscriptions (15). Error codes 1002 and 2045 say to retry later and avoid sudden increases, with no Retry-After or backoff figures (10 of 15). No SLA (0). No beta or preview label on T2A (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.\n- PlayHT Text-to-Speech API (0): Retired. On 2026-10-17 api.play.ht and play.ht didn't resolve, so nothing answers a call. Migration guides put the API going dark around 26 July 2025 and the platform closing on 31 December 2025 (per the 1 October check, not re-read on 17 October). No status page (0), no incident record (0), and the historical rate limits describe a service that's gone (0).\n\n### Agent ergonomics: MiniMax Speech (T2A) +56\n\n- MiniMax Speech (T2A) (56): API reading of the checklist. Audio comes back hex-encoded inside JSON by default, with subtitles opt-in and format, bitrate and sample rate settable (15 of 25). Voices are listed by type through `POST /v1/get_voice`, which has no pagination and returns 300+ system voices for `all` (10 of 20). Errors come as numeric codes in `base_resp` with a short remedy for each, inside responses documented only as 200 (13 of 20). No idempotency key, and the MCP tools carry no read-only or destructive annotations (10 of 20). Two required fields. No official SDK for speech, with MCP servers in Python and JavaScript (8 of 15). Total 56.\n- PlayHT Text-to-Speech API (0): No live surface to call, so every line scores 0.\n\n### Schema \u0026 documentation: MiniMax Speech (T2A) +50\n\n- MiniMax Speech (T2A) (81): OpenAPI 3.1 for the sync and async routes and AsyncAPI files for the WebSocket and bidirectional sockets (25). llms.txt and a Markdown copy of every page (10). The text field says when to stream and how to mark pauses, and guides separate sync, WebSocket and async use (15 of 20). Enums for model and audio settings, with `model` and `text` required (13 of 15). Examples throughout and the shared table of error codes, but the OpenAPI file documents only a 200 response (10 of 15). Versioned `/v1` paths. The API release notes stop at 28 October 2025, and the last T2A entry is 23 September 2025 (8 of 15). Total 81.\n- PlayHT Text-to-Speech API (31): What's left is the docs, still served at docs.play.ht with pages last updated on 9 September 2025 and no shutdown notice. The Markdown copy of each reference page embeds an OpenAPI 3.0.3 fragment for its one operation, with typed enums and seven response codes on the streaming endpoint, and an llms.txt indexes the guides and reference pages as Markdown. Both point at https://api.play.ht, which no longer resolves, and describe the API as live. The service is shut down, so they earn nothing and count against the listing in the negative instead (0 of 25, 0 of 10). The getting-started and streaming pages state purpose and limits (8 of 20). Typed request fields with engine names and a 20,000-character streaming cap (10 of 15). Response codes and examples on the reference pages (8 of 15). Versioned `/api/v2` path, and docs.play.ht/changelog returns 404 (5 of 15). Total 31. A model reading these pages or the llms.txt would call an API that doesn't exist.\n\n### Maintenance \u0026 community: MiniMax Speech (T2A) +38\n\n- MiniMax Speech (T2A) (38): Read as a model, as minimax-voice-cloning is. The newest dated change touching speech is the MCP servers' August update, `minimax-mcp-js` 0.0.18 on 21 August 2026, 77 days before 6 November, and Speech 2.8 dates from 23 January 2026 (20 of 30). No dated API entries in the last 90 days (0). Support by email and Discord, not tested (6 of 15). No official SDK for speech; the MCP servers expose `text_to_audio` and `list_voices` (8 of 15). The Python MCP server has tests and moved to version 2 of the MCP SDK in August, with no CI workflow (4 of 10). Total 38.\n- PlayHT Text-to-Speech API (0): No release or changelog entry in the last 90 days or the last year (0). No support channel (0). SDKs abandoned (0). No package health to judge (0).\n\n### Security \u0026 auth: MiniMax Speech (T2A) +36\n\n- MiniMax Speech (T2A) (36): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain API keys with no scopes found, and leaked keys may be disabled (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). The speech docs call every interface stateless, and no retention period for submitted text or generated audio was found (5 of 15). Responses carry `usage_characters` and a trace ID, with no audit log (6 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). Total 36.\n- PlayHT Text-to-Speech API (0): No live surface. Historically a secret key plus a user ID in two headers, with no scopes. Accounts, audio and clones were reportedly deleted at shutdown with no export. Nothing left to score (0).\n\n### Transparency \u0026 trust: MiniMax Speech (T2A) +30\n\n- MiniMax Speech (T2A) (65): Closed API with clear terms under Singapore law naming Nanonoble Pte. Ltd., and MIT MCP servers (15 of 30). 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, as on minimax-voice-cloning (8 of 30). The API release notes carry a dated legacy notice of 20 June 2025 for the old text-to-voice API with service continuing, and older speech models stay accepted, with no written policy or notice period (15 of 20). Data location stated as the United States and an EU representative named, third parties only by category (10 of 20). Total 48.\n- PlayHT Text-to-Speech API (35): SDKs remain on GitHub under Apache-2.0, while the terms survive only as Internet Archive copies (5 of 30). No live privacy policy or retention statement, and the deletion of data at shutdown is reported by third parties, not by PlayHT (0 of 30). We found no shutdown notice from PlayHT on the live site or docs today (0 of 20). No sub-processors or data locations (0 of 20).\n\n## Score by category\n\n| Category | Weight | MiniMax Speech (T2A) | PlayHT Text-to-Speech API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 0 | MiniMax Speech (T2A) +75 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 31 | MiniMax Speech (T2A) +50 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 0 | MiniMax Speech (T2A) +56 |\n| Security \u0026 auth | 14% (17.5 this run) | 36 | 0 | MiniMax Speech (T2A) +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 0 | MiniMax Speech (T2A) +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 38 | 0 | MiniMax Speech (T2A) +38 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 65 | 35 | MiniMax Speech (T2A) +30 |\n| Negative events | ≤15 | 0 | -4 | |\n| **Total** | | **55.1 · C** | **4.1 · F** | |\n\n## Facts side by side\n\n| Fact | MiniMax Speech (T2A) | PlayHT Text-to-Speech API |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | MiniMax | PlayHT |\n| Hosted endpoint | no (local only) | `https://api.play.ht/api/v2` |\n| Transports | HTTP, websocket | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | none | Apache-2.0 (Python SDK) |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-01-23 | 2025-05-21 |\n| Terms last updated | couldn't be read | 2023-06-01 |\n| Privacy policy last updated | couldn't be read | 2021-06-19 |\n| Customer content may train models | couldn't be read | 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 | yes |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | none | 218 stars, 14k npm/wk, 6.6k PyPI/wk |\n| Agent reviews | none | 1/5 (2) |\n\n## How the scores have moved\n\n### MiniMax Speech (T2A)\n\nNo score change since it was listed.\n\n### PlayHT Text-to-Speech API\n\n- +0.2 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n\n## Verdicts\n\n**MiniMax Speech (T2A).** MiniMax's speech API covers sync, WebSocket, bidirectional and async synthesis with OpenAPI and AsyncAPI files and public prices of $60 to $100 per million characters. Text-to-Speech had only short incidents in 90 days. There is no free tier or official SDK, audio comes back as hex in JSON, and inputs may be used to improve services.\n\n**PlayHT Text-to-Speech API.** The old API reference is still readable at docs.play.ht for anyone porting code. api.play.ht doesn't resolve, so every call fails.\n\n## Before you call either\n\n### MiniMax Speech (T2A)\n\n1. Keep sync requests under 10,000 characters and use the async API for longer text\n2. Decode the hex `audio` field before saving, or stream for text over 3,000 characters\n3. Check `base_resp.status_code` on every response, since errors arrive inside a 200\n4. Stay under 60 requests a minute and back off on code 1002\n5. Use speech-2.8-turbo for agents and HD only where quality matters, since HD costs two thirds more\n\n### PlayHT Text-to-Speech API\n\n1. Don't call api.play.ht, it doesn't resolve.\n2. Ignore docs.play.ht code samples, its llms.txt and the OpenAPI fragments, they describe a closed service.\n3. Map PlayDialog or Play 3.0 Mini work to another TTS listing before writing code.\n\n## Questions\n\n### Which is better for AI agents, MiniMax Speech (T2A) or PlayHT Text-to-Speech API?\n\nMiniMax Speech (T2A) scores 55.1 (C) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category.\n\n### Do MiniMax Speech (T2A) and PlayHT Text-to-Speech API need an API key?\n\nBoth need an API key.\n\n### Can an agent call MiniMax Speech (T2A) and PlayHT Text-to-Speech API without installing anything?\n\nNo hosted endpoint is listed for MiniMax Speech (T2A). PlayHT Text-to-Speech API has a hosted endpoint at https://api.play.ht/api/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.json, and with the fewest tokens: https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"minimax-speech\", \"b\": \"playht-tts\"}`. From a terminal: `anchor compare minimax-speech playht-tts`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/minimax-speech.json and https://www.anchorterminal.com/api/v1/tools/playht-tts.json\n\n## Other comparisons with MiniMax Speech (T2A) or PlayHT Text-to-Speech API\n\n- [Amazon Polly vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/amazon-polly-vs-minimax-speech.md)\n- [Amazon Polly vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/amazon-polly-vs-playht-tts.md)\n- [Azure AI Speech text-to-speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.md)\n- [Azure AI Speech text-to-speech vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-playht-tts.md)\n- [Cartesia Sonic TTS API + MCP vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/cartesia-tts-vs-minimax-speech.md)\n- [Cartesia Sonic TTS API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/cartesia-tts-vs-playht-tts.md)\n- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/deepgram-tts-vs-minimax-speech.md)\n- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/deepgram-tts-vs-playht-tts.md)\n- [ElevenLabs Text to Speech API + MCP vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-minimax-speech.md)\n- [ElevenLabs Text to Speech API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-playht-tts.md)\n- [Fish Audio TTS API vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/fish-audio-tts-vs-minimax-speech.md)\n- [Fish Audio TTS API vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/fish-audio-tts-vs-playht-tts.md)\n- [Google Cloud Text-to-Speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.md)\n- [Google Cloud Text-to-Speech vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.md)\n- [HeyGen Voice vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/heygen-voice-vs-minimax-speech.md)\n- [HeyGen Voice vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/heygen-voice-vs-playht-tts.md)\n- [Inworld Realtime TTS-2 vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/inworld-tts-vs-minimax-speech.md)\n- [Inworld Realtime TTS-2 vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/inworld-tts-vs-playht-tts.md)\n- [MiniMax Speech (T2A) vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/minimax-speech-vs-murf-tts.md)\n- [MiniMax Speech (T2A) vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/minimax-speech-vs-resemble-ai-tts.md)\n- [MiniMax Speech (T2A) vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/minimax-speech-vs-rime-tts.md)\n- [MiniMax Speech (T2A) vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/minimax-speech-vs-smallest-lightning-tts.md)\n- [MiniMax Speech (T2A) vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/minimax-speech-vs-soniox-tts.md)\n- [Murf TTS API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/murf-tts-vs-playht-tts.md)\n- [PlayHT Text-to-Speech API vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/playht-tts-vs-resemble-ai-tts.md)\n- [PlayHT Text-to-Speech API vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/playht-tts-vs-rime-tts.md)\n- [PlayHT Text-to-Speech API vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/playht-tts-vs-smallest-lightning-tts.md)\n- [PlayHT Text-to-Speech API vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/playht-tts-vs-soniox-tts.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": "MiniMax Speech (T2A) vs PlayHT Text-to-Speech API", "url": "" } ], "description": "MiniMax Speech scores 55.1 (C) to PlayHT Text-to-Speech's 4.1 (F) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MiniMax Speech (T2A) C 55.1", "PlayHT Text-to-Speech API F 4.1", "scores" ], "h1": "MiniMax Speech (T2A) vs PlayHT Text-to-Speech API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/minimax-speech-vs-playht-tts", "published": "2026-10-01", "section": "tools", "title": "MiniMax Speech vs PlayHT Text-to-Speech for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts" }, "tokens": { "markdown": 4350, "slim": 2430 }, "version": 1 }