Skip to main content
Every insight the AI Spend Agent produces is a finding. Each finding has a detection rule, an estimated dollar impact, a severity, and — where available — the attribution that pins it to a model, key, workspace, or user. This page explains how the agent generates findings, how they split between Anomalies and Violations, and how the Action Plan ranks them.

How findings are produced

  1. Sync — The agent pulls usage and cost from your connected providers on a schedule, and on demand when you click Sync now.
  2. Audit — When you click Refresh insights (or on the agent’s own audit cadence), the agent runs every detection rule against your current usage. This produces the finding set and the reconciliation summary for Recovery.
  3. Attribute — Where the provider exposes it, each finding is tagged with the model, key, workspace, or user that caused it, plus the pricing basis used to compute the discrepancy or opportunity.
The Refresh insights button in the top bar of the agent holds an Auditing… state while the job runs and refreshes the dashboard the moment it finishes. See Connect providers.

Anomalies vs. Violations

Every finding lands in exactly one of two views, based on its category: The split matters for what you can do with each:
  • Anomalies are optimization work — changes you make in your own stack (routing to a cheaper model, adding caching, revoking a stale key). They can’t be recovered as refunds.
  • Violations are disputable — the provider charged you something that pricing says they shouldn’t have. Billing-discrepancy violations back the refund claims you file in Recovery.
Both views share the same layout: a summary strip on top with counts and estimated impact per category, then a filterable table. Filter by severity, date range, and category. Click any row to expand the full explanation, attribution, and pricing basis.

The Action Plan

The Action Plan is a single ranked list of every open finding — anomalies and violations combined — sorted by estimated dollar impact, highest first.
  • The header shows the total identified opportunity: the sum of estimated impact across every finding in the list.
  • Each row shows the finding’s title, severity, human-readable explanation, and its individual estimated impact.
  • Work top-down. The highest-impact items are the ones worth doing first, regardless of category.
Refund claims are tracked in Recovery, not on the Action Plan. Action Plan is your optimization to-do; Recovery is the money the agent is chasing back on your behalf.

Severity

Every finding carries a severity: high, medium, or low. The detection rule sets severity based on how confident the agent is in the finding and how material the impact is likely to be. Severity is separate from dollar impact. A low severity finding can still be worth acting on if it recurs across many keys or workspaces, and a high severity finding isn’t always the biggest single line item.

When findings change

The agent re-derives findings on every audit. That means:
  • A finding that no longer applies after your next audit disappears from the list.
  • Estimated dollar impact can move up or down as the underlying usage window shifts.
  • Opening a refund claim against a billing-discrepancy violation flips that finding’s claim-opened marker so you can’t double-file. The finding itself keeps showing until it’s fully resolved.