SAVI

Stop Runaway Agents before they turn into unexpected costs

SAVI watches each agent's call rate, output size and spend as calls arrive, flags a loop pattern, and sends a plain-language alert with the cost context. This page covers runaway agents. For all spend types, see Anomaly Detection.

  • Detects looping behaviour as calls arrive, against each agent's own history
  • Cost and reliability scores show what kind of problem you have
  • Every incident explains which signals fired and why

Autonomous agents can quietly use up your AI budget overnight

Modern AI agents are autonomous: they retrieve documents, call APIs, summarise results and loop until done. Without guardrails, one misconfigured agent can make thousands of identical tool calls through the night. Finance sees the damage on the monthly invoice, not at 11:43 PM when it started.

One runaway loop adds up fast

A loop that runs all night can produce a very large bill. Standard budget alerts fire daily or weekly, after the damage has built.

Triage by hand takes hours

Without runtime detection, engineers read logs, find the looping agent and redeploy, which costs hours on top of the spend.

Post-mortems need a record

Without per-call logging you cannot show what happened, when it started or what it cost. A record makes the post-mortem quick and factual.

1
Every call is observed
All LLM requests pass through SAVI's monitoring layer.
2
Unusual activity is scored against the agent's baseline
A sudden spike in call rate stands out against that agent's own history.
3
Runaway output is detected
When an agent generates far more output than it takes in, SAVI raises its score.
4
Signals are combined into one verdict
Cost and reliability signals are weighted together. Critical alerts need signals to agree, so one number does not trigger a false alarm.
5
Your team is notified
When the score crosses a threshold, your Slack or PagerDuty channel is alerted and the dashboard updates.

Detection pipeline

Every call checked against the agent's own history

SAVI scores each AI request as it arrives. It compares an agent's call rate with its own history and watches for output far larger than the input. Signals are combined, and a critical alert needs more than one of them to agree. Different workloads behave differently, so SAVI uses thresholds set for each type. More signals, such as repeated tool use, are being tested.

  • A small SDK wrapper for the major providers
  • Thresholds set for each workload type
  • A clear path from normal activity to detection, alert and investigation

Flag, alert and investigate without stopping agents

When a threshold is crossed, SAVI flags the incident and sends a structured alert. Pausing an agent is an opt-in, so you decide how much SAVI does on its own.

  • Alerts to Slack, PagerDuty, email or a webhook
  • A live view of incidents as they are detected
  • Alert context includes the signals that fired, the score and the cost so far
Agent
summarise-pipeline-v2
Loop Pattern
247 calls/min
critical
Estimated cost exposure
$38,200 if unchecked
warning
Pause signalled (opt-in)
11:43:18 PM

Example alert in a finance channel

timestampagenttokenscost impactdecisionmodel
11:43 PMsummarise-pipeline-v22.4M$38,200Pause signalledgpt-4o
09:18 AMcustomer-support-bot180K$420Alertedclaude-3-5
Yesterdaydoc-retrieval-agent890K$12,100Pause signalledgemini-1.5
2 days agoinvoice-processor44K$110Loggedgpt-3.5
3 days agocode-review-bot640K$7,800Pause signalledgpt-4o

Swipe to see all columns →

Example data. Agent loop events, 5 of 23 this month

A tamper-evident record of every detection

SAVI records every detection event: the agent, token counts, cost impact and the response. Entries in the audit log are signed, so an edit after the fact shows. When audit or the board asks what your AI did and what it cost, the record is already there.

  • Signed entries, so changes after the fact show
  • Export as JSON, or send to your security tools
  • Role-based access, so people see what their role needs

Plain-language explanations on every incident

Every alert comes with a plain-English explanation of what triggered it, written for operators and not only engineers. SAVI tells you which pattern fired, how far above normal it was, and what it means for your AI budget. You do not need to decode scores or read log files.

  • Every alert names the pattern that fired, how far above normal it was, and the estimated cost impact
  • Plain-English summaries for operators and compliance reviewers
  • Mark an alert as a true or false positive to help tune detection
Agent
summarise-pipeline-v2
Pattern detected
Call velocity spike
critical
How far above normal
3.8x the 7-day baseline
Plain-English summary
This agent made 47 calls in 5 minutes, nearly 4x its usual rate. Cost exposure: $38K/hr if unchecked.

Example alert detail

What detection gives your team

 
Each call is scored as it arrives, so detection does not wait for a daily report
 
Call rate is compared with each agent's own history, not a global average
 
Pausing an agent is your choice, so SAVI does not act without your say

Do you know if your agents are using your AI budget well right now?

6 questions. Answer honestly.

Can you see every LLM call across your agents as it happens, not on a daily report?

Do you know which agents call the same tool with identical inputs again and again?

If an agent started a loop at 11 PM tonight, would you know before 9 AM tomorrow?

Can you spot a runaway agent without waiting for an engineer to go on call?

Do you have an audit trail of AI agent actions that your compliance team can open today?

Could your organisation absorb a large runaway loop that was found days after it started?

This checks one slice of your AI estate. Take the full AI Cost Ownership Assessment →

Find runaway agents when they start, not on the invoice.

SAVI detects looping agents as calls arrive and sends plain-language incident reports your compliance team can use.