// Track

FinOps for AI Agents

Never Get Surprised by an LLM Bill Again

Per-agent daily budgets, model tier routing, loop detection, cost attribution events, and the CFO daily report — the complete FinOps stack for autonomous AI agents. Prevent the $200 weekend before it happens.

Recommended: Complete Agent Authority & Safety Systems first

6 lessons~53 min total

Lessons are shown in recommended order. Complete them in sequence for the best experience — or jump to any lesson.

Lesson 204·9 min read

The $200 Weekend Problem — Why AI Agents Need FinOps

Uncapped LLM spend is not a billing quirk — it is a system design flaw. Real war stories from runaway agent spend, and why FinOps is the first layer every agent platform needs before it goes live.

Lesson 205·8 min read

Model Tier Routing — Automatic Downgrade Logic

Four model tiers, one enforcement layer. How principal-broker routes agents to the cheapest model that meets their quality ceiling — and blocks anyone who tries to reach above their tier.

Lesson 206·9 min read

Per-Agent Daily Budgets — 80% Warning, 100% Stop

The BudgetEnforcer implementation: per-agent daily limits from the DAILY_BUDGETS_USD map, soft warnings at 80%, hard stops at 100%, and the $25 global ceiling that blocks everything when the fleet has spent too much.

Lesson 207·10 min read

Loop Detection — Jaccard Similarity and Session Termination

The Loop Detector uses Jaccard token overlap to score consecutive agent turns. Three similar turns triggers a VP warning. Five triggers forced termination. Here is how it works and why it is the cheapest insurance in your agent stack.

Lesson 208·9 min read

cost.attributed Events — Every LLM Call Tracked

The CostRecord data model, the emit callback pattern that fires a cost.attributed event on every LLM call, and the CFO daily report structure that aggregates spend into a format the operator can act on.

Lesson 209·8 min read

Budget Override With Audit Trail — Knox Approval Flow

The admin REST endpoint for budget overrides: BROKER_ADMIN_TOKEN enforcement, the BudgetOverrideInput schema with mandatory reason field, what the audit trail captures, and the Knox approval flow that makes overrides accountable.