> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alesta.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Credits

> Understand Alesta credit allowance, usage, reset behavior, and mid-run exhaustion.

Credits measure eligible paid work in a workspace. The free domain-first profiling run is zero-rated, so it does not consume a paid credit allowance.

## Find credit use

The Company-panel credit indicator opens Billing. The Billing credit card can show:

* credits used;
* the current maximum when the plan is metered;
* percentage used;
* limit-reached state;
* next reset date when provided;
* unlimited state when the server reports no cap;
* no-allowance state when the plan includes no credits.

The application calculates the displayed percentage from the raw used and maximum values returned for the current workspace.

## What can consume credits

The server decides which operations are metered. Eligible examples can include:

* new Pro chat turns and assistant tool work;
* company-description corrections;
* generated-document corrections;
* competitor additions, removals, swaps, or batch changes;
* signal improvements;
* other model-backed actions exposed by the current workspace catalog.

Do not rely on an old per-action estimate. Review the current plan and any action-specific message before submitting.

## Free workspace behavior

The free profiling run remains zero-rated even when the Free plan has no monthly paid-action credits. A locked edit or chat control indicates that the action belongs to a paid plan; it does not mean the free baseline itself failed.

## When the limit is reached

A metered workspace reaches its limit when used credits meet or exceed the current maximum. A new action can be refused before it starts.

If a run exhausts credits mid-flight, Alesta can stop it with **Stopped: out of credits** and a Billing action. Treat this as a terminal capacity result, not a provider connection error.

<Steps>
  <Step title="Open Billing">
    Confirm the selected workspace, used amount, maximum, and reset information.
  </Step>

  <Step title="Review the interrupted work">
    Check Chat, Signals, document state, or active workspace actions to identify
    what completed before the stop.
  </Step>

  <Step title="Choose the appropriate capacity path">
    Wait for the reported reset or ask the workspace Owner to review current
    plan options.
  </Step>

  <Step title="Retry one intent">
    After capacity is available, retry only the unfinished action. Idempotency
    and target locks protect against duplicates, but you should still confirm
    the result first.
  </Step>
</Steps>

## Unlimited and no-allowance states

* **Unlimited:** the server reports no cap. The card shows the used count without a percentage bar.
* **No credits included on this plan:** the maximum is zero and nothing has been spent. This is not the same as a limit that was consumed.
* **Limit reached:** a real allowance was exhausted, or a zero budget already has recorded spend against it.

## No separate wallet

The current application treats capacity as part of the plan. It does not expose a separate prepaid credit wallet in Billing.

## References

* [Billing](/billing)
* [Workspace actions](/workspace/workspace-actions)
* [Chat and logs](/workspace/chat-and-logs)
* [Locked and unavailable actions](/troubleshooting/locked-and-unavailable-actions)