> For the complete documentation index, see [llms.txt](https://docs.scorable.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scorable.ai/concepts-and-examples/usage/usage-quotas-and-costs.md).

# Usage, Quotas & Costs

Scorable meters two different things, and it is worth keeping them apart:

|                         | What it counts                                                     | Where it applies                     |
| ----------------------- | ------------------------------------------------------------------ | ------------------------------------ |
| **Evaluator run quota** | How many evaluator and skill executions your organization performs | Per organization, per billing period |
| **Model spend limit**   | How much the underlying LLM calls cost in USD                      | Per user, per rolling 24 hours       |

The first is what your plan is sold on. The second is a guardrail against a runaway job. Hitting one has nothing to do with the other.

## Evaluator run quota

Every plan includes a number of evaluator executions per billing period. Your period is either daily or monthly depending on the plan; monthly periods run from the day your current plan was assigned, not from the first of the calendar month.

Two separate numbers govern it:

* **Included quota**: what your plan covers. Going past it does not stop anything; it starts accruing usage-based charges (see below).
* **Hard limit**: the point at which executions are refused. This is what protects you from an unbounded bill.

Sales or support can grant a **one-time additional quota** on top of both, which is consumed before either threshold applies. That is the usual way to unblock an organization that has hit its limit mid-period.

## Usage-based billing

Executions beyond your included quota are billed in **blocks**, not per run. Anything over the included quota is rounded up to the next whole block, so a single run past the threshold bills a full block.

Block size and price are plan-specific; check the Subscription page for yours. Free plans have no block pricing; they simply stop at the limit.

## Whose key pays for the model call

Model calls can run on Scorable's provider keys or on keys your organization connects itself. See [Models](/concepts-and-examples/usage/models.md) for how to connect one.

* **Scorable keys**: the model provider bills Scorable, and the cost appears against your account.
* **Your organization's keys**: the model provider bills you directly. Scorable does not mark up or re-bill these calls.

The Usage tab reports the two separately, so you can see how much of your model spend runs on which.

This choice is independent of the evaluator run quota: an execution counts against your quota whichever key served the underlying model call, because the quota measures platform usage, not model cost.

## Daily model spend limit

Each user has a cap on how much their model calls may cost in any rolling 24-hour window. Reach it and further model calls are refused until the window rolls forward; nothing else about your account changes.

Set your own under **Settings → Account**:

* Leave it on **Use plan default** to inherit the limit your plan sets.
* Choose **Set my own limit** to lower it. That is worth doing before a large backfill, or any job where a bug could loop.

You can raise it up to the maximum your plan allows, which is shown next to the field. On plans where the default and the maximum are the same, the limit can only be lowered.

{% hint style="info" %}
The cap covers **every** model call made through Scorable, including calls served by your organization's own provider keys. It limits spend routed through the platform, not spend billed to Scorable, so a user on their organization's own keys is still subject to it.
{% endhint %}

Two further points worth knowing:

* **Changing plans re-applies the limit.** An upgrade raises everyone still on the plan default. If you have explicitly set your own number, that choice is kept. If an upgrade appears not to have raised your limit, check whether you set one yourself.
* **Administrators can lift a single user** above what their plan allows, from the Django admin. Ask support if you need this.

## The Usage tab

**Settings → Usage** shows the current period and:

* **Evaluator run quota**: executions used against your included quota for this period.
* **Model costs — Scorable keys**: spend on calls served by Scorable's provider keys.
* **Model costs — organization keys**: spend on calls served by your own connected keys.
* **Your daily spend limit**: the cap currently in force for you, after any plan clamping.

The cost figures cover the displayed period, while the spend limit is a rolling 24-hour window, so the two are not directly comparable.

## Self-hosting

Self-hosted deployments do not run Scorable's plan model by default: quotas are not applied, and spend caps come from a single deployment-wide setting instead. See [Self-hosting](/self-hosting.md#capping-model-spend-per-user).