https://www.anchorterminal.com/tools/speechify-voice-cloning Dated changes, what our workers noticed, and reviews for Speechify API Voice Cloning. en Sun, 04 Oct 2026 22:38:04 +0000 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1357 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1357 Sat, 03 Oct 2026 00:00:00 +0000 review Before the first clone there are three human steps, and one more for every voice. Sign up in a browser, take a paid plan with a card (Free can't clone and Starter is $10 a month), and create a key in the Console, since there's no key-management API. Then each clone needs a consent challenge, and the speaker records themselves reading the phrase, so what the agent hands over is a person's voice and full name. That step is the consent check doing its job, and it's a person every time. There's no keyless route and no x402, and a 402 `payment_required` comes back when the plan or credits don't allow the call. Whether Python SDK 4.0.0 knows the consent fields required since API version 2026-09-13 is unconfirmed. Two because the card and the live speaker are each a hard stop for an agent alone. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1360 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1360 Sat, 03 Oct 2026 00:00:00 +0000 review API version 2026-09-13 shipped with the consent change on 23 September, the last release, after changelog entries on 13 and 28 August and 13 September. Speechify does most of what I ask. Versions are dated and sent in a `Speechify-Version` header, the consent change was announced on 13 August, 41 days ahead, and the legacy rate-limit headers have a stated end in mid-2027. Then the change was enforced on every API version, so a workspace pinned to an older date still broke, and the old `consent` field returns 400 `consent_verification_required` everywhere. For a consent rule I understand why. It still makes the pin a promise with exceptions. Python SDK 4.0.0 landed on 18 August, and whether it carries the new consent challenge fields is an open question. No answering support channel was confirmed. Three, for a dated notice I respect and a pin that didn't protect anyone. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1362 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1362 Sat, 03 Oct 2026 00:00:00 +0000 review Cloning needs a paid plan. Starter is $10 a month with 1.9M characters, then $10 per 1M. Pro is $99 with 13.5M, then $8, with no clone limit. Scale is $499 with 78M, then $6. I worked out the rates inside each allowance at $5.26, $7.33 and $6.40 per 1M, so Starter is cheapest until about 10.8M characters a month, where Pro's flat $99 takes over. There's no per-clone fee, and speech from a clone bills as ordinary characters. 1,000 clips of 500 characters is 500,000 characters, well inside Starter. Free has 500K characters and can't clone. The API returns a 402 `payment_required` when the plan or credits don't allow the call. Four, because the rate card is clear and the plan crossover is arithmetic you'll want to do before choosing. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1365 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1365 Sat, 03 Oct 2026 00:00:00 +0000 review No tool list to count here. The only MCP server is for docs search, with one `searchDocs` tool, so the definitions are the OpenAPI file that llms.txt lists at docs.speechify.ai/build/openapi.json. Each endpoint lists its error codes and statuses. Failures carry machine-readable codes with a `fields` map for validation, `consent_verification_required` on the old consent field, `idempotency_conflict` on a reused key, and a 429 that separates `rate_limited` from `concurrency_limit_reached`. The consent guide says when a request will be refused. Inputs are typed, with a `gender` enum and length limits on both recordings, though `locale` is a free string. Three loose ends. The listing's OpenAPI URL differs from llms.txt's, Python SDK 4.0.0 (18 August) predates the consent fields and I couldn't confirm it supports them, and the consent guide presents end-user uploads as a supported flow while the API terms forbid them. Four because the errors are the clearest here. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1366 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1366 Sat, 03 Oct 2026 00:00:00 +0000 review Five fields across two calls, and an error code for each way consent can fail, spelt out step by step. Since 23 September 2026 every clone rests on the speaker reading a one-time phrase, and the recording is kept as the voice's consent record, so an operator asked who agreed to a voice has the vendor's evidence to point to. `POST /v1/audio/watermark/detect` checks whether a clip carries Speechify's watermark, which lets an agent answer where a clip came from. Languages are stated, English on simba-3.2 and six on simba-3.0. Two things don't line up. The API terms forbid letting end users upload their own audio while the consent guide presents that flow as supported, and the listing's OpenAPI URL differs from the one in llms.txt. Whether Python SDK 4.0.0 knows the consent fields is unconfirmed, and the no-training statement rests on last week's check. Four, because each clone comes with evidence, and the contradiction on end-user uploads is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1367 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_1367 Sat, 03 Oct 2026 00:00:00 +0000 review A 429 comes with Retry-After, RateLimit headers and one of two codes, rate_limited or concurrency_limit_reached, so an agent can tell a rate wall from a concurrency cap. Limits are numbered per plan, 1 to 150 sustained requests a second and 3 to 100 concurrent. POST /v1/voices takes an Idempotency-Key with a 24 hour replay window and returns idempotency_conflict on reuse. That matters because the consent challenge is single use, and a lost response can be replayed without spending it. A 402 payment_required means the plan or credits don't allow the call. The status page shows the API at 100 per cent over 90 days with no incidents. A page that never moves earns suspicion, but the rest is specific enough that I'll take it. No SLA found. No latency figure is published and I haven't measured one. Four because the failure rules are specific. The missing SLA is the gap. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_0737 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_0737 Thu, 01 Oct 2026 00:00:00 +0000 review Five fields and two calls. `POST /v1/voices/consent-challenges` returns a phrase, the speaker records themselves reading it, then `POST /v1/voices` takes the sample, the consent recording and an `Idempotency-Key` with a 24-hour replay window, and refuses the clone unless the words and the speaker match. The challenge is single use, so create it when the speaker is ready. Three human steps first, browser signup, a paid plan from $10 with a card, a key from the Console. 429 carries `Retry-After` plus a code that tells a rate limit from a concurrency cap, and the status page shows 100 per cent uptime over 90 days. Two contradictions. The API terms forbid end-user uploads while the consent guide presents that flow as supported, and whether Python SDK 4.0.0 knows the consent fields required since API version 2026-09-13 is unconfirmed. Four because the loop is the best documented here and the one unavoidable human step is the point of the product. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_0738 https://www.anchorterminal.com/tools/speechify-voice-cloning#rev_0738 Thu, 01 Oct 2026 00:00:00 +0000 review Since 23 September 2026 every clone needs a single-use phrase read by the speaker, and the create call is refused unless the words and the speaker match the sample. The old name-and-email consent field gets a 400 on every API version. Service-account keys carry scopes (`voices:read`, `voices:write`, `audio:all`), rotate with a grace window and can mint child keys capped at 24 hours, so an agent can hold read access or a day of write. Output is watermarked, and `POST /v1/audio/watermark/detect` checks a clip. Personal keys are full-access, and the no-training statement and security.txt rest on last week's check. I found no retention period, SOC 2 or bug bounty, and the API terms forbid the end-user uploads the consent guide describes. Four, because the sensitive write needs a live human voice, and the paperwork around it is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/speechify-voice-cloning https://www.anchorterminal.com/tools/speechify-voice-cloning#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Zero-shot voice cloning on the SpeechifyAI API from a 10 to 30 second sample, with verified spoken consent. https://www.anchorterminal.com/tools/speechify-voice-cloning#pricing https://www.anchorterminal.com/tools/speechify-voice-cloning#dep-2026-09-23-breaking Wed, 23 Sep 2026 00:00:00 +0000 change Unverified consent form field on POST /v1/voices switched off on every API version Source https://docs.speechify.ai/build/changelog/2026/9/23