Niches · Voice cloning & custom voices
Clone a staff member's, actor's or friend's voice with their consent on record
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Docs describe a consent or verification step that the speaker completes (a spoken challenge matched to the sample, or a documented manual route), the API returns or stores a consent record tied to the voice, the speaker can complete it without the account holder's login, a failed check returns a reason and says when a retry is allowed, and the region and plan where cloning is allowed are stated.
How agents ask for it: clone our presenter's voice for the product
, make a voice of my friend, she agreed
, use the voice actor's voice in the app
, prove we had consent for this voice
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| ElevenLabs Voice Cloning and Voice Design API A Eleven Labs Inc. | Professional clones need the speaker's own voice verification and can only be of the account holder; another person must create and verify on their own account and share it. Instant clones rest on an attestation, and acc-22 cloned nine people's voices with no consent step mentioned. source |
| Fish Audio Voice Cloning API B Hanabi AI Inc. | On the MCP, create_voice_clone can return verification_required and verify_voice_clone takes a recording of the actual speaker reading a prompt sentence; the REST create endpoint has no consent field. When verification triggers, retry rules and the region policy are not documented. source |
| Speechify API Voice Cloning A Speechify, Inc. | A single-use, short-lived consent challenge phrase is read aloud by the speaker; Speechify transcribes it, matches the speaker to the sample and keeps it as the consent record. Cloning is refused by caller IP with 403 voice_cloning_unavailable_in_region, but the regions are unnamed. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Murf Voice Cloning API C Murf Inc. | Murf's terms bar automated access to murf.ai, so its API docs were not read this run, as in the 5 November check; no first-hand account names Murf. |
Doesn't do this job 10
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Cartesia Voice Cloning API + MCP C Cartesia AI, Inc. | The clone request has no consent, verification or speaker-challenge field; the guide only gives recording advice. source |
| Gradium Voice Cloning and Voice Design B Gradium SAS | The FAQ says explicit consent from the voice owner is required, but the create call has no consent or verification field; nothing is checked or recorded. source |
| Hume Octave Voice Design and Cloning + MCP C Hume AI, Inc. | Hume's docs index now lists only Audio Decisions and Expression Measurement, and the voice overview and changelog redirect there; the TTS and EVI APIs, cloning and design included, are no longer documented after the 13 November 2026 end of access. source |
| Inworld Instant Voice Cloning B Theai, Inc. dba Inworld AI | Only the Portal flow asks the user to confirm rights to the voice; the API request has no consent or verification field. source |
| MiniMax Voice Clone and Voice Design C Nanonoble Pte. Ltd. | The documented gate is account verification (error 2038). text_validation can reject a clip that does not say a given sentence (1043), but no consent record is kept and the speaker completes nothing. source |
| Resemble AI Voice Cloning API D Resemble AI, Inc. | The create-voice reference lists only name, dataset_url, callback_uri and language; no consent or verification step. source |
| Smallest.ai Instant Voice Clone C Smallest, Inc. | The clone request has no consent or verification field. source |
| Soniox Voice Cloning BB Soniox Inc. | No consent capture or speaker verification in the voice-cloning flow. source |
| Ultravox Voice Cloning E Theai, Inc. dba Inworld AI | The create endpoint has no consent or verification field; the docs set no consent step. source |
| VoiceStudio D VoiceStudio maintainers | No consent step; the terms require the owner's consent but the software cannot check it (listing notes), and clone_voice takes any audio. source |
What stops agents finishing
- consent is an attestation checkbox only, so nothing is on record if challenged (ElevenLabs instant, Hume, Ultravox, VoiceStudio)
- spoken challenge expires or is single use and the speaker is not ready (Speechify)
- PVC verification failed with a 24-hour wait before retry (ElevenLabs help centre)
- cloning refused by the caller's IP region (Speechify since 7 October; Gemini per acc-26)
- API terms forbid end-user uploads (Speechify)
Around it
Before: identity-verification.verify-person, e-signatures.send-from-template. After: voice-cloning.clip-to-voice-id, text-to-speech.clone-voice-speak.
Where this comes from
Weight 15 of 100 in Voice cloning & custom voices: 6 of 34 accounts (a Discord bot that asks the friend first, a builder who cloned nine real people's voices, character voices for a CLI, a fintech wanting watermarks against clones of its agent voices, a region refusal, a voice-actor clone for a launch). Weighted up because consent is a buyer check and decides whether a voice is usable later
The same as data: /api/v1/use-cases/voice-cloning.consented-clone-of-another.json, or the MCP tool get_use_case with id voice-cloning.consented-clone-of-another. Other jobs in this category: /api/v1/niches?category=voice-cloning.
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.