Skip to main content

Plan and actual

The first block on the Usage screen compares what your plan allows with what you have actually consumed in the current cycle, and projects where you land if the current pace holds.

Reading it​

  • Allowance — what the plan includes for the cycle, per model family: a request count and a token volume.
  • Actual — consumed so far in this cycle.
  • Projection — the end-of-cycle figure at the current daily pace. It is an arithmetic extrapolation of the days already closed, not a promise.

When the projection crosses the allowance, that is the moment to act — not the day the allowance is actually exhausted.

Notifications​

Two thresholds are watched for you: 90 % and 99 % of the allowance. When one is crossed, the people responsible for the account are notified by email. The notification fires once per threshold per cycle, so a busy week does not turn into a stream of duplicate warnings.

The cycle​

A billing cycle runs from your contract's anchor day to the day before the next anchor. The exact dates of the current cycle are printed at the top of the Billing screen — use those, not the calendar month, when you reconcile.

Spend by day​

Below the plan block, spend is charted per day, with the same totals available per month. The chart is built from closed days plus the running total of today, which is why today's bar keeps growing while you look at it.

Spend breakdown​

The breakdown answers where consumption and cost went. Filters let you narrow by period, public model, API key and project.

If your organisation has a detailed breakdown enabled, entries are listed separately; otherwise they are grouped. The same visibility rule applies to exports.