API keys
API keys connect the engine plugins and the MCP server to your account. Create them on the Developer page in the studio.
The full key is shown once, when you create it. Keys are stored only as a hash, so a lost key can't be recovered; revoke it and create a new one. Revoking takes effect immediately.
Keep keys out of version control. The engine plugins store them in editor preferences or environment variables, never in project files.
Scopes
Each key has one or more scopes. Give every plugin or agent only what it needs.
| Scope | Allows | Typical use |
|---|---|---|
read | Projects, lines, jobs, takes and voices; downloading audio | Engine plugins that only sync audio |
generate | Spending credits: render, translate, one-off speech, cancel jobs | Rendering from the editor or an agent |
write | Editing projects, characters, scenes, lines, translations and lexicon; selecting takes | Editing the script from the editor or an agent |
A key without generate can never spend credits, which makes it a safe default for agents you're still trying out.
Billing, API key management, support tickets and account deletion work only from a signed-in studio session, never with an API key.
Rate limits
Limits are counted per account, across all of its keys and sessions.
| Action | Limit |
|---|---|
| All requests (default) | 600 per 1 minute |
| Starting a render | 30 per 1 minute |
| One-off speech and dialogue | 40 per 1 minute |
| Machine translation | 10 per 1 minute |
| ZIP export | 6 per 1 minute |
| Voice previews | 60 per 1 minute |