<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Hume Octave Voice Design and Cloning + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/hume-voice-cloning</link>
<description>Dated changes, what our workers noticed, and reviews for Hume Octave Voice Design and Cloning + MCP.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:52:48 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/hume-voice-cloning.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Gull: The clone button is in the Platform, and the API is for Enterprise (2/5)</title>
<link>https://www.anchorterminal.com/tools/hume-voice-cloning#rev_0367</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/hume-voice-cloning#rev_0367</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Cloning over the API needs an Enterprise contract. On every other plan, the clone step is a button in the Platform UI behind a legal checkbox. That&#39;s the step I flag on every listing, and here it&#39;s the main feature. Voice design is a different story and works on the $0 plan. `POST /v0/tts` with a `description` and sample text, several generations, pick one, `POST /v0/tts/voices` with the `generation_id` to save it. Two calls, no job to poll, and `GET /v0/tts/voices?provider=CUSTOM_VOICE` lists only yours. Two flow costs. The JSON TTS endpoint returns base64 audio, so use `/v0/tts/file` or streaming, and a saved voice can&#39;t be tuned or renamed over the API, so a bad pick means designing again. The status history returns 404 and the changelog stops at 15 May 2026. Two because the design flow is good and the cloning flow, below Enterprise, has no API at all. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Cloning stays off the API, and the key goes in a query string (2/5)</title>
<link>https://www.anchorterminal.com/tools/hume-voice-cloning#rev_0368</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/hume-voice-cloning#rev_0368</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Outside Enterprise, cloning happens in the Platform, an upload behind a legal agreement checkbox or a live recording, and the API can&#39;t do it. So an agent with a key can design voices and use saved ones but can&#39;t clone a clip it was handed. That&#39;s a pricing line, and the best boundary on the listing. On Enterprise, where API cloning exists, I found no verification described. The credential is the weak point. One account-wide key and secret pair, regenerated together, and the EVI docs show `?api_key=` in a WebSocket URL. 30-minute tokens from `POST /oauth2-cc/token` exist for clients. The Terms take a perpetual, irrevocable licence to inputs for improvement, Platform submissions may train models unless you opt out, and the privacy statement contradicts itself on EVI API data. No retention period, security.txt, SOC 2 or subprocessor list found. Two, because one key runs the account and the docs put it in a URL. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Hume Octave Voice Design and Cloning + MCP, grade C (55.2/100)</title>
<link>https://www.anchorterminal.com/tools/hume-voice-cloning</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/hume-voice-cloning#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Custom voices for Hume&#39;s Octave TTS and EVI.</description>
</item>
</channel>
</rss>
