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

# Entity limit

> Get notified immediately when a key, user, team, or organization crosses a percentage of its spend limit

Entity limit alerts you the moment anything a request bills against — the API key, your user, its team, or the organization — crosses a percentage of one of its spend limits. Unlike [key exhaustion](/docs/alerts/key-exhaustion) — which forecasts ahead — entity limit is reactive and fires as soon as the threshold is actually hit.

## When to use it

* You want to know the instant a key, team, or organization crosses, say, 80% or 90% of a cap.
* A safety net under [key exhaustion](/docs/alerts/key-exhaustion) — the forecast misses sometimes, the threshold doesn't.
* Entities with predictable, steady usage where a flat percentage is the most natural signal.

Entities without a spend limit are skipped — there's nothing to measure against. Set a period or total limit on the entity first.

## What you configure

| Setting                  | What it does                                                                                                                                                                                             |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Threshold Percentage** | Percentage of a limit at which the alert fires (e.g. `80` for 80%). Every configured limit across the chain is checked — period and total alike — and the alert reports whichever is closest to its cap. |

This is a reactive alert — no schedule, no scope picker. It evaluates each time a key is used.

## How you're notified

Email and/or SMS, based on your preferences in **Settings → Notifications**. The notification names which entity crossed its limit. A cooldown prevents repeat notifications while usage stays above the threshold. See [the alerts overview](/docs/alerts/overview) for delivery details.