1. Install and set your key
2. Clone, wait until it’s ready, then speak
A new voice starts asPENDING while it is processed, and text to speech with it fails until its status is COMPLETED. Wait for it before the first speech request:
wait_for_ready / waitForReady raise an error with the reason if cloning fails, and after timeout (300 seconds by default) if it is still processing.
wait_for_ready and waitForReady arrive in the next release of both SDKs (after 2.10.1). On 2.10.1 or earlier, poll the voice status yourself before speaking:GET /api/v1/voice/voices/{id}/status until status is COMPLETED.Tips
- Record in a quiet room with the microphone at a steady distance. Run a noisy sample through noise reduction first.
- Custom voices count against your plan’s voice slots. See pricing.
- Remove a voice with
client.voice.delete_voice(id)(Python) orclient.voice.delete(id)(Node). - Change who is speaking in an existing recording with the voice changer, using the same voice id.
From an AI agent
On the full MCP endpoint (https://mcp.audiopod.ai, see AudioPod for AI agents) ask: “Clone my voice from https://example.com/my-voice.wav and name it ‘Me’. It’s my own voice.” The clone_voice tool requires the agent to confirm consent (consent_confirmed: true) before anything is created, so expect it to ask you first.
Full endpoint reference: Voice Management.