Skip to content

Cost

The Cost panel is a display-only cost-attribution dashboard: total spend, projected monthly spend, daily burn rate, budget-vs-actual (once a monthly limit is configured in System → Budget), spend over time, cost by model, and — where the platform per-scope read is reachable — month-to-date and day-to-date spend by model and provider. Cost-routing rules are authored elsewhere, in Models & Routing.

The Cost panel showing spend roll-up tiles, a spend-over-time line chart, a cost-by-model donut, and a per-scope spend caps table.
Monitoring & Reporting → CostCitadel synthetic data on a non-production Arbitex demo instance. Never client data.
  1. Open Monitoring & Reporting → Cost. Review the roll-up tiles: Total spend, Projected monthly, Daily burn, and Monthly budget (with percent used, or “Not set” if no limit is configured).

  2. Pick a Trend period (Day / Week / Month) to change the granularity of the Spend over time chart.

  3. Review Cost by model (a donut of spend share) and the grouped Cost by model — detail table (cost, requests, and average cost per request).

  4. Review Cost by scope (model / provider) for month-to-date and day-to-date spend per model or provider. This section reads “Temporarily unavailable” if the platform data path can’t be reached right now — never a fabricated figure.

  5. Scroll to the retained Cost rollups table for the raw per-window rollups (kind, window start, model, cost, requests, daily burn, projected monthly, trend).

Terminal window
curl -X POST "https://admin.arbitex.ai/api/v1/admin/monitoring/cost/breakdown" \
-H "Authorization: Bearer $ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"dimension": "model", "metric": "cost"}'

The spend trend reads cost/timeseries, the budget-vs-actual tiles read budget/summary, and the raw rollup table reads cost/list — all POST-only, account-scoped server-side.

Available on every plan. Setting a monthly budget limit is done in System → Budget — this page only visualizes it.

Cost telemetry is computed by the local control plane from its own request/token accounting. Cost by scope is a platform cross-plane read; in an air-gapped deployment without a path back to the platform it degrades honestly to “temporarily unavailable” rather than showing stale data.