Credits History
The Credits History menu lets you view credit transaction history in the organization, including credit charges, usage, refunds, expirations, adjustments, and more.
Filtering Credits History
You can filter credit transaction history by the following conditions.
- User email: View credit transaction history for a specific user.
- Transaction type: Select from all transactions, charge, usage, refund, expiration, adjustment, overuse, or deletion.
- Default view: In Default view after the transaction type filter, view history by deduction reason. Select general chat, agent chat, automation, or a specific app to show only that usage history. Apps are listed from the apps available to the organization.
- Date range: View records for the last 7 days, last 30 days, last 3 months, or a custom date range.
Viewing Credits History
The history table shows the main information for each credit transaction.
- Date: The date and time when the transaction occurred
- User: The user associated with the transaction
- Event type: The transaction type, such as charge, usage, or refund
- Credits: Credits increased or deducted
- Balance after transaction: The credit balance after the transaction
- Credit type: The credit source, such as plan, additional, event, Free PoC, PoC, Production, or Partner
- Deduction reason: The reason credits were used or changed
Expand each row to view detailed information for that credit transaction.
Expanded Row Details
Source Information
- Source type: The usage type where the credit occurred, such as personal agent, organization agent, automation, or general chat
- Source name: The name of the target where the credit occurred
Details Table
- Time: The time when the work occurred
- Usage history: The type of work that used credits
- Lingo: Shows separate entries for actual features, such as voice conversations, meeting summaries, meetings, meeting real-time translation, speech recognition, and meeting bots.
- NotePie: When usage from multiple models occurs, shows separate detail rows for each model so you can review the model, usage, and credits.
- Other apps: When detailed billing information is available, shows separate rows by task or model.
- Model: The model used for the work
- In addition to models selected by users for chat, models used for internal tasks such as title generation, message search and indexing, conversation history summarization, and agent icon generation may also appear.
- Usage: Tokens or time used for the work
- Token-based tasks: Internal processing in general chat—including chat responses, title generation, message search and indexing, tool calls, and conversation history summarization—as well as Lingo meeting summaries are shown as
input / cache / outputtokens. - Lingo meetings and real-time meeting translation: The actual meeting duration is shown in hours, minutes, and seconds.
- Lingo speech recognition (STT): The processed audio duration is shown in hours, minutes, and seconds.
- Token-based tasks: Internal processing in general chat—including chat responses, title generation, message search and indexing, tool calls, and conversation history summarization—as well as Lingo meeting summaries are shown as
- Credits: Credits used by the work
Downloading Credits History
Administrators can download the queried credit usage history as a CSV file.
- On the Credits History page, set the user email, transaction type, default view (deduction reason), and date range filters.
- Click CSV Download.
- Enter the ZIP password.
- When the download starts, save the compressed file and open it with the password you entered.
The CSV download reflects the currently selected user email, transaction type, default view (deduction reason), and date range conditions. You can specify a download period of up to 31 days.
Responses Stopped by the Recursion Limit
If tool calls or step execution run too long and reach the recursion limit, response generation may stop. In this case, the credits used for that turn are restored, and the chat screen displays a notice that the credits will be restored.
Administrators can filter Credits History by the Refund transaction type to check restoration records. If credits for the same turn have already been restored, they are not restored again.