Usage
Every project has a Usage page, and every team has one covering all of its projects. Use them to see how close a project is to its included usage, what it has cost so far this month, and where AI credit goes.
Choose the period
Pick a date range at the top. Current Billing Cycle covers the calendar month so far (UTC), the period that included usage and on-demand charges are counted in. Use it when a project is close to a limit or has been restricted.
Sections
The team Usage page shows the same sections, adding up every project in the team.
Read the numbers
Each chart uses its own unit: requests, tokens, gigabytes or dollars. Compare a chart only with its own allocation.
- AI model spend (Spend by Model, Requests by Model, All Tokens) is paid from AI credits. It doesn’t count toward the plan’s included usage.
- Database capacity and asset storage show size at each point in time. On Pro, the amount above the allocation is billed as a time-weighted average, not at its peak.
- Agent steps count each model call the agent makes. A long task uses many steps, so watch this chart for automations that loop or retry.
Investigate unexpected usage
- Narrow the date range to when usage rose.
- Match it with recent deployments, imports, traffic or automation runs.
- Use Logs for request-level detail, and run history for automation outcomes. Failing work that retries still uses resources.
To control what usage can cost:
- Spend management limits a Pro project’s on-demand usage.
- Auto-reload settings limit AI credit top-ups.
- Notifications explains the alerts Flexkit sends as a project nears its limits.
Last updated on