app.delta-v.dev/governor
Delta-V
AI SPEND GOVERNOR
← DELTAV.INFO
→ GOV ΔV · BILLING DAY 22/31
SCRIPTED DEMO
COPILOT · TOOLS ONLY, NO RAW DATA
GET_SPEND_SUMMARY()
GET_FORECAST()
Through day 22 of 31 you have spent $41.2k of the $50.0k budget, 83% used. At the trailing burn of $1.87k/day the month projects to $58.1k, which lands $8.1k over. The projection is on the canvas. The detector also flagged Tuesday, ask about the spike.
why did spend spike tuesday?
DETECT_ANOMALY()
GET_ATTRIBUTION()
Found it. Tue Jul 7: llm spend hit $3.14k against a 14 day median of $1.24k, 2.5x, above the 1.8x alert threshold. Attribution points at claude-opus batch jobs: retries tripled between 02:00 and 06:00 after a malformed payload. That run added $1.9k of excess.
DAILY LLM SPEND · 14D
PINNED ✓
$3.14K 1.8x 1.4x MED JUN 26 JUL 7 JUL 9
show routing economics
GET_ROUTING_ECONOMICS()
Two runs of the same 30 days of traffic, replayed deterministically. Everything on opus versus your routing rules: drafts and classification to haiku, summaries to sonnet, complex reasoning stays on opus.
ALL OPUS$63.4K
WITH ROUTING RULES$41.2K
-$22.2K/MO
35% SAVINGS DELTA
spend by team and model
GET_ATTRIBUTION(TEAM × MODEL)
Month to date by team and model. support-ai on opus is the heavy cell at $11.8k, that is where Tuesday's retries landed. Pin it to keep watching.
SPEND · TEAM × MODEL · $K
PINNED ✓
OPUS
SONNET
HAIKU
platform
9.4
3.1
0.8
growth
6.2
2.4
1.1
support-ai
11.8
1.9
0.6
research
2.9
0.7
0.3
why did this get blocked?
CHECK_ROLE_GATE()
CHECK_IMPACT_GATE()
An agent tried to execute a change. Two independent checks ran before anything touched the gateway:
INTERCEPTED ACTION
apply_routing_rule(
  "draft_reply → claude-haiku"
)
ACTOR: finops-agent EST. IMPACT: $412/MO
GATE 1 · ROLE · CHECK_ROLE_GATE()
RUNNING…
FAIL
Is this actor allowed to execute at all? Role FINOPS is read-only. It can query every tool but cannot execute actions.
GATE 2 · IMPACT · CHECK_IMPACT_GATE()
RUNNING…
HOLD
Does the change exceed authority? $412/mo > $50/mo execute limit. This gate holds any change above authority, even for an ENG role with execute permission.
ACTION HELD
Blocked by two deterministic gates, each one on its own would have stopped it. The rule change is queued for human approval. Nothing was written to the gateway.
CODE DECIDES AUTHORITY · THE MODEL ONLY NARRATES THE VERDICT
TRY NEXT
CANVAS · SESSION ONLY
PIN CHARTS FROM CHAT →
SPEND MTD
$41.2k
BUDGET USED
83%
OF $50.0K
PROJECTED MONTH END
$58.1k
+$8.1K OVER
VARIABLE BURN / DAY
$1.87k
⋮⋮ FORECAST VS BUDGET · GET_FORECAST()
TRENDING OVER
BUDGET $50.0K $58.1K PROJECTED $41.2K TODAY JUL 1 DAY 22 JUL 31
ACTUAL
PROJECTION
BUDGET
ENFORCEMENT
01 traffic → your gateway
LITELLM / PORTKEY
02 delta-v meters + decides
03 caps written back → gateway
Delta-V is not in the request path. It governs by writing caps and routing rules back to your gateway. Enforcement applies to governed gateway traffic.
⋮⋮ PINNED · DAILY LLM SPEND · DETECT_ANOMALY()
$3.14K · RETRIES 3.1X 1.8x 1.4x MED JUN 26 JUL 7 JUL 9
⋮⋮ PINNED · SPEND BY TEAM × MODEL · $K MTD
OPUS
SONNET
HAIKU
platform
9.4
3.1
0.8
growth
6.2
2.4
1.1
support-ai
11.8
1.9
0.6
research
2.9
0.7
0.3