Signal
Spend change
Scope
Org + key
Sensitivity
Configurable
How far spend must move from baseline before the owner is notified.
Low
Large deviations
Only flag major spend changes.
Medium
Moderate
Default sensitivity for most teams.
High
Smaller changes
Catch unusual movement earlier.
New capabilities
Choose how far spend has to break from baseline before it alerts, so you catch real anomalies without drowning in noise from normal traffic swings.
Monitor spend by organization, team, user, or key, so the alert lands with the people who can actually shut down the runaway workload.
Catch a runaway agent loop or a bad prompt change the day it starts, instead of finding it on the invoice three weeks later.
Who Concentrate is designed for
A spend spike alert compares current usage to a workload's baseline and notifies the owner when the gap is large enough to matter. That turns month-end surprises into same-day signals — often before a key limit is hit.
See unusual movement by org or team without waiting for the provider invoice.
Scope alerts to the key behind a production app so the right team gets the notification.
Catch agent loops, prompt regressions, or model swaps that doubled token volume overnight.
Choose how far spend must deviate before alerting so normal traffic swings do not flood inboxes.
Feature basics