Top up and understand the balance
Top up the active workspace and understand available, total, and reserved balance.
Last updated on
The Balance page shows funds for the active workspace. Check the selected workspace before paying or investigating a request.
Top up the active workspace
- Open Balance and select Top up.
- Use a payment method shown for the current payer profile.
- Enter an amount at or above the minimum displayed in the form.
- Complete the external payment or create the bank invoice, then return to the balance page to check status.
The minimum is a current cabinet value, not a permanent amount from a guide.
Use the method for the payer profile
- An individual profile is offered card and SBP controls.
- An ООО profile uses a bank invoice generated from the company's saved billing details.
- An ИП profile uses a bank invoice generated from the entrepreneur's saved billing details.
Update the payer details in Settings. Use only the methods shown by the form; this guide does not promise support for a fixed card brand, country, alternative currency, or payment method.
Read the three balance amounts
| Amount | Meaning |
|---|---|
| Available | Funds that can be used for a new request now. |
| Total | The ledger balance before active request reservations are subtracted. |
| Reserved | Estimates temporarily held for requests that are still being processed. |
Available balance equals total balance minus active reservations. Parallel requests have separate reservations, so the reserved amount can rise during agent or batch work.
Understand a reservation
Before a request starts, provod.ai estimates its cost from the input and requested output limit, then reserves that amount. The reservation prevents the same funds from being promised to concurrent requests. It is an estimate, not a hard spending cap.
After settlement, confirmed usage is charged in full even when it exceeds the estimate. The difference is debited from total balance and can leave too little available balance for the next request. Unused reserved funds are released. Use API-key spend limits for budget control, while allowing for the same estimate-versus-final-charge boundary.
Know when a request is charged
A request that fails before any model output or reported usage is confirmed releases its reservation without a usage charge. If a stream delivered part of the output or usage was confirmed before interruption, that confirmed portion can be charged. Do not blindly retry a stream after output starts because that can repeat work and cost.
Check a pending payment
Check the operation status on Balance and refresh the balance. If a confirmed payment is still missing, do not create a duplicate payment until its status is checked. Send support the payment or order ID, approximate time with timezone, receipt, and active workspace name. Never send payment credentials or a complete API key. Confirmation time is not guaranteed.