Identity & Security
Anomaly detection
Watching spend or usage for sudden deviations from the normal pattern and flagging them the instant they happen, so a spike is caught on the request path rather than in next month's report.
Example
A workload that normally spends $40 an hour suddenly spikes to $1,600 an hour at 3 a.m. Anomaly detection flags the 40× deviation the moment it starts — while there's still time to freeze the key — instead of surfacing it in a report a day later.
This is a Tokenality concept. See how it works in the product overview or the live playground.
Related terms
Budget cap (hard cap)
A spending limit enforced before a call is sent, not an alert fired after. When the cap is reached, the next call is refused — no spend occurs. A hard cap is a circuit breaker; an alert is a smoke detector that may or may not wake anyone.
Binding key
A second factor attached to a virtual key so the key string alone isn't enough to spend. A token that leaks without its binding key is a dead key — exfiltrating the string buys an attacker nothing.
Spend control plane
The layer that governs AI spend across an organization: it issues virtual keys, enforces budgets before calls, attributes every dollar, and produces the audit record. "Observability" tells you what you spent; a control plane decides whether you spend it — the enforcement happens before the call, not after. (This is Tokenality's category.)