Skip to main content
Agent Manager’s FinOps tooling gives you real-time visibility into LLM token usage and associated costs. You can monitor spending per agent and session, set expected burn-rate baselines, and receive alerts when agent costs deviate from normal behavior.

What FinOps tracks

Valuation rates

Token-to-USD conversion rates per model. Agent Manager uses these rates to compute cost estimates from raw token counts reported by the LLM provider.

Burn rates

Real-time USD spend velocity per active session. Sliding-window accumulators track cost per hour so you can detect runaway sessions before they become costly.

Historical trends

Daily cost aggregations over configurable trailing windows (7, 30, or up to 90 days) broken down by agent and organization.

Anomaly detection

Sessions whose burn rate exceeds a registered agent baseline by a configurable multiplier are flagged as anomalies, visible in the dashboard and via API.

Viewing cost data

Historical cost trends (trailing N days, default 7):
Cost allocation by agent and org:
Cost allocation broken down by LLM model:
Active session burn rates:
Returns one entry per active session with its cumulative USD spend within the current observation window. Cache ROI statistics:
Returns accumulated cache savings (USD), embedding costs (USD), and net ROI since the last application restart.

Configuring valuation rates

Agent Manager computes cost estimates using per-model token-to-USD rates. Retrieve the current rate table:
Register or update a model’s rates:
Rate updates take effect immediately — the new values are stored in an in-memory concurrent cache and applied to all subsequent runs.

Setting agent burn-rate baselines

Baselines define the expected normal USD/hour spend for an agent. Agent Manager uses baselines to identify anomalous sessions.
Set baselines after running your agents in normal conditions for a few days. Use the historical trends endpoint to determine a representative USD/hour figure for each agent.

Anomaly detection

When a session’s burn rate exceeds its agent’s baseline by a configured multiplier, it appears as an active anomaly:
An empty array means no sessions are currently anomalous.

Prometheus metrics

Agent Manager exposes FinOps data via Prometheus at the standard actuator endpoint:
Key metrics:

Health check

Returns system status including database connectivity, Docker availability (for the code sandbox), and any configured API provider health.
Use the cache impact time-series endpoint (GET /api/v1/finops/cache-impact) to measure how effectively your agents are leveraging semantic caching. Higher cache hit rates directly reduce LLM spend.