Limit
Per key
Alert
Threshold
Owner
Team
Budget per key with threshold alerts before the limit is reached.
Key
support-prod
Production support app key.
Threshold
80%
Notify when usage approaches the limit.
Owner
Support
Team responsible for the spend.
New capabilities
Attach a usage limit to each key that represents an app or team, so one workload can't quietly burn the budget the rest of the company depends on.
Notify the owner when a key crosses a chosen percentage of its limit, so a busy key gets raised or paused on purpose rather than failing mid-traffic.
Use spend by key to spot the keys approaching their limit, so you act on the one that matters instead of watching a single global budget.
Who Concentrate is designed for
A key usually represents one app, team, or environment. A limit on that key stops one workload from consuming credits meant for the rest of the company, while spend tracking shows which keys are approaching their ceiling.
Give each app a budget that matches its expected usage instead of sharing one org-wide pool.
Pause or raise a single key when a deploy misconfigures prompts or models without affecting unrelated services.
Pair limits with cost attribution so caps map to real owners.
Feature basics
Alert at 80% (or your chosen threshold) so the owner acts before requests start failing.