Administration

AI usage and budgets

Keep assistant usage predictable.

Pyron tracks how much every AI feature is used and lets you put a daily ceiling on that use. Both live under the Usage & budgets section of the AI provider settings, reached from the AI surface of the Setup area.

Usage at a glance

Within Usage & budgets, a summary reports assistant activity over a rolling 24-hour window. Five figures make up the summary:

  • SPEND (24H) — platform-billed AI spend across the past 24 hours.
  • TOKENS (24H) — the total tokens processed in that window.
  • INPUT TOKENS — the tokens sent to the model.
  • OUTPUT TOKENS — the tokens the model returned.
  • ASSISTANT TURNS — how many times the assistant replied.

These figures cover every AI feature in your organisation — the assistant and the builders that draft forms, reports, dashboards, and flow graphs — so a busy day and a quiet one read differently at a glance. When nothing has run in the window, the summary reads No assistant usage in the current window.

Read the summary before you set a budget: it shows what normal use looks like for your organisation, which tells you where a sensible cap sits.

Budgets

To cap what AI can cost your organisation, set a Daily AI budget (USD). This is a rolling 24-hour limit on platform-billed AI spend across everyone in your organisation. Leave the field empty and there is no organisation-wide cap — per-user limits still apply either way.

If your organisation runs AI on its own provider in place of the platform default, that usage bills your own account and does not count towards this budget; the cap covers platform-billed spend. See AI provider for the difference between the platform default and bringing your own provider.

The budget saves with the rest of the AI settings. Save changes and Discard stay inactive until you edit a setting; once you enter or change the budget, save to keep it or discard to return to the stored value. A saved budget takes effect from the next assistant turn.

Related

Need a hand? support@techly.au

Pyron Documentation