{ "data": { "a": { "slug": "azure-text-to-speech", "name": "Azure AI Speech text-to-speech", "vendor": "Microsoft", "vendorUrl": "https://azure.microsoft.com/en-us/products/ai-services/text-to-speech", "kind": "model", "category": "text-to-speech", "summary": "Azure's text-to-speech service for generating spoken audio.", "url": "https://www.anchorterminal.com/tools/azure-text-to-speech", "markdownUrl": "https://www.anchorterminal.com/tools/azure-text-to-speech.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-text-to-speech.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-text-to-speech.json", "dns": "azure-text-to-speech.grade.anchorterminal.com", "repo": "https://github.com/Azure-Samples/cognitive-services-speech-sdk", "license": "MIT (samples), SDK under Microsoft's own licence", "transports": [ "http" ], "remoteUrl": "https://eastus.tts.speech.microsoft.com/cognitiveservices", "packages": [ { "registry": "pypi", "name": "azure-cognitiveservices-speech" }, { "registry": "npm", "name": "microsoft-cognitiveservices-speech-sdk" } ], "auth": "mixed", "authNotes": "`Ocp-Apim-Subscription-Key` header with a Speech resource key, or a Microsoft Entra ID bearer token. Endpoints are per region.", "pricing": "freemium", "pricingNotes": "Free F0 tier with 500,000 characters a month. Pay as you go in East US is $15 per 1M characters for Neural and Neural HD Flash voices and $22 for Neural HD, real time or batch. Commitment tiers from $960 a month for 80M characters (https://azure.microsoft.com/en-us/pricing/details/speech/). Microsoft AI lists MAI-Voice-2.1 at $22 and MAI-Voice-2.1-Flash at $15 per 1M characters in preview (https://microsoft.ai/models/mai-voice-2-1/).", "priceSummary": "$960 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No machine payment. Billing runs through a cloud account with a card or invoice.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 3450, "npmWeekly": 475621, "pypiWeekly": 1032532, "asOf": "2026-09-30" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/text-to-speech", "capabilities": [ "speech.tts", "speech.streaming", "speech.voices", "speech.ssml", "speech.languages" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "python", "typescript", "enterprise", "streaming", "batch", "async-jobs" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 71.5, "grade": "BB", "agentReady": true, "rank": 157, "ranked": true, "rankOf": 1486, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 80, "schema": 65, "security": 90, "transparency": 86 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-05" }, "negative": 0, "verdict": "Real-time synthesis keeps neither the input text nor the output audio. An Azure subscription needs a card, even for the free F0 tier.", "bestFor": "Operators on Azure who need SSML control, many languages and voices, and enterprise access control.", "strengths": [ "Real-time synthesis keeps neither the input text nor the output audio", "Full SSML with speaking styles, prosody, phonemes, lexicons and up to 50 voice or audio tags a request", "Microsoft Entra ID with role-based access, or two rotatable keys", "Covered by Microsoft's online services SLA", "S0 starts at 30 requests a second and can be raised to 1,000" ], "weaknesses": [ "An Azure subscription needs a card, even for the free F0 tier", "No llms.txt and no OpenAPI file for text-to-speech found", "429s often reflect busy capacity for a voice in a region, which a quota increase doesn't fix", "The voice list comes back as one response per region with no paging documented", "MAI-Voice-2.1 and MAI-Voice-2.1-Flash, Microsoft's newest models, are public preview with no SLA" ], "agentNotes": [ "Send SSML with `\u003cspeak\u003e` and `\u003cvoice\u003e`, and set `X-Microsoft-OutputFormat` and `User-Agent`.", "On 429 retry with backoff, and try the voice's home region or another region rather than asking for more quota.", "Keep each real-time request under 10 minutes of audio, or use batch synthesis.", "Use Entra ID tokens instead of resource keys where the agent runs inside Azure.", "Name a MAI voice with its model suffix, such as `en-US-Harper:MAI-Voice-2.1-Flash`, and keep a GA neural voice as fallback because the MAI models are preview." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.5 } ], "editorialScores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 80, "schema": 65, "security": 90, "transparency": 80 }, "provenanceScore": 91, "checked": { "categories": { "ergonomics": "2026-10-05", "maintenance": "2026-10-05", "payments": "2026-10-05", "reliability": "2026-10-05", "schema": "2026-10-05", "security": "2026-10-05", "transparency": "2026-10-05" }, "last": "2026-10-05", "lastMoved": "2026-10-27", "oldest": "2026-10-05", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install azure-cognitiveservices-speech # or: npm i microsoft-cognitiveservices-speech-sdk", "http": "curl -X POST \"https://eastus.tts.speech.microsoft.com/cognitiveservices/v1\" \\\n -H \"Ocp-Apim-Subscription-Key: $AZURE_SPEECH_KEY\" -H \"Content-Type: application/ssml+xml\" \\\n -H \"X-Microsoft-OutputFormat: audio-24khz-48kbitrate-mono-mp3\" -o speech.mp3 \\\n -d '\u003cspeak version=\"1.0\" xml:lang=\"en-US\"\u003e\u003cvoice name=\"en-US-AvaMultilingualNeural\"\u003eYour table is booked for seven.\u003c/voice\u003e\u003c/speak\u003e'" }, "letme": { "capability": "https://letme.dev/speech.tts", "tool": "https://letme.dev/azure-text-to-speech" }, "sameCompany": [ "azure-openai", "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "bing-grounding", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "voice", "unitPrices": [ { "item": "Neural and Neural HD Flash voices", "unit": "1m-chars", "usd": 15, "note": "real time or batch, East US" }, { "item": "Neural HD voices", "unit": "1m-chars", "usd": 22 }, { "item": "Commitment tier 80M characters", "unit": "month", "usd": 960, "note": "$12 per 1M overage" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Endpoints are on speech.microsoft.com, api.cognitive.microsoft.com and cognitiveservices.azure.com. microsoft.com publishes a security.txt, but it passed its Expires date on 2026-09-23.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/releasenotes", "securityTxt": "expired", "checked": "2026-09-30", "score": 91 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-text-to-speech.json", "live": { "slug": "azure-text-to-speech", "probe": { "target": "https://eastus.tts.speech.microsoft.com/cognitiveservices", "method": "get", "lastAt": "2026-11-07T18:20:12.223615011Z", "lastOk": true, "lastStatus": 404, "lastMs": 322, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 268, "p95ms24h": 358, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "github", "name": "Azure-Samples/cognitive-services-speech-sdk", "version": "ingestion-v2.1.13", "released": "2026-07-10", "seenAt": "2026-11-06T23:09:37.913134624Z" }, { "registry": "npm", "name": "microsoft-cognitiveservices-speech-sdk", "version": "1.53.0", "seenAt": "2026-11-06T23:09:37.879130417Z" }, { "registry": "pypi", "name": "azure-cognitiveservices-speech", "version": "1.53.0", "released": "2026-10-21", "seenAt": "2026-11-06T23:09:37.772566763Z" } ], "githubStars": 3457, "npmWeekly": 666362, "pypiWeekly": 623310, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "domain": { "domain": "microsoft.com", "registered": "1991-05-02", "source": "https://rdap.verisign.com/com/v1/domain/microsoft.com", "checkedAt": "2026-11-01T14:14:19.336136409Z" }, "github": { "repo": "azure-samples/cognitive-services-speech-sdk", "checkedAt": "2026-11-02T08:33:46.314203025Z", "stars": 3457, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T08:28:26Z", "openIssues": 2, "openPRs": 44, "issuesOpened90d": 22, "issuesClosed90d": 24, "prsMerged90d": 12, "ci": { "branch": "master", "runs": 4, "success": 1, "failure": 3, "other": 0, "latest": "failure", "latestAt": "2026-10-23T22:25:20Z" }, "replies": { "sampled": 25, "unanswered": 1, "medianDays": 1 } }, "updatedAt": "2026-11-07T18:20:12.223615011Z" } }, "answer": "Azure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 5 of 7 scored categories. MiniMax Speech (T2A) leads on schema \u0026 documentation.", "b": { "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": 879, "ranked": true, "rankOf": 1486, "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-07T18:21:22.955290584Z" }, "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-07T18:21:22.955290584Z" } }, "edges": [ { "by": 54, "category": "security", "leads": "azure-text-to-speech", "name": "Security \u0026 auth", "reasons": { "a": "Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access (30). Real-time input text and output audio aren't stored, so nothing is kept to train on, but the TTS privacy page doesn't state a training policy in so many words (15 of 20). Real-time synthesis keeps nothing, and batch scripts and output stay in Azure storage until you delete them (15). Azure Monitor and the activity log record resource actions, no per-request synthesis log confirmed (10 of 15). MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports and public advisories. The microsoft.com security.txt still carries an Expires date of 2026-09-23 on 5 October (20).", "b": "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." }, "scores": { "a": 90, "b": 36 } }, { "by": 42, "category": "maintenance", "leads": "azure-text-to-speech", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a model. MAI-Voice-2.1 and MAI-Voice-2.1-Flash entered public preview on 1 October 2026, and Speech SDK 1.52.0 shipped on npm and PyPI on 28 September 2026 (30). Speech release notes for July, August and September 2026. The TTS release notes don't list MAI-Voice-2.1 yet (10). Retirements follow Microsoft's published lifecycle policy with dated notices. The MAI model has turned over three times since March 2026 (MAI-Voice-1, MAI-Voice-2-Flash, MAI-Voice-2.1), and the MAI page dropped MAI-Voice-2-Flash without a dated notice, though the language list still carries it as preview (10). Public release notes and Microsoft Q\u0026A, SDK issue tracker not checked (10 of 25). Speech SDK current in eight languages (15). The SDK is a closed binary, so we can't see its CI (5 of 10).", "b": "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." }, "scores": { "a": 80, "b": 38 } }, { "by": 21, "category": "transparency", "leads": "azure-text-to-speech", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Microsoft's product terms, with an MIT samples repository (15). The TTS privacy page, the privacy statement and the product terms agree on no storage for real-time synthesis and retention until deletion for batch (25 of 30). Dated retirements under Microsoft's lifecycle policy (20). Regions chosen per resource and a public sub-processor list (20). MAI-Voice previews run under the Azure preview supplemental terms (updated June 2026). Product terms, the privacy statement and the sub-processor list per the 1 October check, not re-read on 5 October.", "b": "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." }, "scores": { "a": 86, "b": 65 } }, { "by": 19, "category": "ergonomics", "leads": "azure-text-to-speech", "name": "Agent ergonomics", "reasons": { "a": "API reading of the checklist. More than 40 output formats chosen by header, from 8 kHz telephony to 48 kHz, and synthesis events in the SDK (23 of 25). The voice list returns the region's voices in one response with no paging documented, while batch jobs list with paging, and per-request limits are published (10 minutes of audio, 50 voice or audio tags, 64 KB per WebSocket turn) (15 of 20). The REST page lists 400, 401, 415, 429, 502 and 503 with likely causes, and the SDK returns cancellation details with error codes (15 of 20). Retry guidance for 429, no idempotency key on batch jobs (10 of 20). Every REST request needs an SSML body and four headers, including the output format and a `User-Agent`. Speech SDKs in eight languages (12 of 15).", "b": "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." }, "scores": { "a": 75, "b": 56 } }, { "by": 16, "category": "schema", "leads": "minimax-speech", "name": "Schema \u0026 documentation", "reasons": { "a": "Real-time synthesis takes SSML, a W3C format with documented Azure extensions, and we didn't confirm a public OpenAPI file for text-to-speech (10 of 25). No llms.txt found (0). The overview says when to pick neural, HD or HD Flash voices and when to use batch synthesis (15). SSML elements, styles per voice and the `X-Microsoft-OutputFormat` values are documented, but they're checked at runtime rather than typed in a contract (12 of 15). The REST page lists seven status codes with likely causes, and examples cover REST and the SDKs (13 of 15). Dated release notes and `api-version` values on batch synthesis (15). The new MAI voices page gives SSML, REST, Python, C#, JavaScript and Java examples for both models. llms.txt per the 1 October check, not re-read on 5 October.", "b": "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." }, "scores": { "a": 65, "b": 81 } }, { "by": 5, "category": "reliability", "leads": "azure-text-to-speech", "name": "Reliability", "reasons": { "a": "Azure status page with post-incident reviews (20). The 23 July 2026 review (ZJV6-SGG) names Azure Speech in Foundry Tools among services hit by connectivity failures for traffic entering or leaving West US from 14:44 to 19:41 UTC, so we count one major outage. The 1 October note missed it. A 29 September 2026 review covers intermittent 5xx errors for Cognitive Services in Sweden Central from 10:03 to 15:58 UTC, counted as minor. Nothing since 1 October names Speech (10). TTS quotas published, 20 transactions a minute on F0 and 30 a second on S0 by default, adjustable to 1,000, plus batch limits (15). The quotas page explains that 429 usually means backend capacity for a voice and region, and asks for retry logic, a gradual ramp and spreading load across regions (15). Covered by Microsoft's online services SLA (10). Neural and HD voices, the surface graded here, are GA. MAI-Voice-2.1, MAI-Voice-2.1-Flash and MAI-Voice-2-Flash are public preview without an SLA, which doesn't change this line (10).", "b": "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." }, "scores": { "a": 80, "b": 75 } } ], "facts": [ { "a": "Model API", "b": "Model API", "name": "Kind" }, { "a": "Microsoft", "b": "MiniMax", "name": "Vendor" }, { "a": "https://eastus.tts.speech.microsoft.com/cognitiveservices", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, websocket", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (samples), SDK under Microsoft's own licence", "b": "none", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-01", "b": "2026-01-23", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "3.5k stars, 476k npm/wk, 1M PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Azure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 5 of 7 scored categories. MiniMax Speech (T2A) leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Azure AI Speech text-to-speech or MiniMax Speech (T2A)?" }, { "answer": "Azure AI Speech text-to-speech takes an API key or an OAuth sign-in. MiniMax Speech (T2A) needs an API key.", "question": "Do Azure AI Speech text-to-speech and MiniMax Speech (T2A) need an API key?" }, { "answer": "Azure AI Speech text-to-speech has a hosted endpoint at https://eastus.tts.speech.microsoft.com/cognitiveservices. No hosted endpoint is listed for MiniMax Speech (T2A).", "question": "Can an agent call Azure AI Speech text-to-speech and MiniMax Speech (T2A) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 75", "Agent ergonomics, 75 against 56", "Security \u0026 auth, 90 against 36", "Maintenance \u0026 community, 80 against 38", "Transparency \u0026 trust, 86 against 65" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "goodFor": "Operators on Azure who need SSML control, many languages and voices, and enterprise access control.", "slug": "azure-text-to-speech", "watchFor": "An Azure subscription needs a card, even for the free F0 tier" }, { "aheadOn": [ "Schema \u0026 documentation, 81 against 65" ], "also": null, "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" } ], "history": { "azure-text-to-speech": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 71.4, "fromGrade": "BB", "to": 71.5, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 71.7, "fromGrade": "BB", "to": 71.4, "toGrade": "BB" }, { "causes": [ "reliability" ], "date": "2026-10-06", "delta": -2, "from": 73.7, "fromGrade": "BB", "to": 71.7, "toGrade": "BB" } ], "minimax-speech": null }, "job": { "capability": "speech.tts", "name": "Text-to-speech" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-polly-vs-azure-text-to-speech.json", "title": "Amazon Polly vs Azure AI Speech text-to-speech", "url": "https://www.anchorterminal.com/compare/amazon-polly-vs-azure-text-to-speech" }, { "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/azure-text-to-speech-vs-cartesia-tts.json", "title": "Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-cartesia-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-deepgram-tts.json", "title": "Azure AI Speech text-to-speech vs Deepgram Text-to-Speech (Aura-2, Flux TTS)", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-deepgram-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-elevenlabs-tts.json", "title": "Azure AI Speech text-to-speech vs ElevenLabs Text to Speech API + MCP", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-elevenlabs-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-fish-audio-tts.json", "title": "Azure AI Speech text-to-speech vs Fish Audio TTS API", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-fish-audio-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.json", "title": "Azure AI Speech text-to-speech vs Google Cloud Text-to-Speech", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-heygen-voice.json", "title": "Azure AI Speech text-to-speech vs HeyGen Voice", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-heygen-voice" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-inworld-tts.json", "title": "Azure AI Speech text-to-speech vs Inworld Realtime TTS-2", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-inworld-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-murf-tts.json", "title": "Azure AI Speech text-to-speech vs Murf TTS API + MCP", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-murf-tts" }, { "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/azure-text-to-speech-vs-resemble-ai-tts.json", "title": "Azure AI Speech text-to-speech vs Resemble AI Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-resemble-ai-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-rime-tts.json", "title": "Azure AI Speech text-to-speech vs Rime TTS API + MCP", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-rime-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-smallest-lightning-tts.json", "title": "Azure AI Speech text-to-speech vs Smallest.ai Lightning TTS", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-smallest-lightning-tts" }, { "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-soniox-tts.json", "title": "Azure AI Speech text-to-speech vs Soniox Text-to-Speech", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-soniox-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/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/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/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/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/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/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/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-playht-tts.json", "title": "MiniMax Speech (T2A) vs PlayHT Text-to-Speech API", "url": "https://www.anchorterminal.com/compare/minimax-speech-vs-playht-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" } ], "panel": null, "scores": [ { "azure-text-to-speech": 80, "by": 5, "edge": "azure-text-to-speech", "key": "reliability", "minimax-speech": 75, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-text-to-speech": 65, "by": 16, "edge": "minimax-speech", "key": "schema", "minimax-speech": 81, "name": "Schema \u0026 documentation", "weight": 13 }, { "azure-text-to-speech": 75, "by": 19, "edge": "azure-text-to-speech", "key": "ergonomics", "minimax-speech": 56, "name": "Agent ergonomics", "weight": 13 }, { "azure-text-to-speech": 90, "by": 54, "edge": "azure-text-to-speech", "key": "security", "minimax-speech": 36, "name": "Security \u0026 auth", "weight": 14 }, { "azure-text-to-speech": 20, "by": 0, "edge": "", "key": "payments", "minimax-speech": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-text-to-speech": 80, "by": 42, "edge": "azure-text-to-speech", "key": "maintenance", "minimax-speech": 38, "name": "Maintenance \u0026 community", "weight": 7 }, { "azure-text-to-speech": 86, "by": 21, "edge": "azure-text-to-speech", "key": "transparency", "minimax-speech": 65, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Azure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 5 of 7 scored categories. MiniMax Speech (T2A) leads on schema \u0026 documentation. Both do text-to-speech.", "tasks": [ { "a": "$0.13 to $0.20", "b": "$0.54 to $0.90", "cheaper": "azure-text-to-speech", "task": "Narrate a 9,000-character script", "what": "about 1,500 words" } ], "tutorials": [], "verdicts": { "azure-text-to-speech": "Real-time synthesis keeps neither the input text nor the output audio. An Azure subscription needs a card, even for the free F0 tier.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech", "json": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.min.md" }, "markdown": "Azure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 5 of 7 scored categories. MiniMax Speech (T2A) leads on schema \u0026 documentation. Both do text-to-speech.\n\n- Azure AI Speech text-to-speech: grade BB, 71.5/100, rank #157 of 1486. Markdown https://www.anchorterminal.com/tools/azure-text-to-speech.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-text-to-speech.json\n- MiniMax Speech (T2A): grade C, 55.1/100, rank #879 of 1486. Markdown https://www.anchorterminal.com/tools/minimax-speech.md · JSON https://www.anchorterminal.com/api/v1/tools/minimax-speech.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### Azure AI Speech text-to-speech (BB)\n\nGood for: Operators on Azure who need SSML control, many languages and voices, and enterprise access control.\n\nAhead on:\n- Reliability, 80 against 75\n- Agent ergonomics, 75 against 56\n- Security \u0026 auth, 90 against 36\n- Maintenance \u0026 community, 80 against 38\n- Transparency \u0026 trust, 86 against 65\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: An Azure subscription needs a card, even for the free F0 tier\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- Schema \u0026 documentation, 81 against 65\n\nWatch for: No free allowance for synthesis and no official SDK\n\n\n## Why the edge\n\n### Security \u0026 auth: Azure AI Speech text-to-speech +54\n\n- Azure AI Speech text-to-speech (90): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access (30). Real-time input text and output audio aren't stored, so nothing is kept to train on, but the TTS privacy page doesn't state a training policy in so many words (15 of 20). Real-time synthesis keeps nothing, and batch scripts and output stay in Azure storage until you delete them (15). Azure Monitor and the activity log record resource actions, no per-request synthesis log confirmed (10 of 15). MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports and public advisories. The microsoft.com security.txt still carries an Expires date of 2026-09-23 on 5 October (20).\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\n### Maintenance \u0026 community: Azure AI Speech text-to-speech +42\n\n- Azure AI Speech text-to-speech (80): Read as a model. MAI-Voice-2.1 and MAI-Voice-2.1-Flash entered public preview on 1 October 2026, and Speech SDK 1.52.0 shipped on npm and PyPI on 28 September 2026 (30). Speech release notes for July, August and September 2026. The TTS release notes don't list MAI-Voice-2.1 yet (10). Retirements follow Microsoft's published lifecycle policy with dated notices. The MAI model has turned over three times since March 2026 (MAI-Voice-1, MAI-Voice-2-Flash, MAI-Voice-2.1), and the MAI page dropped MAI-Voice-2-Flash without a dated notice, though the language list still carries it as preview (10). Public release notes and Microsoft Q\u0026A, SDK issue tracker not checked (10 of 25). Speech SDK current in eight languages (15). The SDK is a closed binary, so we can't see its CI (5 of 10).\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\n### Transparency \u0026 trust: Azure AI Speech text-to-speech +21\n\n- Azure AI Speech text-to-speech (86): Closed service under Microsoft's product terms, with an MIT samples repository (15). The TTS privacy page, the privacy statement and the product terms agree on no storage for real-time synthesis and retention until deletion for batch (25 of 30). Dated retirements under Microsoft's lifecycle policy (20). Regions chosen per resource and a public sub-processor list (20). MAI-Voice previews run under the Azure preview supplemental terms (updated June 2026). Product terms, the privacy statement and the sub-processor list per the 1 October check, not re-read on 5 October.\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\n### Agent ergonomics: Azure AI Speech text-to-speech +19\n\n- Azure AI Speech text-to-speech (75): API reading of the checklist. More than 40 output formats chosen by header, from 8 kHz telephony to 48 kHz, and synthesis events in the SDK (23 of 25). The voice list returns the region's voices in one response with no paging documented, while batch jobs list with paging, and per-request limits are published (10 minutes of audio, 50 voice or audio tags, 64 KB per WebSocket turn) (15 of 20). The REST page lists 400, 401, 415, 429, 502 and 503 with likely causes, and the SDK returns cancellation details with error codes (15 of 20). Retry guidance for 429, no idempotency key on batch jobs (10 of 20). Every REST request needs an SSML body and four headers, including the output format and a `User-Agent`. Speech SDKs in eight languages (12 of 15).\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\n### Schema \u0026 documentation: MiniMax Speech (T2A) +16\n\n- Azure AI Speech text-to-speech (65): Real-time synthesis takes SSML, a W3C format with documented Azure extensions, and we didn't confirm a public OpenAPI file for text-to-speech (10 of 25). No llms.txt found (0). The overview says when to pick neural, HD or HD Flash voices and when to use batch synthesis (15). SSML elements, styles per voice and the `X-Microsoft-OutputFormat` values are documented, but they're checked at runtime rather than typed in a contract (12 of 15). The REST page lists seven status codes with likely causes, and examples cover REST and the SDKs (13 of 15). Dated release notes and `api-version` values on batch synthesis (15). The new MAI voices page gives SSML, REST, Python, C#, JavaScript and Java examples for both models. llms.txt per the 1 October check, not re-read on 5 October.\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\n### Reliability: Azure AI Speech text-to-speech +5\n\n- Azure AI Speech text-to-speech (80): Azure status page with post-incident reviews (20). The 23 July 2026 review (ZJV6-SGG) names Azure Speech in Foundry Tools among services hit by connectivity failures for traffic entering or leaving West US from 14:44 to 19:41 UTC, so we count one major outage. The 1 October note missed it. A 29 September 2026 review covers intermittent 5xx errors for Cognitive Services in Sweden Central from 10:03 to 15:58 UTC, counted as minor. Nothing since 1 October names Speech (10). TTS quotas published, 20 transactions a minute on F0 and 30 a second on S0 by default, adjustable to 1,000, plus batch limits (15). The quotas page explains that 429 usually means backend capacity for a voice and region, and asks for retry logic, a gradual ramp and spreading load across regions (15). Covered by Microsoft's online services SLA (10). Neural and HD voices, the surface graded here, are GA. MAI-Voice-2.1, MAI-Voice-2.1-Flash and MAI-Voice-2-Flash are public preview without an SLA, which doesn't change this line (10).\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\n## Score by category\n\n| Category | Weight | Azure AI Speech text-to-speech | MiniMax Speech (T2A) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 75 | Azure AI Speech text-to-speech +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 65 | 81 | MiniMax Speech (T2A) +16 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 56 | Azure AI Speech text-to-speech +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 90 | 36 | Azure AI Speech text-to-speech +54 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 38 | Azure AI Speech text-to-speech +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 86 | 65 | Azure AI Speech text-to-speech +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **71.5 · BB** | **55.1 · C** | |\n\n## Facts side by side\n\n| Fact | Azure AI Speech text-to-speech | MiniMax Speech (T2A) |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | Microsoft | MiniMax |\n| Hosted endpoint | `https://eastus.tts.speech.microsoft.com/cognitiveservices` | no (local only) |\n| Transports | HTTP | HTTP, websocket |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | MIT (samples), SDK under Microsoft's own licence | none |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-01 | 2026-01-23 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | 2026-09-01 | couldn't be read |\n| Customer content may train models | yes | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 3.5k stars, 476k npm/wk, 1M PyPI/wk | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## What the same task costs\n\n| Task | Azure AI Speech text-to-speech | MiniMax Speech (T2A) |\n| --- | --- | --- |\n| Narrate a 9,000-character script | $0.13 to $0.20 | $0.54 to $0.90 |\n\n## How the scores have moved\n\n### Azure AI Speech text-to-speech\n\n- +0.1 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n- -2.0 on 6 October 2026: reliability\n\n### MiniMax Speech (T2A)\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Azure AI Speech text-to-speech.** Real-time synthesis keeps neither the input text nor the output audio. An Azure subscription needs a card, even for the free F0 tier.\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## Before you call either\n\n### Azure AI Speech text-to-speech\n\n1. Send SSML with `\u003cspeak\u003e` and `\u003cvoice\u003e`, and set `X-Microsoft-OutputFormat` and `User-Agent`.\n2. On 429 retry with backoff, and try the voice's home region or another region rather than asking for more quota.\n3. Keep each real-time request under 10 minutes of audio, or use batch synthesis.\n4. Use Entra ID tokens instead of resource keys where the agent runs inside Azure.\n5. Name a MAI voice with its model suffix, such as `en-US-Harper:MAI-Voice-2.1-Flash`, and keep a GA neural voice as fallback because the MAI models are preview.\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## Questions\n\n### Which is better for AI agents, Azure AI Speech text-to-speech or MiniMax Speech (T2A)?\n\nAzure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against MiniMax Speech (T2A)'s 55.1 (C), and leads in 5 of 7 scored categories. MiniMax Speech (T2A) leads on schema \u0026 documentation.\n\n### Do Azure AI Speech text-to-speech and MiniMax Speech (T2A) need an API key?\n\nAzure AI Speech text-to-speech takes an API key or an OAuth sign-in. MiniMax Speech (T2A) needs an API key.\n\n### Can an agent call Azure AI Speech text-to-speech and MiniMax Speech (T2A) without installing anything?\n\nAzure AI Speech text-to-speech has a hosted endpoint at https://eastus.tts.speech.microsoft.com/cognitiveservices. No hosted endpoint is listed for MiniMax Speech (T2A).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-text-to-speech\", \"b\": \"minimax-speech\"}`. From a terminal: `anchor compare azure-text-to-speech minimax-speech`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-text-to-speech.json and https://www.anchorterminal.com/api/v1/tools/minimax-speech.json\n\n## Other comparisons with Azure AI Speech text-to-speech or MiniMax Speech (T2A)\n\n- [Amazon Polly vs Azure AI Speech text-to-speech](https://www.anchorterminal.com/compare/amazon-polly-vs-azure-text-to-speech.md)\n- [Amazon Polly vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/amazon-polly-vs-minimax-speech.md)\n- [Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-cartesia-tts.md)\n- [Azure AI Speech text-to-speech vs Deepgram Text-to-Speech (Aura-2, Flux TTS)](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-deepgram-tts.md)\n- [Azure AI Speech text-to-speech vs ElevenLabs Text to Speech API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-elevenlabs-tts.md)\n- [Azure AI Speech text-to-speech vs Fish Audio TTS API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-fish-audio-tts.md)\n- [Azure AI Speech text-to-speech vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.md)\n- [Azure AI Speech text-to-speech vs HeyGen Voice](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-heygen-voice.md)\n- [Azure AI Speech text-to-speech vs Inworld Realtime TTS-2](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-inworld-tts.md)\n- [Azure AI Speech text-to-speech vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-murf-tts.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- [Azure AI Speech text-to-speech vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-resemble-ai-tts.md)\n- [Azure AI Speech text-to-speech vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-rime-tts.md)\n- [Azure AI Speech text-to-speech vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-smallest-lightning-tts.md)\n- [Azure AI Speech text-to-speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-soniox-tts.md)\n- [Cartesia Sonic TTS API + MCP vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/cartesia-tts-vs-minimax-speech.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- [ElevenLabs Text to Speech API + MCP vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-minimax-speech.md)\n- [Fish Audio TTS API vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/fish-audio-tts-vs-minimax-speech.md)\n- [Google Cloud Text-to-Speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.md)\n- [HeyGen Voice vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/heygen-voice-vs-minimax-speech.md)\n- [Inworld Realtime TTS-2 vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/inworld-tts-vs-minimax-speech.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 PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/minimax-speech-vs-playht-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", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Azure AI Speech text-to-speech vs MiniMax Speech (T2A)", "url": "" } ], "description": "Azure AI Speech text-to-speech scores 71.5 (BB) to MiniMax Speech's 55.1 (C) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Azure AI Speech text-to-speech BB 71.5", "MiniMax Speech (T2A) C 55.1", "scores" ], "h1": "Azure AI Speech text-to-speech vs MiniMax Speech (T2A)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/azure-text-to-speech-vs-minimax-speech", "published": "2026-10-01", "section": "tools", "title": "Azure AI Speech text-to-speech vs MiniMax Speech for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech" }, "tokens": { "markdown": 5300, "slim": 3080 }, "version": 1 }