Skip to content
All use cases
For developers

Build a voice-cloning product

Give every user their own voice.

Enroll a user's voice once (free), then synthesize with it through Speak - pay only for audio out. Designed (prompt-to-voice) voices are free to create too.

How it works

  1. 1

    Enroll a voice

    Submit a reference clip; enrollment is free and returns a voice_id.

  2. 2

    Synthesize

    Pass the voice_id to /v1/audio/speech and stream the result.

  3. 3

    Scale per-user

    Plan limits cover up to unlimited cloned voices on higher tiers.

What this replaces

Manual coverage gaps

Enroll voices for free and synthesize with them on demand. That means fewer missed calls, fewer handoffs without context, and fewer hours spent catching up after the fact.

Stacked AI bills

Teams often pay separately for transcription, speech, realtime models, telephony, QA, and orchestration. PyAI keeps the core voice workflow on one usage-based stack.

Slow experimentation

Start with a free key, replay real conversations, compare latency and cost, then route production traffic only when the numbers and customer experience hold up.

Common questions

How does PyAI support build a voice-cloning product?

Enroll a user's voice once (free), then synthesize with it through Speak - pay only for audio out. Designed (prompt-to-voice) voices are free to create too.

What does it cost to test this use case?

Speak realtime text-to-speech is billed per minute, with free voice cloning enrollment and prompt-to-voice design. Every account starts with free credit, so teams can test real call flows before committing budget.

How does this reduce wasted AI spend?

PyAI reduces duplicated vendor bills, manual review work, and migration drag by putting transcription, speech, realtime agents, grounding, and call intelligence on one OpenAI-compatible stack.

How do we keep call quality high in production?

Ground the agent in your own content, bind tools for real actions, warm-transfer when needed, and use Trace or Recap when calls require QA, compliance review, summaries, and audit evidence.

Choose how you want to start.

Use an instant sandbox key for the API, or open Agents Beta and build without code. Sandbox usage never bills. Live keys require available credit.

Agents is live in beta. Sandbox keys have daily limits and never touch billing.