Docs
Use the same speech workflow from the browser UI, your product backend, or an LLM app. Start with scoped keys, natural expression markup like [excited but still professional], reusable voice templates, async speech jobs, and an MCP and skills package prepared for release.
Speech generation should not depend on a browser waiting for one long request. The docs explain how to create jobs, poll for status, receive audio URLs, and keep longer scripts in the background so your product UI stays responsive while the server handles billing, storage, retries, and delivery.
After npm publication, the MCP and skills package will give LLM apps focused tools for validating expression markup, listing approved templates, previewing credit use, creating jobs, and returning audio without broad account access. Use the studio or API today.
Instead of repeating subjective voice instructions in every API call, your app sends text plus a template ID. The docs cover how templates should be named, versioned, approved, and shared across workspaces so narrators, characters, support voices, and course instructors stay recognizable.
API keys, OAuth, payment state, private audio storage, service routing, and usage ledger updates belong on the backend. The public UI only needs scoped actions and safe configuration, which keeps setup easier for users and reduces the chance of accidental secret exposure.
Docs quickstart
await fetch("https://texttospeechskills.com/api/v1/tts/jobs", {
method: "POST",
headers: {
authorization: `Bearer ${process.env.TTS_API_KEY}`,
"content-type": "application/json"
},
body: JSON.stringify({
text: "[quiet] hello. [loud and angry] how are you?",
voice_template: "vt_calm_narrator_v1"
})
});API keys
key_••••••••••••Keys are hashed at rest and never shown again after creation.
API playground
{
"text": "[quiet] hello. [loud and angry] how are you?",
"voice_template": "vt_calm_narrator_v1",
"format": "wav"
}MCP package
npm release status
Install commands are not available yetThe package is prepared for release but is not published. Use the browser studio or API today; MCP commands will appear here after npm publication.
Read API docsSafety
Keys, workspace access, private storage, and background generation are designed so teams can test quickly without opening up risky access.
Create keys for apps, workspaces, and LLM tools without sharing broad account access.
Longer generations run in the background, so users can poll or receive updates when audio is ready.
Generated audio is stored privately and served through controlled URLs.