Documentation

Build with voice in a predictable way.

Use these guides to move from first generation to production integration with authentication, API usage, SSML, and security practices.

DOC INDEX

Getting started

Authentication

TTS

SSML

START

AUTH

GENERATE

SHIP

Documentation map

Start with the browser studio, then move to API keys and integration when the workflow needs automation.

Create an account, choose a voice, generate a short sample, and save the result.

User access is handled through Clerk and requests to Laravel flow through the live-auth proxy.

Submit text, select voice/language, and handle long-running generation states.

Upload only consented samples and follow the 25MB frontend/backend limit.

Use supported tags for breaks, emphasis, prosody, and pronunciation control.

Plan for validation errors, timeouts, unavailable voices, and billing limits.

Keep API keys server-side, use HTTPS, avoid storing raw secrets in client code, and log generated content responsibly.

Do I need technical setup to start?

No. You can create audio in Voice Studio from the browser. Developers can use the API when they need automation.

Does CORD.GE support Georgian voices?

Yes. The product is built for Georgian and English workflows, including business narration, support audio, and product voiceovers.

Can I clone any voice?

No. You must have the legal right and explicit permission to upload and clone a voice. Non-consensual cloning and impersonation are prohibited.