Reading the usage page
Understand the chart, totals, and tables on the Usage page.
The Usage page shows how many requests and credits your workspace consumed over a selected date range.
Pick a date range
Use the date range controls or quick presets:
- 1D — today.
- 7D — the last 7 days.
- 30D — the last 30 days.
Click Apply after changing dates.
Top metrics
- Total Requests — number of requests in the selected range.
- Total Credits — credits consumed in the selected range. When Source is All, the card also splits them into Chat and Training credits.
Usage Over Time
The chart shows one stacked bar per day, with a colored segment for each chatbot, so you can see both the daily total and which bot contributed most. Use the chart metric menu to switch between:
- Credits - credits used per day, stacked by chatbot.
- Requests - requests per day, stacked by chatbot.
- Credits by type - available when Source is All; splits each day into Chat and Training credits.
Spikes usually mean a popular widget page, a large training run, or API automation.
By Chatbot table
Each row shows the chatbot, its Share of credits (a bar and the percentage of the range's credits), its total requests, and its total credits. Rows are sorted by credits, largest first.
If a bot name is missing, Pegasus shows "Unknown Bot" while still keeping the usage record.
Source filter
The Source filter narrows usage to where requests came from.
Source values
| Source | Includes |
|---|---|
| Direct | Logged-in workspace chat. |
| Widget | Visitor conversations from the embed widget. |
| API | Personal Access Token/API usage. |
| All | Every source, plus training credits where applicable. |
Training credits and filtering
When you filter by a specific source, Pegasus does not include training credits. Switch to All to see every source and the chat/training breakdown.
When to use each filter
- Use Direct when investigating your own workspace chat.
- Use Widget when a public website has sudden traffic.
- Use API when checking automation or external clients.
- Use All for the monthly total picture.
Credits breakdown
The Credits card can show a breakdown by type when the Source filter is All.
Chat credits
Chat credits include:
- Workspace conversations.
- Widget visitor messages.
- API/PAT messages.
- Extra context and response tokens.
Training credits
Training credits include document processing work such as reading and indexing documents. They are linked to bot knowledge updates, not to a visitor or chat session.
Why numbers differ from request count
One request can consume multiple credits. A long response, a large context window, or Max Mode can increase token usage.
Use the breakdown for decisions
- If Chat dominates, inspect popular bots and source filters.
- If Training dominates, review document size and retraining frequency.
- If Widget dominates, check Allowed websites and public-site traffic.
Team usage views
Team owners see additional usage tabs when they are in a team workspace.
My Usage
Shows usage attributed to you in the current workspace context.
Team Members
Shows usage grouped by member, listed by name (or email when no name is set), with share of credits, requests, and credits. Use this to understand who is using the team's credits.
Team Bots
Shows usage grouped by bot, with the bot's owner under its name, its Consumers (the members who used it, by name), share of credits, requests, and credits. Use this when a bot is using unexpectedly many credits.
Who can see team views
Team owner role is required for team-wide member/bot usage views. Regular members see their own usage context.
The selected date range and Source filter apply to all tabs.