Head to head · Voice cloning · October 2026 research run

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

Hume Octave Voice Design and Cloning + MCP scores 56.5 (C) on agent readiness against Ultravox Voice Cloning's 43.4 (E), and leads in 4 of 7 scored categories. Ultravox Voice Cloning leads on security & auth, payments & pricing and transparency & trust. 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

  • Reliability, 58 against 30
  • Schema & documentation, 87 against 68
  • Agent ergonomics, 75 against 35
  • Maintenance & community, 45 against 15

Also in its favour

  • Runs on your own machine

Watch for

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

Ultravox Voice Cloning E

Best for Giving an Ultravox voice agent a custom voice.

Ahead on

  • Security & auth, 35 against 23
  • Payments & pricing, 60 against 45
  • Transparency & trust, 66 against 57

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

No consent or speaker verification in the product

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.

Agent ergonomics Hume Octave Voice Design and Cloning + MCP +40

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.

Ultravox Voice Cloning 35

Creating a voice returns a small voice object (20 of 25). A voices list exists, pagination and an own-voices filter not confirmed (10 of 20). No error codes documented for voices (0 of 20). No idempotency key and no job to poll (0 of 20). Few required fields, but no official REST SDK, only client SDKs for joining calls (5 of 15).

Maintenance & community Hume Octave Voice Design and Cloning + MCP +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.

Ultravox Voice Cloning 15

Read as a model, on the lines the other hosted voice-cloning listings 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. No dated change touching cloning was found. The news page's newest entry is 3 December 2025 (the v0.7 model), and the deprecation guide's newest entry, 3 November 2026, concerns which call fields, voice among them, a call continued with priorCallId inherits until 7 December 2026, a change to call creation rather than to the voices API, and a sibling listing's reading doesn't move this line (0). No cloning release in the 90 days from 12 August (0). The deprecation guide states a minimum 30-day deprecation window with migration guidance and dated entries (10). A public changelog that has gone quiet, and a support address for more clones, with no answering channel confirmed (5 of 15). No issue tracker for the voices API (0). No official REST SDK; the client SDKs join calls and have no cloning methods (0). No package to check (0). 0 + 0 + 10 + 5 + 0 + 0 + 0 = 15.

Reliability Hume Octave Voice Design and Cloning + MCP +28

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.

Ultravox Voice Cloning 30

status.ultravox.ai's robots.txt disallowed every path on 1 October and again on 4 November, so the page was never read and earns nothing (0; was 10, corrected as for other listings on such hosts) and there is no readable incident history (5). The pricing page, re-read on 10 November 2026, caps Pay as You Go at 5 concurrent calls with no hard cap on Pro (15). No 429, Retry-After or backoff guidance found for creating voices (0). The pricing table lists a response SLA for Enterprise only, with no terms published (0). Cloning has been live since September 2024 and carries no beta label (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.

Schema & documentation Hume Octave Voice Design and Cloning + MCP +19

Hume Octave Voice Design and Cloning + MCP 87

