Use filters, charts, and model-call records to investigate Organization costs and understand separate Platform cost oversight.
Review Organization costs
Select the Organization, then open Costs. Organization Owner/Admin can use this page. Access to an individual Agent does not grant access to the Organization-wide report.
Review the summary, then narrow the report with the available search, Agent, model, and date filters. The summary, charts, and call list use the same filters. Review spend over time, average prompt-token usage, spend by Agent, and the cost-per-call distribution to understand changes in usage.
Set the reporting period and monthly breakdown
The default window is 30 days. The API supports seven-, thirty-, and ninety-day presets, explicit timestamp ranges, and calendar-month aggregations with spend totals, call volumes, and model-level cost distribution; see Reporting period and granularity.
Dedicated Agent Costs view
The Agent detail page features a dedicated Costs tab alongside Activity and Logs. It provides per-agent spend over time, token consumption distributions, model breakdown charts, and a filterable model-call ledger for that specific Agent.
Review model-call records
The list contains model calls, not one expandable row per Agent. Additional records load progressively. Use the displayed call count and filters to narrow a large result set. Refresh reloads the current report; it does not start a new cost-synchronization job.
Review Platform costs
Platform Administrators can open the separate Platform Costs surface to review cross-Organization reporting. It includes Organization attribution, unattributed spend, daily burn rate, remaining OpenRouter credit when available, and estimated runway. Unknown credit or runway is unavailable information, not zero.
Platform cost access does not grant access to Organization-owned prompts, credentials, Conversation content, or the Organization Costs page without the required Membership.
See Platform administration for the separate authority boundary.
Interpret the results
Cost data reflects stored model calls and the latest synchronization. An Agent represented in a usage metric is not necessarily running now. Historical records can remain after deletion, and recovered charges may increase past totals. Current Agent configuration and models observed in historical calls are different facts.
Deleted Agents and missing current keys
Cost records retain captured Agent and Organization identities and display names. Organization Owner/Admin can read soft-deleted Agent history; Agent assignments do not retain access after Agent deletion. Reading historical records does not require decrypting a current Agent key.
How cost attribution works
- LiteLLM spend logs
- Synchronization and attribution
cost_record- Authorized reports
OpenRouter generation charges can recover missing cost into the stored records. Reports read the latest completed synchronization. Conversation Messages and Tool Calls are separate records and do not calculate spend.
Read Costs and Spend Attribution for the data model.
Reporting boundaries
Cost reports support operational attribution. Platform Administrators can set per-Organization LLM spend limits and budget alerts via Platform Administration; reports themselves do not enforce per-conversation quotas, provide provider invoices or payment history, or allocate charges to individual Conversations or Tool Calls. Use provider billing records for invoicing and financial reconciliation.
Organization LLM spend limits
Organizations receive an automated LiteLLM team mapping to enforce monthly spend ceilings. When an Organization reaches its configured spend limit, model calls fail with an explanatory limit message until renewed or adjusted, while Agent containers and other platform features continue operating normally. Automated reconciliation and threshold alert CronJobs synchronize spend state and notify Organization owners as thresholds are crossed.
Different reporting windows, delays, recovered charges, rounding, provider adjustments, or calls outside the configured attribution path can explain differences from provider invoices.
Cost API and reporting windows
All requests require authentication. Organization summary, list, and filter endpoints require Organization cost permission. Per-Agent detail is authorized against that Agent. Platform cost endpoints require Platform Administrator authority. An Organization ID in an Organization route is the scope boundary, not an optional query filter.
GET /api/v1/organizations/{organization_id}/costs/summary?period=THIRTY_DAYS
GET /api/v1/organizations/{organization_id}/costs/summary?from_date=2026-09-01T00%3A00%3A00Z&to_date=2026-09-08T00%3A00%3A00Z&granularity=day
GET /api/v1/organizations/{organization_id}/costs?page=1&page_size=50
GET /api/v1/organizations/{organization_id}/costs/filters/agents
GET /api/v1/organizations/{organization_id}/costs/filters/models
GET /api/v1/organizations/{organization_id}/costs/agents/{agent_id}?period=SEVEN_DAYS
GET /api/v1/platform/costs/summary?period=THIRTY_DAYS
GET /api/v1/platform/costs?page=1&page_size=50
GET /api/v1/platform/costs/organizations?period=THIRTY_DAYSReporting period and granularity
Cost endpoints use a 30-day window by default. Select period=SEVEN_DAYS, period=THIRTY_DAYS, or period=NINETY_DAYS. For an explicit range, send from_date and to_date as timestamps. granularity selects minute, hour, day, or week series buckets. The summary returns the resolved window and granularity; use these fields rather than assuming a report covers all time.
Pagination and response fields
Record-list responses contain page, page_size, total, and items. Page size defaults to 50 and accepts 1–100.
Summary responses include from_date, to_date, granularity, total_spend, total_calls, active_agents, top_model, top_model_spend, avg_cost_per_call, avg_prompt_tokens, spend_over_time, avg_prompt_tokens_over_time, spend_by_agent_over_time, and cost_per_call_histogram.
Per-Agent history
Per-Agent detail queries stored costs for the requested window. It does not return lifetime key spend or force the status to stopped merely because a current key is absent. An inaccessible Agent returns 404 Not Found.
Cost data access
Organization-wide reporting requires Organization-level cost.read. Per-Agent reporting requires effective Agent cost access. Platform Administrator authority applies to separate Platform routes and does not grant Organization Membership.
Treat names, model usage, tokens, and spend as sensitive operational data. Keep LiteLLM keys out of reports and support tickets; do not export decrypted keys to reproduce attribution.