Feature
Key Spend Limits
Set a usage ceiling on each Universal API key and notify the owner before production traffic hits the wall.
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
What your team gains with Concentrate
A hard ceiling per key
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.
Warn before the wall
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.
See which keys are close
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
Why limits belong on keys — not one global cap
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.
Team leads
Give each app a budget that matches its expected usage instead of sharing one org-wide pool.
Platform engineering
Pause or raise a single key when a deploy misconfigures prompts or models without affecting unrelated services.
Finance
Pair limits with cost attribution so caps map to real owners.
Early warning
Alert at 80% (or your chosen threshold) so the owner acts before requests start failing.
Feature basics