Skip to main content

​
Review the cost before submitting

Generation uses credits. Cost can vary with the operation, quality, duration, sample count, and account’s available credit categories. Check the current cost and settings exposed by your client before submitting. A displayed total balance does not guarantee that every credit is eligible for the selected workflow. An operation can be rejected when the eligible balance is insufficient, even when other credits remain.

​
Automatic reload

If automatic reload is enabled for the account, a generation submission can trigger a payment attempt to replenish credits. Review the account’s billing settings before running paid work through a connected client. Payment activity and generation credit usage are separate records. A generation that did not start does not, by itself, prove that an independent automatic reload attempt was not charged. Inspect billing activity as well as generation history when reconciling an unexpected outcome.

​
Repeated operations

Creation calls are non-idempotent: repeating one can create another task and use credits again. Reading an existing generation’s status does not consume generation credits or create more work. Keep the original receipt, reconcile uncertain submissions, and retry a failed status read through the same task. See tasks and results.

​
When credits are insufficient

Check the connected account, the credit categories eligible for the selected operation, and the account’s billing activity. Resolve the cause before making a new submission. If a payment attempt occurred, verify its outcome separately. Do not infer a refund or a payment outcome from a task status alone. Use the account’s actual credit and billing records for reconciliation. For current account options, open APOB. For submission, status, and output problems, follow troubleshooting.