Head to head · Voice cloning · October 2026 research run

Hume Octave Voice Design and Cloning + MCP vs Soniox Voice Cloning

Soniox Voice Cloning scores 70 (BB) on agent readiness against Hume Octave Voice Design and Cloning + MCP's 56.5 (C), and leads in 5 of 7 scored categories. Hume Octave Voice Design and Cloning + MCP leads on payments & pricing. Both do voice cloning.

Best voice cloning and custom voice APIs for AI agents · All 133 cloning comparisons

Which one, for what

Hume Octave Voice Design and Cloning + MCP C

Best for Designing a voice from a description, and for teams already on EVI.

Ahead on

  • Payments & pricing, 45 against 30

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Soniox Voice Cloning loses 3 points for them

Watch for

Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date

Soniox Voice Cloning BB

Best for A quick clone that has to speak many languages, from a vendor with clean data terms.

Ahead on

  • Reliability, 87 against 58
  • Agent ergonomics, 82 against 75
  • Security & auth, 67 against 23
  • Maintenance & community, 75 against 45
  • Transparency & trust, 71 against 57

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 2.0 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 +44

Hume Octave Voice Design and Cloning + MCP 23

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. One account-wide API key and secret pair, regenerated together (10), and 30 minute OAuth client-credential tokens for clients (5), less 10 because the docs show the API key in a WebSocket query string, ?api_key= (net 5 of 30). Cloning outside Enterprise happens in the Platform behind a legal agreement checkbox, with no verification (5 of 20). API data isn't used for training, but cloning outside Enterprise is a Platform submission, which may be used unless you opt out in settings, and no retention period is published (5 of 15). Usage is tracked in the portal, no per-call log found for TTS (8 of 15). No security.txt, bug bounty, SOC 2 or trust centre found, HIPAA compliance and a DPA on request are claimed (0 of 20). Per the 1 October check, not re-read on 4 November, because Hume's terms of 5 October 2026 (clause 9.4) bar robots and other automated tools from its websites, so every hume.ai host, status.hume.ai included, is paused.

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.

Maintenance & community Soniox Voice Cloning +30

Hume Octave Voice Design and Cloning + MCP 45

Read as a closing service, since TTS and EVI API access ends on 13 November 2026, with recency from the last change to the listed product's code, and the umbrella rule for the hume SDKs. The last release touching TTS code is Python SDK 0.14.1 (17 August 2026, on PyPI per the 1 October check), built from the Fern regeneration dd9d2c4 of the same day, which sets the version to 0.14.1 and changes the TTS validation error types. It is reached only from a Fern generation tag, not from main or a version tag. 79 days, so 20 of 30, as on 1 October. From 6 August there are only 0.14.1 and the 2 October shutdown notice. TypeScript 0.16.1 (18 August) removed the uuid dependency with no TTS code and isn't counted. That is two dated entries, short of three (0). @humeai/mcp-server's newest tag is 0.3.0 on 8 January 2026. A public changelog, gone quiet, and no answering support channel confirmed (5 of 15). Official Python and TypeScript SDKs (15). TypeScript SDK released within 90 days, Python 3.9 to 3.15 (5 of 10). 20 + 0 + 5 + 15 + 5 = 45.

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.

Reliability Soniox Voice Cloning +29

Hume Octave Voice Design and Cloning + MCP 58

Status page at status.hume.ai (incident.io) with a Text-to-speech API component (20). We couldn't read an incident history on 1 October, the history page returned 404 (5). The sibling EVI listing read the history feed on 1 and 2 October, which holds one TTS incident of about 7 minutes on 19 September; 3 October to 4 November is unread, and a partly unread window keeps its recorded award, so 5 holds. Requests per minute are published by plan on the pricing page, 15 on Free and Starter up to 225 on Business (15). Rate limiting returns error E0811 with 'try again later', and the official SDKs retry with exponential backoff (8, an in-between value kept and flagged). No idempotency or safe-retry guidance for saving a voice (0). No SLA published (0). Voice design over the TTS API is generally available until API access ends on 13 November 2026 (10). 20 + 5 + 15 + 8 + 0 + 0 + 10 = 58. Per the 1 October check, not re-read on 4 November, because Hume's terms of 5 October 2026 (clause 9.4) bar robots and other automated tools from its websites, so every hume.ai host, status.hume.ai included, is paused.

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.

Payments & pricing Hume Octave Voice Design and Cloning + MCP +15

Hume Octave Voice Design and Cloning + MCP 45

No x402, MPP or L402 (0). Per-unit overage prices are public, $0.15 per 1,000 characters on Creator down to $0.05 on Business (20). A $0 Free plan includes voice design over the API, but cloning over the API is Enterprise-only and the card requirement isn't stated (10 of 20). Signup is a human browser flow (0). Per the 1 October check, not re-read on 4 November, because Hume's terms of 5 October 2026 (clause 9.4) bar robots and other automated tools from its websites, so every hume.ai host, status.hume.ai included, is paused. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Transparency & trust Soniox Voice Cloning +14

Hume Octave Voice Design and Cloning + MCP 57

