Skip to main content
The AI Usage page shows how your organization is consuming AI credits against its contract: how many credits are allotted, how many you’ve used in the current billing period, what’s left, and which flows are driving that usage.
AI Usage is an early-access page. Reach out to your Statisfy contact to request access.

​
Accessing the AI Usage Page

Click AI Usage in the left navigation. The page loads your credit summary, usage by source, and the usage log for the current billing period. If no AI credit contract has been configured for your account yet, the page shows a message asking you to reach out to your Statisfy contact to get one set up.

​
Credit Summary

Four cards at the top of the page summarize your contract:
  • Contract period — The start and end dates of your current billing period. Usage shown on the page is limited to this window.
  • Total allotted — The total credits included in your contract for the period.
  • Used to date — Credits consumed so far in the period.
  • Remaining — Credits left in the period (Total allotted minus Used to date).

​
The Overused State

If your usage exceeds the allotment, the Remaining card changes to Overused and shows how far over the allotment you are. Used to date turns red at the same time. Nothing is blocked when you’re overused; the page surfaces the overage explicitly so you can discuss it with your Statisfy contact instead of showing a silently negative remaining balance.

​
How Credits Are Computed

Every billable AI event falls into one of three rate tiers. Each tier has a per-run rate set in your contract: Credits for a source over a period are simply runs × tier rate. Rates are flat per run, not volume-based, and are set per contract by Statisfy.

​
Usage by Source

The Usage by source table breaks down consumption by what actually ran:
  • One row per Agent Studio flow, aggregated across all of that flow’s runs in the period.
  • A Stella (PPT) row for PPT generation triggered from Stella chat, which doesn’t run through an Agent Studio flow.
Each row shows the source name, its tier, the number of runs, and the credits used. A single flow can span more than one tier — for example, a flow with both an LLM step and an agent step bills each step at its own tier, and the row shows the combined tiers and total credits. Rows are sorted by credits used, and the table is paginated.

​
Usage Log

The Usage log table lists every billable event, most recent first, so you can drill into exactly what consumed credits. Each entry shows:
  • When — The date and time of the event
  • Use case — The type of AI work (for example, Agent Studio: LLM, Agent Studio: Custom Agent, or PPT Generation)
  • User/Flow — The user or flow that triggered the event
  • Credits Used — The credits billed for that event
The log is paginated at 20 entries per page. Use the Previous and Next buttons to move through it.

​
Billing Period Behavior

  • Usage is counted from the contract period’s start date (inclusive) up to its end date (exclusive). When a contract renews, usage at the boundary belongs to the new period and is never double-counted.
  • If your contract has no period configured, the page reports all-time usage instead.
Check the AI Usage page periodically as you scale up Agent Studio automations — the Usage by source table makes it easy to spot which flows are consuming the most credits before you hit your allotment.