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.…