Skip to main content
Five API is prepaid. You buy credits in the console and every video task is paid in credits. There is no subscription and no minimum spend.

​
Buy credits

Open Billing in the developer console, pick a credit pack and pay with one of the methods shown there. Credits are added to your balance as soon as the payment is confirmed. Larger packs cost less per credit.

​
What a video costs

The price of a task depends on three things:
  • the model,
  • the resolution,
  • the duration (for video extend, the number of seconds added).
The credit packs and the price of every model, per resolution and duration, are listed in the developer console. The price of a specific request is returned as credits.estimated as soon as the task is created.
Not every model sells every combination of resolution and duration. A combination the model does not offer answers 400 invalid_parameter and costs nothing.

​
How credits move

In v1 the charge of a completed task always equals its estimate.
balance.credits is what you can spend right now. Credits held by queued and processing tasks are not spendable until those tasks finish, so a request can answer 402 insufficient_credits while the console shows a larger total. Wait for in-flight tasks, cancel the ones you no longer need, or top up.

​
Check your balance

When the balance cannot cover a new task, the create call answers 402:

​
Low-balance reminder

On the Billing page you can set a threshold. When your spendable balance falls below it, the account’s owners and admins get an email. You get one email each time the balance falls below the threshold: once the balance is back at or above it, the next drop below it sends a new email.

​
Track usage

  • GET /v1/account/usage returns one row per UTC day and model with the number of tasks and the credits charged. See Get daily usage.
  • The console shows the same usage, every credit movement of the account (purchases, holds, charges and releases), and exports usage as CSV.

​
Daily credit cap

Some plans carry a daily credit cap: the most credits that may be held in one UTC day. A task that would exceed it answers 429 daily_cap_exceeded. GET /v1/account shows the cap of your plan as plan.daily_credit_cap (null means no cap).

​
FAQ

No. The hold of a failed task is released in full, whatever the reason.
No. Cancelling a queued or processing task releases its hold at once, and a result that finishes after the cancel is discarded and never charged.
No. Validation errors, URL policy errors, 402, 429 and 503 happen before anything is held.
Email support@fiveapi.ai with your account id (acct_...).