Credits & limits

What each call costs, and the limits every plan has.

The API spends the founder's credits, at the app's prices, through the same database checks. Nothing is cheaper or skips a limit because it came through the API.

Prices

WhatCredits
A video (POST /videos)25 each
A slideshow (POST /slideshows, /slideshows/batch)25 each
A retry of a failed video (POST /videos/{id}/retry)25, held again
New lines (POST /ai/lines)adaptive, usually 4–5
A caption (POST /ai/captions)adaptive, a few
Everything else: reads, POST /videos/plan, uploads, cancel, plan itemsfree

AI writes are priced from what the model really used: a hold for the most it can cost first, the real cost after. Every AI response includes credits.

Plans

PlanCreditsAbout
Free30 a day, up to 300 a month10 videos a month
Pro2,500 a month60 videos a month
Max12,500 a month300 videos a month

When credits are taken

  1. POST /videos holds 25 per video. The call fails with 402 not_enough_credits if the balance cannot cover all of them; nothing is held then.
  2. A video that becomes ready is charged.
  3. A video that fails or is cancelled gets its credits back.

Other limits

These come from the plan and answer 422 with their code:

  • queue_full: 40 videos waiting at once.
  • storage_full: finished videos fill the plan's storage. The founder deletes old videos in the app; the API cannot delete.
  • uploads_used: uploads a day and a month.
  • ai_hour_used, ai_day_used: AI writes an hour and a day.
  • rerenders_used: re-renders a month.
  • setup_incomplete: videos need the app, 5 demos and the founder's own reaction; slideshows need the app and 5 images (detail.gate says which).

See the pricing page for each plan's numbers, and Rate limits for request limits.

On this page