Skip to content

Budget

Budget shows spend against limit, burn rate, and projected month-end spend — display-only. The monthly limit itself is authored in System → Budget; this page only visualizes spend-vs-limit and per-scope (model/provider) caps with their month-to-date and day-to-date spend.

The Budget panel showing spend, monthly limit, daily burn rate, and projected-monthly tiles, a budget-consumed gauge, and a cumulative spend line chart.
Monitoring & Reporting → BudgetCitadel synthetic data on a non-production Arbitex demo instance. Never client data.
  1. Open Monitoring & Reporting → Budget. Pick a range for the Cumulative spend chart.

  2. Review Spend (USD), Monthly limit (reads “Not set” with a pointer to System → Budget when none is configured), Daily burn rate, and Projected monthly (flagged if the projection would exceed the configured limit).

  3. Review Budget consumed — a percent-of-limit gauge, shown only once a limit is configured.

  4. Review Cumulative spend — daily and running-total lines.

  5. Use the Per-scope spend caps table’s Group by control (Model / Provider) to see each scope’s daily/monthly cap plus its month-to-date and day-to-date spend. This reads “Temporarily unavailable” if the platform per-scope read can’t be reached, or “No per-scope caps configured” if the read succeeds with nothing authored.

Terminal window
curl -X POST "https://admin.arbitex.ai/api/v1/admin/monitoring/budget/summary" \
-H "Authorization: Bearer $ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{}'

Per-scope caps read budget/scope-caps.

Available on every plan. Setting the monthly limit happens in System → Budget — this page is view-only.

Per-scope caps are a platform cross-plane read; air-gapped deployments without a platform path show “temporarily unavailable,” never a fabricated cap.