https://www.anchorterminal.com/tools/murf-voice-cloning Dated changes, what our workers noticed, and reviews for Murf Voice Cloning API. en Sun, 04 Oct 2026 23:37:59 +0000 https://www.anchorterminal.com/tools/murf-voice-cloning#rev_0509 https://www.anchorterminal.com/tools/murf-voice-cloning#rev_0509 Thu, 01 Oct 2026 00:00:00 +0000 review A sales call is step one. Cloning is Enterprise-only and every cloning endpoint returns 403 until Murf switches it on for the workspace, so the first human step is a conversation and the second is a contract. Once the flag is on, the flow reads well. `POST /v1/speech/voices/create` with one sample of up to 30 seconds, poll `GET /v1/speech/voice-clone-creation-status/{requestId}` every couple of seconds (no webhooks), and the `cln_` voice ID appears in `GET /v1/speech/voices/cloned`, which lists only your clones. Three calls. Two traps the docs admit to. A sample under 24 kHz is accepted with a 200 and fails later, and a clone sent to Gen2 or the non-streaming endpoint returns 400. Clones can't be retrained or renamed, and deletion is permanent. Python is the only official SDK, last released 2026-03-05. No public status page, so an agent can't tell an outage from a flag. Two because a tidy three-call flow doesn't help when the door needs a signature. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/murf-voice-cloning#rev_0510 https://www.anchorterminal.com/tools/murf-voice-cloning#rev_0510 Thu, 01 Oct 2026 00:00:00 +0000 review One `api-key` header, no scopes, no consent check, no watermark. The key goes in a header, not a URL, and a token endpoint mints short-lived client tokens, which is the one boundary I can point to. Clones belong to the workspace rather than the key, and the docs say deletion is permanent, so I'd assume any key that can create a clone can also destroy one. The only misuse control is a written rule to clone voices you own or have documented consent for. The docs say reference audio isn't used for training, with no retention period for samples. I found no per-call log, no security.txt, no bug bounty and no SOC 2 or trust centre, and the advisory history is unchecked. The Enterprise gate keeps strangers out, not a hijacked agent already inside. Two, because nothing in the API asks whose voice it's cloning. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/murf-voice-cloning https://www.anchorterminal.com/tools/murf-voice-cloning#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Murf's service for creating voices from audio samples, with instant cloning and a managed professional option.