Credits and billing //

What costs credits

A 120 s video dubbed into 3 languages uses 360 credits. Credits are sold at $0.06 each (1,000 credits = $60). The table is also returned in costs by GET /v1/credits.

A plan is required

• Every customer workspace needs an active plan. Without one (none yet, cancelled, expired, or on hold while a payment is retried), nothing paid runs: connecting accounts, publishing or scheduling, dubbing, lip sync, voice previews, restyling subtitles and auto-DMs all answer 402 Choose a plan to start. Credits are added on top of a plan. Reading (posts, accounts, credits, history) keeps working.
• If a plan ends, the credit balance is kept. Connected accounts are paused and their scheduled posts held; everything resumes on its own as soon as a plan is active again.
• Top-ups only add credits on top of an active plan.

One balance

• Your plan's credits and the credits you buy share one balance. Credits never expire: what you don't use rolls over.
• GET /v1/credits (or fiftyeight credits) returns credits_balance, plan_credits_per_month, next_plan_credits_at, costs, auto_topup and budget. dub_seconds_balance is kept as a deprecated alias of credits_balance.
• The balance never goes below zero. When a day of fees for accounts past the plan can't be paid, the most recently connected of those accounts are paused (their scheduled posts held). They resume right away once credits are added by the plan's renewal or a top-up (from $5).

See the cost first

GET /v1/credits/estimate?seconds=45&languages=2&lipsync=true returns dubbing, lipsync, total, your balance and whether it is enough. The console shows the same number on every dub (This dub: 90 credits). Pass duration_seconds when creating a dub so one the balance can't cover is refused up front; the exact cost is taken once the video is measured (rounded up to the second). If a language fails, its credits come back.

When the balance is too low

• With automatic top-up on, your saved card is charged right away (within your monthly budget) and the call answers 402 with Not enough credits: this dub needs 60, you have 12. We're adding 333 credits from your card now; try again in a minute. A dub that is already queued waits for the top-up instead of failing.
• Otherwise, or once the monthly budget is reached, it answers 402 with Not enough credits: this dub needs 60, you have 12. Top up or turn on automatic top-up in Plan & credits.
• Publishing and scheduling never stop.

Buying is done in the dashboard

API keys (REST, CLI and MCP) can use the workspace's credits but never spend money or change billing. Choosing or changing a plan, topping up, automatic top-up, confirming an extra account and invoices are done by a signed-in owner or admin on the dashboard's Plan & credits page. With an API key those calls answer 403 Billing is managed from the dashboard. API keys can only use credits. Reading credits, costs, estimates, history and plans stays available to API keys.

Top up

• On Plan & credits, add a preset (500, 1,000, 2,500 or 5,000 credits) or a custom amount from $5 (83 credits, rounded down). Owners and admins only, with an active plan.
• The first top-up opens a checkout that also saves your card. Later top-ups charge the saved card: the credits arrive a minute or two later, once the payment is confirmed.

Automatic top-up and monthly budget

Also on Plan & credits: when the balance falls below the threshold you choose, the saved card is charged the amount you choose (from $5), never more than your monthly budget in a calendar month (UTC). Only one charge runs at a time, and automatic top-up turns off after 3 failed payments. auto_topup and budget in GET /v1/credits show the settings and what was charged this month.

Credit history

GET /v1/credits/history?limit=25&offset=0 lists every movement, newest first: reason (for example subscription, topup, dub_reserve, dub_refund, lipsync, autodm, accounts), a readable label, credits (+/-), balance_after, and ref, the linked object (dub id, payment, auto-DM event, day of account fees).

Monthly plans

• Each plan includes connected accounts, auto-DMs and credits added each paid month (Solo 30, Starter 360, Creator 970, Pro 2,440, Agency 8,150). GET /v1/billing/plans lists them with prices and the current plan.
• Plans are chosen, changed and cancelled on Plan & credits. The plan starts, and its credits are added, once the payment succeeds; each renewal adds the next month's credits.

Accounts past the plan

• Connecting more accounts than the plan includes is never blocked for good: the connect call answers 402, then an owner or admin confirms one more account on Plan & credits. It uses 100 credits a month, taken daily, and the balance must cover a week of every account past the plan.
• Disconnect it and it stops costing anything.
• accounts_past_plan in GET /v1/credits counts the accounts that cost credits.

Turning dubbing off

A workspace can be set to publish and schedule only: PATCH /v1/workspace with {"dubbing_enabled": false} (owners and admins). POST /v1/localizations then answers 409 and the console hides dubbing. Credits still pay for accounts past the plan and auto-DMs past the quota.