No public engine choices to manage
Your app sends the outcome it needs. Routing stays server-side so customer-facing screens stay simple.
Built for shipping teams
TextToSpeechSkills focuses on the parts developers repeatedly ask for after the demo works: clean API calls, predictable jobs, scoped keys, workspace billing, reusable templates, and an agent integration prepared for npm release.
TextToSpeechSkills is a developer-first text-to-speech platform for teams that want clean API access, expression markup, reusable voice templates, async jobs, workspace billing, visible credit usage, and an MCP and skills package prepared for release. A team can create speech in the UI or call the API from a product today, then connect an LLM app through MCP after npm publication.
Easy LLM setup
Non-technical users can start in the browser studio with a saved voice template. The guide will add the copyable MCP command after npm publication.
Read setup guideYour app sends the outcome it needs. Routing stays server-side so customer-facing screens stay simple.
Credits, optional packs, and workspace billing make speech generation easier to forecast as usage grows.
Human builders use the studio or API today; LLM agents will share the same validated workflow after npm publication.
Comparison pages
These pages focus on buyers who already know a voice studio or model vendor, then need to understand the MCP, skills, templates, and LLM workflow difference.
Builders comparing developer-first text-to-speech platforms usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are no public engine choices to manage, billing that matches usage, api, mcp, and skills together. Those are the moments where voice becomes part of real work instead of a one-off export.
Start with readable text, add natural-language expression directions when tone matters, choose an approved voice template, and create a speech job through the UI or API. After npm publication, MCP will use the same pattern for text-to-speech alternative, developer TTS, voice API alternative, helping humans and LLM apps share one process without exposing internal routing or credentials.
Decide which templates are approved, how natural expression markup should be reviewed, who can create workspace keys, and which usage limits are acceptable. Those choices keep automated voice generation useful without letting it sprawl from the first paid Test plan through Pro, Scale, and Business usage.
Common questions
These are the practical details that matter before a team adds speech generation to a real workflow.
Builders comparing developer-first text-to-speech platforms should use this page when they want generated speech that is easy to review, consistent across prompts, and simple to connect to LLM tools. The core workflow combines natural expression markup, voice templates, credit previews, and job-based generation.
Non-technical users can start in the browser studio with a saved voice template. The guide will add the copyable MCP command after npm publication. The setup guide keeps the first path short while still giving developers a clean API when the workflow moves into a product backend.
Every paid plan uses credits. Teams can add credit packs when needed, and workspaces on Pro and higher add central billing for $2 per user per month.
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 docs