Drıftstack docs
Docs

Reading the Usage page (current period, daily series, limits)

You might be here because: “what does the Usage page show” · “Session minutes” · “Live usage loaded. No activity in the current period yet” · “Couldn’t load live usage” · “is usage billed” · “usage says zero but I ran sessions” · “Limits for your account” · “set by support · ends” · “why is today missing from the chart” · “Sign in to see live usage.”

Short answer

Usage shows activity counts for the current calendar month (UTC) — session minutes, page loads, interactions and captures — a daily chart, and the request limits for your account; none of the counts is billed. A paid plan has no monthly hours total; it limits how many sessions run at once, and each session still has a maximum length. The free trial also limits total session time. The counts are there to spot problems early, like a sudden jump in page loads from a runaway script.

Check first

  • Signed in? Otherwise the page says “Sign in to see live usage.”.
  • The header reads “[start] → [end] · [plan] tier”: the period is the current calendar month, in UTC.
  • Acting as a team owner? Then the page shows the owner’s usage, and the owner’s plan is what the limits come from.

Likely causes and fixes

  1. What the tiles mean. Session minutes are the wall-clock minutes sessions were active, summed over the month; page loads, interactions and captures are counts of each action; no paid plan caps any of them. No paid plan meters minutes: there is no monthly total. Each session still has its own end; a session that no AI agent drives runs for up to 4 hours. The free trial has a total and a shorter session limit: a trial session is closed after 20 minutes, and the trial includes 2 hours of session time in total, counted from the day it starts rather than per calendar month — so on a trial that began last month, this month’s session minutes are not the whole of what it has used. When the 2 hours are used, a new session is refused (HTTP 429 tier-limit, code: "trial_session_time_used").

  2. “Live usage loaded. No activity in the current period yet — counts will fill in as you run sessions.” Real data arrived and every count is zero. If the tiles stay at zero although sessions have run, tell a person (below).

  3. Daily activity for 7, 30 or 90 days. The chart ends on yesterday, the last complete UTC day; today’s partial day is left out on purpose, and days with nothing show as zero.

  4. Captures by kind. Screenshots and page snapshots are counted separately.

  5. “Limits for your account.” One row per request limit: Limit, Maximum, Recovers per second, and Set by — “plan default”, “sized to your session limit” on the agent_sessions:live row (240 a minute for each session your account may run at once) and on the agent_sessions:steps row (lists of steps: 30 a minute for each session your account may run at once, never less than your plan’s agent_sessions:message figures) and on the agent_sessions:tabs row (tab calls: “sized to your session limit, the same figures as agent_sessions:steps”), or “set by support · ends [date]” for a limit set for your account for a time (usually an increase; a reduction shows the same way). The concurrent-session and profile caps are not on this page; they are enforced when you create.

  6. “Couldn’t load live usage (…)”, “Couldn’t load daily activity. Try again.”, “Couldn’t load your limits. Reload to try again.” Three separate fetches; one failing leaves the others alone. Fix: reload.

  7. The same numbers from code. The usage endpoints return the period summary and the daily series for 1 to 90 days.

If it still fails

Press Talk to a person in this chat (or open Help) and include: account email, the period the header shows, and what the tiles say against what you ran (session ids and times). Nothing here requires an account action.