> ## Documentation Index > Fetch the complete documentation index at: https://docs.protodesk.io/llms.txt > Use this file to discover all available pages before exploring further. # Buy credits and understand your balance and usage > Read monthly, bonus, and purchased balances; check recent spending; and understand credit purchases and failed-run deductions. Use **Evelin AI → Usage** to understand your workspace's AI balance, recent spending, and credit history. Credits are shared by the workspace, not held separately by each teammate. ## Read the balance correctly **Available credits** is the total remaining balance. It already includes the remaining monthly, bonus, and purchased credits; do not add those balances to it again. The balance card also shows: * **Monthly allocation:** the plan's included allowance, not necessarily the amount still available. * **Purchased:** the remaining credits added through credit-pack purchases. These are preserved when the monthly allowance is refilled; the product labels them as not expiring. * **Bonus:** the remaining promotional or trial credits. * **Last refill:** the most recent recorded allowance refill. Credits are spent from the remaining monthly allowance first, then bonus credits, then purchased credits. When an allowance refill occurs, it replaces the remaining monthly allowance rather than adding unused monthly credits on top. Purchased and bonus balances are kept separately. **This billing cycle** measures how much of the included monthly allowance has been used. It is not a total of every credit spent from every balance. If you have used purchased or bonus credits, compare the usage charts and transaction history as well. Check the actual **Last refill** and billing records if an expected refill is missing. Do not assume that refreshing the page, buying a pack, or reaching the first day of a calendar month triggers a refill. Ask support to confirm an unexpected refill date, including on an annual subscription. ## Buy a credit pack Owners and Admins can use **Buy credits** from **Usage** or **Settings → Billing**, when the purchase option is available. 1. Confirm that you are in the workspace that needs the credits. 2. Select **Buy credits** to view the available packages. 3. Compare the package's credit quantity and total price. If the unit-price text disagrees with the total, do not rely on that unit-price comparison; ask support to clarify it. 4. Select a package, then **Buy \[quantity] credits** to continue to checkout. 5. Review the final package, total, and payment details before completing payment. 6. Return to **Usage** and check the purchased balance and **Credit history** after payment has been processed. Opening the package selector does not buy anything. A credit-pack purchase is a one-time top-up, not a subscription upgrade. It does not add seats, unlock plan-restricted features, or restore expired workspace access. If checkout is unavailable, ask an Owner or Admin to check Billing. If payment succeeded but credits have not appeared, refresh once and contact support with the workspace, package, approximate payment time, and order reference. Do not buy the same package repeatedly to resolve a missing balance. ## Compare the usage sections **Last 30 days** is a rolling window, separate from the billing cycle. **Daily usage** shows credit spending by date; hover, focus, or tap a bar for details. **By feature** shows how that spending is distributed across AI actions. Included AI actions and operation units are different measurements from paid credits. An operation unit is not another credit deduction. A workflow can contain several actions, so one run is not necessarily one credit. Use the estimate for the specific action and the recorded usage rather than a blanket price per click. **Credit history** shows the 30 most recent transactions, newest first. A negative usage entry records a deduction. Purchase, bonus, trial, refill, and adjustment entries explain balance changes; **Balance** is the total immediately after that transaction, not a separate amount to add up. A refill entry can represent only the net change needed to reset the monthly allowance, rather than the full allocation. The visible history is not a complete lifetime statement, and its 30 transactions are not the same as the chart's 30 days. Ask support if you need an older transaction investigated. Usage charts sum recorded usage deductions. A later credit adjustment can restore your balance without removing the original deduction from those charts, so chart totals are not necessarily net spending after adjustments. ## Failed, stopped, or repeated AI work An AI run marked failed does not necessarily mean that no credits were used. Some work is charged before the model request is made, and a later step can fail after earlier work has already consumed credits. There is no universal automatic credit-refund promise for every failed run. Private assistant answers have a narrower recovery rule: a failed or canceled turn without a saved answer can restore its answer credit through an adjustment. This is not a refund rule for every workflow, or a refund to your payment method. Check the balance and transaction history rather than assuming that every failed action follows the same rule. Before retrying repeatedly, compare **Credit history** with the run in **Monitor**. Give support the run reference, action, approximate time, and unexpected deduction. Do not include customer conversation text unless it is needed and appropriate for the investigation. When the balance is too low, metered AI actions can be blocked. That is separate from workspace expiry: running out of AI credits alone does not consume seats or turn a manual reply into an AI charge. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.