Closed service with clear terms, SDKs under MIT (15 of 30). The privacy statement says API data isn't used for training and also that anonymised EVI API data is used by default, a DPA is on request only, and no retention period or subprocessor list is published (10 of 30). Dated deprecations in the changelog, EVI 1 and 2 retired on 30 August 2025 after six weeks' notice (15 of 20). No subprocessor list or data locations found (0 of 20). Per the 1 October check, not re-read on 4 November, because Hume's terms of 5 October 2026 (clause 9.4) bar robots and other automated tools from its websites, so every hume.ai host, status.hume.ai included, is paused.

Soniox Voice Cloning 71

Closed service with clear terms, SDKs open source (15 of 30). Terms and privacy updated 2026-06-29 agree that samples aren't used for training and stay until deleted, with Async data auto-deleted after 30 days, but we found no public DPA or subprocessor list (20 of 30). Deprecation guidance and model aliases on the models page (15 of 20). Data residency documented, with regions in the US, Europe, Japan and India, no subprocessor list found (10 of 20). Per the 1 October check for the terms and privacy policy, not re-read on 4 November; the security page still says audio is never used to improve models and Async data is deleted after 30 days. 15 + 20 + 15 + 10 = 60.

Agent ergonomics Soniox Voice Cloning +7

Hume Octave Voice Design and Cloning + MCP 75

The official MCP server has 5 tools, but the JSON TTS endpoint returns base64 audio inside the response, which is heavy in a context window (20 of 25). The voice list paginates and filters by provider, so CUSTOM_VOICE returns only your voices (20). Named error codes (E0601, E0811 and others) say whether to retry (20). No idempotency key and no job to poll, a design call simply runs again (0 of 20). Few required fields, official Python and TypeScript SDKs (15). Per the 1 October check, not re-read on 4 November, because Hume's terms of 5 October 2026 (clause 9.4) bar robots and other automated tools from its websites, so every hume.ai host, status.hume.ai included, is paused.

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.

Score by category

CategoryWeightHume Octave Voice Design and Cloning + MCPSoniox Voice CloningEdge
Reliability16%5887Soniox Voice Cloning +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8786Hume Octave Voice Design and Cloning + MCP +1
Agent ergonomics13%7582Soniox Voice Cloning +7
Security & auth14%2367Soniox Voice Cloning +44
Payments & pricing10%4530Hume Octave Voice Design and Cloning + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4575Soniox Voice Cloning +30
Transparency & trust7%5771Soniox Voice Cloning +14
Negative events≤150-3
TotalC 56.5/100BB 70/100

Facts side by side

FactHume Octave Voice Design and Cloning + MCPSoniox Voice Cloning
KindModel APIModel API
VendorHume AISoniox
Hosted endpointhttps://api.hume.ai/v0/ttshttps://api.soniox.com/v1
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
Price for voice cloningnot published$0.0117 per minute of audio
x402nono
LicenceMIT (SDKs)Apache-2.0 (Python SDK)
Tools exposed5none
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-182026-11-03
Terms last updated2026-10-052026-06-29
Privacy policy last updated2025-02-252026-06-29
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity180 stars, 79k npm/wk, 24k PyPI/wk12 stars, 22k npm/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Soniox Voice Cloning higher.

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

Hume Octave Voice Design and Cloning + MCP

Voice design from a natural-language description, saved with one call. Cloning over the API is Enterprise-only. Hume ends API access on 13 November 2026.

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

Hume Octave Voice Design and Cloning + MCP

  1. Design with POST /v0/tts using an utterance description plus sample text, then save a generation_id with POST /v0/tts/voices
  2. Request several generations and pick one. A saved voice can't be tuned afterwards
  3. List your own voices with GET /v0/tts/voices?provider=CUSTOM_VOICE
  4. Use /v0/tts/file or streaming rather than the JSON endpoint to keep base64 audio out of context
  5. On E0811 back off and retry, the request was rate limited

Soniox Voice Cloning

  1. Poll the voice until the target model's status is ready before using it in TTS
  2. On voice_not_prepared call recompute, don't retry the TTS request
  3. Don't retry voice_failed even though it's a 503. Create a new voice from a better clip
  4. Use a key from the project that owns the voice, voices are per project
  5. Keep the clip under 2 minutes and 35 MB, longer fails with voice_audio_too_long
  6. 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.

Questions

Which is better for AI agents, Hume Octave Voice Design and Cloning + MCP or Soniox Voice Cloning?

Soniox Voice Cloning scores 70 (BB) on agent readiness against Hume Octave Voice Design and Cloning + MCP's 56.5 (C), and leads in 5 of 7 scored categories. Hume Octave Voice Design and Cloning + MCP leads on payments & pricing.

Do Hume Octave Voice Design and Cloning + MCP and Soniox Voice Cloning need an API key?

Both need an API key.

Can an agent call Hume Octave Voice Design and Cloning + MCP and Soniox Voice Cloning without installing anything?

Yes. Hume Octave Voice Design and Cloning + MCP has a hosted endpoint at https://api.hume.ai/v0/tts and Soniox Voice Cloning at https://api.soniox.com/v1.

Other comparisons with Hume Octave Voice Design and Cloning + MCP or Soniox Voice Cloning

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.