Moving to the current Verbatik
Map older workflows, billing rules, and API requests to the new workspace.
The current app brings chat, media generation, speech, personas, and projects into a shared creative workspace. Older documentation may use different tools and billing terminology.
Product and billing changes
| Older documentation | Current workflow |
|---|---|
| Separate dashboard for every creative tool | Chat modes for Image, Video, and Audio; a dedicated Text to Speech workspace |
| Large character-credit allowances | Model-based credits shared by the workspace |
| Separate API dollar balance | Current REST API uses the workspace credit pool |
| Creator, Essential, and older unlimited plans | Current catalog is Standard and Pro with credit tiers |
| Fixed clone-slot and 60,000-credit rules | Voice creation is charged according to its current quote |
| Standalone avatar, UGC, captions, and Sound Studio guides | Follow the current persona, campaign, speech, and audio workflows |
Existing subscriptions and imported balances can retain historical details. Check Billing rather than applying the new catalog to an old invoice.
API migration
The current base URL is https://app.verbatik.com/api/v1. Create a current workspace key in Settings → Developer. Keys issued there use the vb_live_ format.
| Legacy pattern | Current API |
|---|---|
/tts with voice headers and plain-text body | POST /speech with JSON speaker blocks, or a supported audio /generations request |
/voices for preset voices | GET /voices/catalog |
/my-voices for custom voices | GET /voices and GET /voices/{id} |
/voice-training | POST /voices with kind: "clone" |
| Voice design tool-specific endpoint | POST /voices with kind: "design" |
/music | POST /generations using an audio music model |
| Immediate audio response assumptions | Queue, poll the returned resource ID, and read completed outputs |
Changing the hostname alone does not migrate the request contract. Update the body, scopes, result handling, error handling, and billing assumptions together. Start with API quickstart.
MCP and older integrations
The current app retains optional compatibility routing for older integrations. That does not make their credentials or tool schemas interchangeable with the current REST API. Read MCP compatibility before connecting a client.