Cost and usage
The figures at the top show spend, requests, tokens and cache savings for the range you pick, each compared with the same length of time before it. Projected this month shows where this month’s spend is heading at its current pace. When a monthly budget applies, the projection is drawn against it and says Over if it will pass it. Select it to open Budgets. The projection starts on the 3rd of the month, once there is enough to go on. Cache savings estimates what the requests answered by the semantic cache would have cost. Point at a figure with a dotted label to see how it is worked out. Below the figures, the Spend chart shows spend over time, and the rankings show who and what spent it: by project, AI system, person, model, provider, client or key. The ranking you pick also splits the chart. No AI system collects traffic on organization and personal keys.Guardrail violations
How often your guardrails fire, where, and what they do about it. Only counts are shown, never the text that was caught. The main figure is Violations per 1,000 checked: of every thousand requests the guardrails checked, how many something fired on. Requests no guardrail checked are left out, so a busy, unguarded AI system does not make the rate look better. Each request with a violation counts once, as Blocked, Masked or Logged only. The rankings put the highest rate first, so a small AI system that trips often is not hidden under a busy one. What was found names the kinds of thing caught, such as Email address. Two sections help you decide what to tighten:- Logged only lists guardrails that fired but only logged, so you can see whether to switch them to Block.
- On tool calls lists guardrails that fired on MCP tool arguments or results.