Guide

Budgets and cost control

How spending is counted, the caps an administrator can set, the projection beside a capped Bot, and what happens when a cap is reached.

3 min read

How spending is countedCopy link to this section

Each run's cost is its tokens times the workspace's price table, in US dollars per million tokens for input, output and cached input; a few image and video models are priced per image or per second. The shipped prices are estimates, so columns read Cost (estimate) until an administrator saves the workspace's own prices under Prices; changing a price restates every month and is recorded in the audit trail. An optional yen rate shows amounts in yen as well; it is entered by hand, not looked up.

A run that finishes without reporting its usage is listed as Not counted rather than guessed at, and failed or stopped runs are not counted. Administrators see everything under Admin › Usage; each person sees their own spending, caps and Bots under Settings › My usage.

The capsCopy link to this section

Monthly caps count by calendar month in UTC. Whichever cap is reached first stops the run.

CapWhereAt the cap
Whole workspace, monthlyAdmin › UsageEvery Bot is paused.
One Bot, monthly (US dollars, tokens or both)Admin › Usage, or the Bot's profile under Monthly budgetThat Bot is paused for everyone.
One person, monthlyAdmin › Usage, By personThat person's next turn is refused; the Bots keep working for everyone else.
One group, monthlyAdmin › Usage, By groupIts members' turns are refused. Someone in two capped groups counts toward both.
Daily (workspace, Bot or person)Admin › Usage, Daily capsRuns are refused until midnight UTC.
Per runAdmin › Usage, Per-run ceilingThe run is stopped instead of finishing, and the person is told what it spent. It applies to chats, routines and Bot-to-Bot work.

Burn rate and days until the capCopy link to this section

Beside each Bot with a monthly cap in US dollars, Admin › Usage shows an Estimate with the method written under it:

  • Projected by month end: spending so far this month divided by the days elapsed, times the days in the month.
  • Days until the cap: what is left of the cap divided by the average spent a day over the last 7 days.
  • Otherwise it says the cap is already reached, or that the Bot is not on track to reach it this month.

WarningsCopy link to this section

At 80% of a cap, administrators get an in-app notification, and so do the Bot's owner for a Bot cap and the person for their own cap. Under Warning thresholds an administrator can choose up to five other percentages, such as 50, 80 and 90. Each threshold is announced once a month per cap, and every administration page shows a banner while a cap is close or reached. A sudden jump in a day's spending, at least three times the 14-day average, raises a separate alert.

When a Bot reaches its capCopy link to this section

The Bot is paused: new turns are refused, and nothing asks for approval to carry on. Caps are checked when a turn starts, so a turn already running finishes and spending can go slightly past the cap. A banner in the conversation and on the Bot's profile says why and when it starts again: on the first of next month (UTC), or sooner if an administrator raises the cap or grants an overage.

A member can choose Ask for an overage on a paused Bot and say why. An administrator grants extra US dollars or tokens for this month, or refuses; the grant ends with the month, and requests and decisions are recorded in the audit trail. Overages are for Bot caps only.

Last updated