Skip to main content

Usage

Usage is the credit ledger for your workspace — what you spent this month, how it was distributed across days, what your balance looks like, and the auto-reload settings that keep you from running dry. It lives at /<workspace>/usage.

📷 Screenshot: Usage page with the month selector, credit summary cards, and the daily-spend chart.

Credits at a glance​

AI Expedite bills AI activity in credits. The exchange rate is fixed: 1 credit = $0.02 of underlying AI cost, regardless of which model an agent picks or which provider is upstream. Higher subscription tiers get a better purchase rate (more credits per dollar), but every tier consumes credits at the same rate, so the bill maps directly to AI work performed.

The page header shows the current month's spend, balance (credits remaining), and an estimate of days until empty at your trailing usage rate. The month picker on the right scrolls back through prior months for historical comparison.

Daily breakdown​

Below the summary, two charts:

  • Monthly Spend — credits consumed per day in the selected month, stacked by category (chat / agents / scheduled runs / system hooks). Hover for the exact daily value; click a day to drill into the executions that ran that day.
  • Monthly Total — running total against your starting-balance line, so you can see at a glance whether you're trending toward a refill or have headroom.

Admins see an extra toggle that flips both charts from credits to dollars — useful when comparing against a finance forecast — but the underlying data is the same.

Auto-reload​

Below the charts is the Auto-reload card:

  • Enabled / disabled — master switch.
  • Threshold — the balance below which a top-up fires.
  • Top-up amount — how many credits to add when the threshold trips.
  • Last triggered timestamp + the next-eligible window (rate-limited to one auto-reload per day).

A successful auto-reload posts a Billing notification to Inbox; a failed one (e.g. card declined) raises a higher-priority Subscription notification with the action link to update the payment method on Account → Settings → Payments.

What consumes credits​

Credits are debited at the moment AI work completes, not when you queue it. The main consumers:

  • Chat — every message that calls a model (every tool call inside a chat is its own debit).
  • Agent runs — each step of an agent that calls a model, plus any sub-agents it delegates to.
  • Scheduled / system-hook runs — ChangeLog summaries, monitoring triage, social-post drafts, and the rest of the platform's background work.
  • Documentation generation — re-analyzing repos, drafting help articles, refreshing API references.

Embedding, tokenization, and Firestore I/O are platform-level and don't count against your credits.

Adding credits manually​

The same Auto-reload card has an Add credits action that fires a one-time purchase against your saved payment method. The receipt lands in Account → Settings → Payments, and the new balance is reflected immediately on this page.

Reconciling against your subscription​

Your subscription plan grants a monthly credit allowance that refills on the renewal date and rolls over within reason (see your plan's terms). The summary cards distinguish between plan-granted credits and purchased credits so you can tell which bucket is depleting first; the Auto-reload setting only ever buys purchased credits — it doesn't change your plan.