Head to head · Voice cloning · October 2026 research run
Cartesia Voice Cloning API + MCP vs Soniox Voice Cloning
Soniox Voice Cloning scores 70 (BB) on agent readiness against Cartesia Voice Cloning API + MCP's 58.9 (C), and leads in 5 of 7 scored categories. Cartesia Voice Cloning API + MCP leads on maintenance & community. Both do voice cloning.
Best voice cloning and custom voice APIs for AI agents · All 133 cloning comparisons
Which one, for what
Cartesia Voice Cloning API + MCP C
Best for Teams that want cheap instant clones and fast streaming TTS in the same account, especially voice agents.
Ahead on
- Maintenance & community, 84 against 75
Also in its favour
- Runs on your own machine
Watch for
No consent or speaker verification in the clone API
Best for A quick clone that has to speak many languages, from a vendor with clean data terms.
Ahead on
- Reliability, 87 against 73
- Agent ergonomics, 82 against 65
- Security & auth, 67 against 42
- Payments & pricing, 30 against 15
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
No consent capture or speaker verification, and the terms say so
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Soniox Voice Cloning +25
Cartesia Voice Cloning API + MCP 42
Graded on the model lines with the voice-cloning substitutions this run uses (consent and misuse controls in place of the read-only line, training and retention of voice data in place of the prompt-injection line), on the same evidence and values as cartesia-tts and cartesia-ink-stt where it is shared. Standard and admin API keys are separate types, revocable, and a server can mint short-lived access tokens with TTS, STT and agent grants, but no key or grant is scoped to cloning (26). Browsers pass the access token in the WebSocket query string, which the authentication guide documents ("In browsers, use an access token and query parameters instead"), so the full 10 comes off, as for cartesia-tts and cartesia-ink-stt (16 of 30; was 25). The clone API takes clip, name and language with no consent field or speaker check, the Acceptable Use Policy asks for the speaker's explicit consent, and no watermark or detection tool was found (0 of 20). The Terms (last revised 14 June 2024, re-read 4 November) allow training on inputs unless otherwise agreed, with an opt-out form, zero data retention "is not available for voice cloning, PVC, voice creation", and no retention period for samples is published beyond a post-termination window in the DPA (5 of 15). Usage totals in the dashboard and through an admin-key endpoint, no per-call log found (7 of 15, aligned with cartesia-tts; was 8). security.txt at www.cartesia.ai is valid until 3 October 2027 with a contact and a policy link to the trust centre, and SOC 2 Type II, HIPAA and PCI-DSS are stated. The trust centre is drawn by script and wasn't read, and no bug bounty was found (14 of 20; the 1 October check found no security.txt, 10). 16+0+5+7+14 = 42.
Soniox Voice Cloning 67
Graded for voice cloning, with consent and misuse controls in place of the read-only line and training and retention of voice data in place of the prompt-injection line, since the API returns audio and IDs rather than third-party text. Project API keys carry permissions per resource, with read and write levels for cloned voices, a missing permission returns 403 permission_denied, and temporary keys serve browser clients (30; was 25). The terms say Soniox doesn't verify the right to clone a voice, and there's no consent step or watermark, per the 1 October check, not re-read on 4 November (0 of 20). Audio is never used to improve models, and a voice's clip stays until you delete the voice (15). Per-request usage logs and every error's request_id, as soniox-tts reads them (10 of 15; was 8). SOC 2 Type 2 and ISO/IEC 27001:2022 stated; the Python SDK's SECURITY.md gives a disclosure route by email, GitHub, a maintainer or Discord; soniox.com/.well-known/security.txt answers 404 and no bug bounty was found, as soniox-tts (12 of 20; was 5). 30 + 0 + 15 + 10 + 12 = 67.
Agent ergonomics Soniox Voice Cloning +17
Cartesia Voice Cloning API + MCP 65
Responses are compact voice objects, but we found no filter to list only your own voices, and the MCP server loads 19 tools (20 of 25). Voice lists paginate, with auto-paginating SDK iterators, filters not confirmed (10 of 20). Errors are HTTP statuses mapped to SDK exceptions, without cloning-specific codes (10 of 20). No idempotency key. Pro clone fine-tunes expose a status to poll (10 of 20). Three required fields plus the version header, and official Python and TypeScript SDKs (15).
Soniox Voice Cloning 82
Responses are small voice objects, and the OpenAPI file says the list returns the voices in your project (22 of 25; was 20). The voices list pages with limit (up to 1,000) and a cursor, and a count endpoint returns the total, with no filters on custom voices (15 of 20; was 10). Errors say which to retry and which are terminal, and voice_not_prepared tells you to recompute (20). No idempotency key; voice processing has a per-model status to poll, and a duplicate name is refused (10 of 20). Two required fields and SDKs for Python, Node, the web and React (15). 22 + 15 + 20 + 10 + 15 = 82.
Payments & pricing Soniox Voice Cloning +15
Cartesia Voice Cloning API + MCP 15
No x402, MPP or L402 (0). Plan prices are public and instant cloning is included from Pro at $5 a month, Pro cloning from Startup at $49, but there's no dollar price per unit, only credits (10). The Free plan has no cloning, re-read on 4 November (0). Signup is a human browser flow (0). 0+10+0+0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Soniox Voice Cloning 30
No x402, MPP or L402 (0). Per-unit prices are public, $4 per million input text tokens and $21.50 per million output audio tokens, about $0.70 an hour by Soniox's estimate, with no cloning fee (20). No free tier for new accounts (0). Signup is a human browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Reliability Soniox Voice Cloning +14
Cartesia Voice Cloning API + MCP 73
incident.io status page at status.cartesia.ai with a Voice Cloning component and a dated history (20). feed.rss, read on 4 November, lists these items touching Voice Cloning from 6 August to 4 November 2026. 7 August "Agents Telephony failing in the US" lists every component in the feed, but its incident page names only Voice Agents, as a partial outage. 4 September "Intermittent issues with voice cloning in APAC" (about 21 hours across 3 and 4 September per the 1 October reading), one region. 7 October "Degraded API Performance in US Regions", US only. 23 October "Elevated latency for instant voice cloning", latency. Each is partial and minor under this run's incident rule, and the 1 August API-wide major has left the window. Minor incidents only (20; was 10), as cartesia-tts and cartesia-ink-stt on the same page. Concurrency limits per plan are published, 2 to 15 TTS requests (15). A 429 is documented when the limit is hit, with no Retry-After or backoff guidance in the docs, but the official SDK README says it retries 429 and 5xx twice with exponential backoff, and there is no idempotency key or safe-retry guidance for clone creation (8). No SLA published (0). Instant cloning is generally available (10). 20+20+15+8+0+10 = 73.
Soniox Voice Cloning 87
Instatus page at status.soniox.com with five components in each of the US, Europe, Japan and India groups plus the Console, and a dated notice history (20). In the 90 days from 6 August the page posted three incidents, failed API key creation in the Console for 1 hour 10 minutes on 24 August, failed new EU real-time STT connections for 9 minutes on 25 August and Japan real-time STT overload for 45 minutes on 8 September, and none for October or November. None touches TTS or voices, so the record is clean for this listing, read as soniox-tts (30; was 20). TTS REST limits published, 100 requests a minute and 3 concurrent requests, and 20 voices per organisation (15). A 429 returns limit_exceeded; the OpenAPI file says to retry a 429 after a delay, retry a 408 and retry a 503 with backoff. No Retry-After and no idempotency key on voice creation, though a repeated create with the same name is refused because names are unique per project. Safe-retry guidance without idempotency keys earns 12, as soniox-tts (12; was 8). No SLA found (0). Voice cloning is part of the GA tts-rt-v2 model (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.
Maintenance & community Cartesia Voice Cloning API + MCP +9
Cartesia Voice Cloning API + MCP 84
Read as a model, on the lines cartesia-tts, cartesia-ink-stt and the other hosted speech models use (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10); the 1 October check used the tool lines. cartesia-mcp, whose clone_voice and localize_voice tools call the cloning API, released 0.28.1 on 30 October 2026 after 0.26.1 (8 October), 0.27.0 (20 October), 0.27.1 (23 October) and 0.28.0 (27 October) (30). From 6 August the Python and TypeScript SDKs released 4.0.0, 4.0.1, 4.1.0 and 4.2.0 (14 August to 2 September) and the MCP server more than ten releases (10). Sonic-2, Sonic Turbo and sonic-3-2025-10-27 were sunset after 20 October 2026, announced in the July changelog, and the deprecations page states no minimum notice period (5 of 10). The changelog has Voices entries every month from May to September 2026, dated by month only, and no October entry (11 of 15, as cartesia-tts). The Python SDK repository had 4 open issues on 9 October per the cartesia-ink-stt check, not re-read since GitHub's pages answered 403 (5 of 10). Official cartesia and @cartesia/cartesia-js SDKs at 4.2.0 (2 September 2026), generated for API version 2026-08-14 (15). CI (test.yml), release-please and lock files, with dependency updates merged on 23 October (8 of 10). 30+10+5+11+5+15+8 = 84.
Soniox Voice Cloning 75
Read as a model, on the lines soniox-tts, deepgram-tts and cartesia-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10); the 1 October note used the tool lines. Python SDK soniox 2.11.0 on 3 November 2026 adds voice permissions and voice limits to its types, and the JavaScript tag v2026.11.03 ships @soniox/node 2.5.0 the same day (30; was 20). In the 90 days from 6 August, tts-rt-v2 GA with high-fidelity cloning (11 August), the tts-rt-v1 removal (31 August), Python 2.9.0 (11 August, adds the voices client), 2.10.0 (2 October) and 2.11.0 (3 November), and JavaScript tags v2026.08.11, v2026.10.12 and v2026.11.03 (10). tts-rt-v1 was removed 20 days after its deprecation notice, while the deprecation of api_key in WebSocket config messages carries a 15 January 2027 deadline with a migration guide (5 of 10). The models page and a support channel, untested (5 of 15). SDK issues couldn't be read because GitHub's pages answered 403 (3 of 10). SDKs for Python, Node, the web and React (15). soniox-js runs a CI workflow on every push (lint and tests); the Python SDK has tests and a lock file but no workflow in its clone (7 of 10). 30 + 10 + 5 + 5 + 3 + 15 + 7 = 75.
Score by category
| Category | Weight | Cartesia Voice Cloning API + MCP | Soniox Voice Cloning | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 87 | Soniox Voice Cloning +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 86 | Soniox Voice Cloning +1 |
| Agent ergonomics | 13% | 65 | 82 | Soniox Voice Cloning +17 |
| Security & auth | 14% | 42 | 67 | Soniox Voice Cloning +25 |
| Payments & pricing | 10% | 15 | 30 | Soniox Voice Cloning +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 75 | Cartesia Voice Cloning API + MCP +9 |
| Transparency & trust | 7% | 73 | 71 | Cartesia Voice Cloning API + MCP +2 |
| Negative events | ≤15 | -3 | -3 | |
| Total | C 58.9/100 | BB 70/100 |
Facts side by side
| Fact | Cartesia Voice Cloning API + MCP | Soniox Voice Cloning |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Cartesia | Soniox |
| Hosted endpoint | https://api.cartesia.ai | https://api.soniox.com/v1 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for voice cloning | not published | $0.0117 per minute of audio |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Apache-2.0 (Python SDK) |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-11-03 |
| Terms last updated | 2024-06-14 | 2026-06-29 |
| Privacy policy last updated | 2024-06-14 | 2026-06-29 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 133 stars, 166k npm/wk, 177k PyPI/wk | 12 stars, 22k npm/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Soniox Voice Cloning higher.
| Reviewer | Cartesia Voice Cloning API + MCP | Soniox Voice Cloning |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 One call for an instant clone, four for a Pro one | 4/5 Name, file, poll for ready, done |
| WardenSecurity auditor | 2/5 Ten seconds of audio and no consent field | 3/5 Clean data terms, and nobody checks consent |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Cartesia Voice Cloning API + MCP
Instant clones need 10 seconds of audio and use up to 60 seconds on Sonic 3.6, and the official MCP server exposes cloning with annotated tools. The clone API has no consent or speaker check, the Terms allow training on uploads unless you opt out, and Pro clones began requiring dated model IDs in March 2026 without advance notice.
Soniox Voice Cloning
One API call and a clip of up to 2 minutes, with an OpenAPI file covering create, list, recompute and delete. No consent capture or speaker verification, and the terms say so. A Python SDK minor release removed public interfaces without notice in October 2026.
Before you call either
Cartesia Voice Cloning API + MCP
- Send
Cartesia-Versionon every call. The clone endpoint lists it as a required header - Pass the speaker's recorded
language. A clone is built from one language, add others with the accents API - Keep IVC uploads under 16 MB
- Don't blind-retry
POST /voices/clone. The SDK retries 429 and 5xx twice and there's no idempotency key, so check the voice list first - Call a Pro clone with a model from its
fine_tunes.public_model_id, such assonic-3.6-2026-08-27, not an undated alias
Soniox Voice Cloning
- Poll the voice until the target model's status is
readybefore using it in TTS - On
voice_not_preparedcall recompute, don't retry the TTS request - Don't retry
voice_failedeven though it's a 503. Create a new voice from a better clip - Use a key from the project that owns the voice, voices are per project
- Keep the clip under 2 minutes and 35 MB, longer fails with
voice_audio_too_long - Send the API key with the WebSocket connection, not in the config message, before 15 January 2027
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Create a private voice clone with Cartesia, for Cartesia Voice Cloning API + MCP
- Prepare a project voice for Soniox TTS, for Soniox Voice Cloning
Questions
Which is better for AI agents, Cartesia Voice Cloning API + MCP or Soniox Voice Cloning?
Soniox Voice Cloning scores 70 (BB) on agent readiness against Cartesia Voice Cloning API + MCP's 58.9 (C), and leads in 5 of 7 scored categories. Cartesia Voice Cloning API + MCP leads on maintenance & community.
Do Cartesia Voice Cloning API + MCP and Soniox Voice Cloning need an API key?
Cartesia Voice Cloning API + MCP takes an API key or an OAuth sign-in. Soniox Voice Cloning needs an API key.
Can an agent call Cartesia Voice Cloning API + MCP and Soniox Voice Cloning without installing anything?
Yes. Cartesia Voice Cloning API + MCP has a hosted endpoint at https://api.cartesia.ai and Soniox Voice Cloning at https://api.soniox.com/v1.
Other comparisons with Cartesia Voice Cloning API + MCP or Soniox Voice Cloning
- Cartesia Voice Cloning API + MCP vs ElevenLabs Voice Cloning and Voice Design API
- Cartesia Voice Cloning API + MCP vs Fish Audio Voice Cloning API
- Cartesia Voice Cloning API + MCP vs Gradium Voice Cloning and Voice Design
- Cartesia Voice Cloning API + MCP vs Hume Octave Voice Design and Cloning + MCP
- Cartesia Voice Cloning API + MCP vs Inworld Instant Voice Cloning
- Cartesia Voice Cloning API + MCP vs MiniMax Voice Clone and Voice Design
- Cartesia Voice Cloning API + MCP vs Murf Voice Cloning API
- Cartesia Voice Cloning API + MCP vs PlayHT Voice Cloning API
- Cartesia Voice Cloning API + MCP vs Resemble AI Voice Cloning API
- Cartesia Voice Cloning API + MCP vs Smallest.ai Instant Voice Clone
- Cartesia Voice Cloning API + MCP vs Speechify API Voice Cloning
- Cartesia Voice Cloning API + MCP vs Ultravox Voice Cloning
- Cartesia Voice Cloning API + MCP vs VoiceStudio
- ElevenLabs Voice Cloning and Voice Design API vs Soniox Voice Cloning
- Fish Audio Voice Cloning API vs Soniox Voice Cloning
- Gradium Voice Cloning and Voice Design vs Soniox Voice Cloning
- Hume Octave Voice Design and Cloning + MCP vs Soniox Voice Cloning
- Inworld Instant Voice Cloning vs Soniox Voice Cloning
- MiniMax Voice Clone and Voice Design vs Soniox Voice Cloning
- Murf Voice Cloning API vs Soniox Voice Cloning
- PlayHT Voice Cloning API vs Soniox Voice Cloning
- Resemble AI Voice Cloning API vs Soniox Voice Cloning
- Smallest.ai Instant Voice Clone vs Soniox Voice Cloning
- Soniox Voice Cloning vs Speechify API Voice Cloning
- Soniox Voice Cloning vs Ultravox Voice Cloning
- Soniox Voice Cloning vs VoiceStudio
Machine-readable
- This page as Markdown
/compare/cartesia-voice-cloning-vs-soniox-voice-cloning.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cartesia-voice-cloning.json·/api/v1/tools/soniox-voice-cloning.json - From a terminal
anchor compare cartesia-voice-cloning soniox-voice-cloning(the CLI) - Over MCP
compare_tools {"a": "cartesia-voice-cloning", "b": "soniox-voice-cloning"}at/mcp, no key