Track AI Generation Costs Without Confusing Estimates, Jobs and Invoices

A completed video tells you which take you used. It does not tell you how many attempts you paid for, whether an unfinished request is still running, or whether an estimated cost has been reconciled with an invoice.

FablessBridge's production-ledger guide separates those questions. Here is a reusable recording procedure based on that guide. This post describes a workflow; it does not report a newly executed integration or cost benchmark.

1. Give every request its own row

Record the project, attempt ID, model, access route, input asset, output conditions and submission time. Five seconds at one resolution and a longer clip at another resolution are different conditions, even if the model name matches.

For a retry, create a new row and relate it to the attempt being corrected. Do not overwrite the earlier request: that would hide how many attempts were made for the same purpose. Keep API keys and authentication headers out of the ledger.

2. Separate the estimate from the bill

An estimate needs its pricing formula, conditions, currency and the date you checked it. The billed amount needs a separate reconciliation against the provider's usage statement.

If that reconciliation has not happened, leave the billed value blank and mark it unconfirmed. A blank amount is not a zero-cost generation. Similarly, credits supplied through a web product are not evidence of a model's general API price.

The source links to a drip-video comparison record, where estimated Higgsfield costs and free Kling Web credits are distinguished, and an API prototyping record. Those are production references, not price promises for a new run.

3. Track the request and the asset separately

Use request states such as not submitted, accepted, processing, succeeded, failed and unknown. Separately record the output location and whether the asset was adopted or rejected.

A timeout is not proof that generation failed. Before sending an unknown request again, check whether the existing request can be queried. A failed status is also not sufficient evidence of no charge; billing reconciliation answers a different question.

4. Keep rejected attempts in the total

The source uses this fictional example. Assume identical model, route and five-second output conditions for all three rows:

The estimated total is JPY 60. The actual bill is still unconfirmed. There is one adopted clip, but the two rejected attempts remain part of its production history. These figures illustrate bookkeeping only; they are not actual charges or a provider's unit price.

5. Review what your ledger can establish

Before using the record for the next project's budget, check that each retry has a distinct row, the output conditions are recorded, estimates and reconciled charges remain separate, and adoption has not erased rejected attempts. Keep the spending cap and retry rules alongside the ledger.

This makes it possible to explain what was tried, what was retained and which costs are still unknown. It does not, by itself, prove a saving or predict a new project's final cost.

From an experiment to a video brief

When commissioning a product video, bring the intended output and revision scope into the discussion. A record of the attempts helps explain which generation or editing decisions remain open.

Read the original Japanese guide, browse FablessBridge production examples, or discuss a video brief. Our business contact is [email protected].

Disclosure: This article was prepared with AI assistance from FablessBridge's published guide. The three-row ledger is fictional; no new API requests, invoice reconciliation or cost measurements were performed for this post.