OpenAPI and AsyncAPI files at dev.hume.ai/openapi.json and asyncapi.json, listed in llms.txt (25). llms.txt and Markdown pages (10). The voice guides explain designing from a description and saving a generation, with less on when not to use it (12 of 20). Inputs typed, utterances take a description and text, saving takes a generation ID and a name (12 of 15). Examples throughout and a page of named error codes with fixes (13 of 15). Versioned /v0 paths and a public changelog (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.

Ultravox Voice Cloning 68

The create-voice reference serves its OpenAPI 3.0.3 definition in Markdown on the docs site, and the full schema is published at api.ultravox.ai/api/schema/ (25). llms.txt and Markdown copies of each page (10). The cloning page gives sample rules (30 to 60 seconds, one speaker, MP3 or WAV, 10 MB) but little on when not to use it (10 of 20). Multipart fields typed in the schema, file and name required, language a free BCP47 string with default en (10 of 15). An example request, and only a 201 response documented for the voices endpoint (5 of 15). Unversioned /api paths and a news page whose newest entry is 2025-12-03 (8 of 15). 25 + 10 + 10 + 10 + 5 + 8 = 68.

Payments & pricing Ultravox Voice Cloning +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.

Ultravox Voice Cloning 60

No x402, MPP or L402 (0). Per-minute price public, $0.05 a call minute with the first 30 minutes free and no cloning surcharge, re-read on 10 November 2026 (20). Pay as You Go costs $0 a month and includes one custom voice clone, and the 1 October check found no card needed (20). Signup is a human browser flow (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth Ultravox Voice Cloning +12

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.

Ultravox Voice Cloning 35

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. X-API-Key keys created in the console, no scopes found (20 of 30). No consent step in the product. The terms at ultravox.ai are now Inworld AI's (effective 1 October 2026) and say nothing about cloning others' voices; they incorporate Inworld's Acceptable Use Policy on inworld.ai, which this run can't read (0 of 20). The Inworld terms say generally available models aren't trained on non-public Materials, while the privacy notice lists training its AI models among the uses of collected content, voice recordings included, and keeps voice-derived biometric data until its purpose is met or up to three years (0 of 15). Call History in the dashboard records each call that uses the voice (15). No security.txt (404 on 4 November); the trust centre link answered a bot check, so it is unread (0 of 20). 20 + 0 + 0 + 15 + 0 = 35.

Score by category

CategoryWeightHume Octave Voice Design and Cloning + MCPUltravox Voice CloningEdge
Reliability16%5830Hume Octave Voice Design and Cloning + MCP +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8768Hume Octave Voice Design and Cloning + MCP +19
Agent ergonomics13%7535Hume Octave Voice Design and Cloning + MCP +40
Security & auth14%2335Ultravox Voice Cloning +12
Payments & pricing10%4560Ultravox Voice Cloning +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4515Hume Octave Voice Design and Cloning + MCP +30
Transparency & trust7%5766Ultravox Voice Cloning +9
Negative events≤1500
TotalC 56.5/100E 43.4/100

Facts side by side

FactHume Octave Voice Design and Cloning + MCPUltravox Voice Cloning
KindModel APIModel API
VendorHume AIUltravox (Fixie.ai)
Hosted endpointhttps://api.hume.ai/v0/ttshttps://api.ultravox.ai/api
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
Price for voice cloningnot published$0.05 per minute of call
x402nono
LicenceMIT (SDKs)none
Tools exposed5none
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-182025-12-03
Terms last updated2026-10-052026-10-01
Privacy policy last updated2025-02-252026-10-01
Customer content may train modelsyesyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity180 stars, 79k npm/wk, 24k PyPI/wknone
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Ultravox Voice Cloning higher, the other way from the total score.

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.

Ultravox Voice Cloning

One multipart request with a 30 to 60 second sample creates a private voice for Ultravox calls, with no fee beyond $0.05 a call minute. There is no consent or speaker check, and Inworld's privacy notice allows training on voice recordings and keeps voice-derived data for up to three years.

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

Ultravox Voice Cloning

  1. Send a single clean, single-speaker MP3 or WAV of 30 to 60 seconds, 10 MB at most, with a unique name
  2. Expect one clone per account unless support raises it, whatever the plan page says
  3. Test the voice in the Playground before putting it on a live agent
  4. Get the speaker's written consent first, since Ultravox doesn't check

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 Ultravox Voice Cloning?

Hume Octave Voice Design and Cloning + MCP scores 56.5 (C) on agent readiness against Ultravox Voice Cloning's 43.4 (E), and leads in 4 of 7 scored categories. Ultravox Voice Cloning leads on security & auth, payments & pricing and transparency & trust.

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

Both need an API key.

Can an agent call Hume Octave Voice Design and Cloning + MCP and Ultravox 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 Ultravox Voice Cloning at https://api.ultravox.ai/api.

Other comparisons with Hume Octave Voice Design and Cloning + MCP or Ultravox 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.