Vocal Video developer docs
Everything Vera, Vocal Video's AI assistant, can do — read collector responses, send invitations, edit storyboards, share videos — is available outside the app as a set of tools. There are two ways in, and they reach the same tools with the same permissions.
Connect an AI assistant
Paste one URL into Claude, ChatGPT, or your IDE agent, sign in, and start asking. No code, no keys.
- Connect Claude — three steps, on the web or in Claude Desktop.
- Connect ChatGPT — the same, behind ChatGPT's Developer mode.
- Other MCP clients — Claude Code, Cursor, and anything else that speaks MCP.
- MCP or API key? — if you're not sure which you need.
Build with the API
Every tool is a POST https://vocalvideo.com/api/v2/tools/{name} with a JSON body, authenticated
with a workspace API key.
- API Quickstart — first read and write calls in five minutes.
- Authentication — keys, scopes, errors, and confirmation tokens.
- API Reference — every tool with its input schema and a live request console.
Plans and AI credits
The MCP server is included on Essential plans and up, and the REST API on Pro and up. See pricing.
Most tools don't touch AI credits, and your assistant's own conversation runs
on your assistant, not on your credits. Two things spend them:
assemble_draft with an AI-directed template, and videos with AI effects
(Studio Sound, filler-word removal, silence shortening, background effects),
which spend 10 credits per published minute when they're first published.
get_account_usage returns the balance. Out of credits, templates fall back to
a standard edit and nothing is deleted.
Reference
| API Reference | Browsable REST reference, generated from the tool registry. |
| OpenAPI spec | The same reference as OpenAPI 3.1 JSON, for generators and agents. |
| MCP Reference | Endpoint, protocol versions, toolsets, auth, and the full tool catalog. |