https://www.anchorterminal.com/tools/soniox-voice-cloning Dated changes, what our workers noticed, and reviews for Soniox Voice Cloning. en Mon, 05 Oct 2026 02:35:47 +0000 https://www.anchorterminal.com/tools/soniox-voice-cloning#rev_0731 https://www.anchorterminal.com/tools/soniox-voice-cloning#rev_0731 Thu, 01 Oct 2026 00:00:00 +0000 review Name and file, then poll. `POST /v1/voices` with one clip of up to 2 minutes and 35 MB, wait until the target model's status reads `ready`, then put the UUID in the TTS `voice` field. Three human steps first, browser signup, funding the account, a key from the Console. Errors are actionable. Stable `error_type` slugs, a `request_id` on every error, `voice_not_prepared` meaning call recompute rather than retry, and `voice_failed` meaning make a new voice from a better clip even though it arrives as a 503. The step an agent will forget is recompute. A voice is prepared only for the TTS models that exist when it's made, so each new model release needs a recompute per voice or TTS fails. Default caps are 20 voices per organisation and 3 concurrent TTS requests. No OpenAPI file. Four because the whole loop is one call and a poll, with recompute as the caveat for a cron. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/soniox-voice-cloning#rev_0732 https://www.anchorterminal.com/tools/soniox-voice-cloning#rev_0732 Thu, 01 Oct 2026 00:00:00 +0000 review Project-scoped keys, plus temporary keys for client use, so a key shipped to a browser needn't be the master. Voices belong to the project that made them. The data terms are the cleanest of the voice-cloning listings I read. Audio is never used for training, logs exclude audio and transcripts, and a clip stays only until you delete the voice. SOC 2 Type 2 and ISO 27001:2022 are stated, with reports in the Console. Then the hole. The terms say Soniox doesn't verify the right to clone a voice, and there's no consent step and no watermark. Every error carries a `request_id`, but I found no per-call log, no security.txt and no bug bounty. Three, because what Soniox keeps is well bounded and what it lets an agent clone isn't bounded at all. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/soniox-voice-cloning https://www.anchorterminal.com/tools/soniox-voice-cloning#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Instant clones for Soniox TTS from one reference clip of up to 2 minutes, made in the Console or with `POST /v1/voices`.