Voice Cloning And Voice Library

Operator uploads a sample clip to create a cloned voice and expects an instantly usable, high-fidelity voice id from a 2-second noisy phone snippet.

Create the voice via the documented voice-creation request with an adequate, clean sample (per documented clip duration/quality guidance [REQUIRES-VERIFICATION on exact minimums]); persist the returned voice id with its provenance. Validate input audio quality before submission rather than expectin…

After cloning, the agent re-uploads the source clip on every /tts call instead of referencing the persisted voice id.

Reference the persisted voice id in subsequent /tts requests. Do not re-upload or re-clone per call — that wastes quota and may produce subtly different voices. Keep a stable id→voice mapping in the operator's store.

A product flow lets end users clone 'any voice' from an uploaded clip with no attestation that they have rights to that voice.

Gate voice creation on a recorded consent/authorization attestation that the uploader controls or is licensed for the voice, stored with the voice id and timestamp for audit. Refuse to create cloned voices from clips lacking a consent record — this is core to Cartesia's voice-clone consent posture.