Short answer: Kie.ai states that 1 credit equals approximately $0.005 and that failed tasks are never charged. A model listed at 11.5 credits per video second therefore costs about $0.0575 per second, and a model listed at 63 credits per video costs about $0.315. Convert the exact model row you use, multiply by retries and accepted outputs, and verify the conversion with one small invoice.
| Model row | Credits | USD | Note |
|---|---|---|---|
| bytedance/seedance-2per second | 11.5 | $0.0575 | Per second; the page shows 'from $0.057 per second'. |
| bytedance/seedance-2 fastper second | 6.8 | $0.034 | Per second; the page shows 'from $0.034 per second'. |
| bytedance/seedance-2-5per second | 17 | $0.085 | Per second; a newer version at a higher rate. |
| Google nano banana proper image | 18 | $0.09 | Per image, pro configuration. |
| Kling 2.6per video | 63 | $0.315 | Per video. |
| gpt-image-2-5-flareper image | 6 | $0.03 | Per image; economy variants start near 5 credits. |
The credit conversion is simple; the model row is not
Kie.ai publishes a fixed conversion of about $0.005 per credit and lists each model with a credit price. Multiplying the two gives a dollar figure: 11.5 credits per second is roughly $0.0575 per second. The arithmetic is trivial, and the published per-second dollar figure on the page matches it, which is a useful consistency check.
The hard part is choosing the row. The catalog has hundreds of entries across video, image, music, and chat models, and similar names can differ by version, resolution, or tier. Seedance 2.0 standard, Seedance 2.0 fast, and Seedance 2.5 are three rows at three rates. Pick the identifier your integration actually sends, not the family name from a blog post.
- Convert credits with the price you actually paid, not a remembered conversion from an earlier top-up.
- Price one request end to end, then multiply by the attempts your acceptance rate implies.
- Keep image and video lines separate; a cheap image row does not offset an expensive video row.
- Recheck the model row before a batch, because a version rename can move the bill without a headline change.
Video batches: credits per second versus per video
Video rows mix per-second and per-video units. The Seedance rows bill per second, so a longer clip costs proportionally more. Kling 2.6 bills per video at 63 credits, so the dollar cost is fixed regardless of runtime within the model's cap. Comparing a per-second row with a per-video row using the raw numbers is meaningless; convert both to cost per accepted clip at your target duration.
For a ten-second accepted clip, Seedance standard at 11.5 credits per second costs 115 credits, or $0.575. Kling 2.6 at 63 credits per video costs $0.315. The per-video row wins on price for that duration, but resolution, motion quality, and audio differ. Validate on your own prompts before choosing on credits alone.
Failed tasks and retries
Kie.ai's page states that failed tasks are never charged. If that holds for your workflow, a retry loop is cheap: rejected generations cost review time but not credits. Confirm it with one invoice that includes a deliberate failure, because the distinction between a failed task and a low-quality successful task is where the cost hides.
Low-quality generations are billable. A cinematic prompt that produces unusable motion still consumes the credits. Model your budget on accepted outputs, not attempts, and include the reviewer's time in the comparison if the provider choice changes how many attempts are needed.
Prepaid credits also change the risk profile. A failed batch does not produce a refundable invoice line; it consumes balance. Keep a small reconciliation sheet that records the batch, the credits before and after, and the accepted outputs, so a mismatch between the expected and observed consumption is visible within one batch rather than at the end of a quarter. That discipline costs a few minutes and makes every later estimate more trustworthy.
Worked budget: 500 short clips
Five hundred accepted eight-second clips at an 85% acceptance rate need about 588 attempts, or 4,706 billable seconds. At Seedance standard's 11.5 credits per second that is 54,119 credits, about $270.60. At the fast row's 6.8 credits per second it is 32,001 credits, about $160.00. The fast row is 41% cheaper, and the difference in motion quality decides whether that saving is real.
Add a separate line for stills if the workflow uses reference images. A batch of 2,000 nano banana pro images at 18 credits each is 36,000 credits, or $180.00. Stills and video are different meters; keep them in separate budget lines so a surprise in one does not hide inside the other.
Buying and rechecking credits
Credit balances are prepaid, so unused credits are a working-capital cost, not just a price. Buy in increments that match a validated batch rather than a year of projected volume. Keep the purchase price, the dated conversion, and one invoice that shows credits consumed per task, and reconcile before the next top-up.
Rates and the credit value can change. The table above carries a retrieval date because the conversion is a published estimate rather than a contract. Before a large batch, load the pricing page, confirm the specific model row, and compare the implied dollar rate with the per-second figure the page shows. If the two disagree, trust the one your invoice uses and report the discrepancy.
Convert a batch to a monthly budget
Enter the dollar price of one billable attempt (credits converted at the published rate), your measured acceptance rate, and fixed costs.
Planning result
Review the example inputs, replace each rate with the exact current value from the linked source, then calculate. APIDir does not send these values to a provider.
Questions developers ask
How much is one Kie.ai credit worth?
Kie.ai states that 1 credit is approximately $0.005. A model priced at 11.5 credits per second therefore implies about $0.0575 per second.
Are failed Kie.ai tasks charged?
Kie.ai's pricing page states that failed tasks are never charged. Confirm the behavior on your own invoice before relying on it for a retry-heavy workflow.
Why do some Kie.ai models bill per video and others per second?
The provider sets the billable unit per model. Convert both to cost per accepted output at your duration and resolution before comparing.
Should I buy a large credit bundle?
Buy in increments that match validated batches. Prepaid credits are a working-capital cost, and rates or model rows can change before you consume them.
Sources and check dates
Every rate in this guide was retrieved from the linked page on Nov 13, 2026. Prices can change; recheck the source before purchasing.