Skip to main content

Show Total LLM Usage Cost to Usage page

Feature Request

Add a Total cost value to the Usage page so users can see the overall amount spent without manually summing the values from the Total column.

The exact placement is flexible. The value can be displayed either:

  • as a separate Total row in the usage table; or

  • as part of the Monthly usage summary.

The main requirement is to provide users with the automatically calculated total amount for the displayed usage data.

Current Behavior

The Usage page displays costs per individual row, but users must manually sum the Total column to calculate the overall cost.

Expected Behavior

The system automatically calculates and displays the total cost for the relevant usage period/data currently shown on the page.

Acceptance Criteria

  1. The Usage page displays the automatically calculated total cost.

  2. The value matches the sum of the existing Total column.

  3. The total updates according to the currently displayed usage period/data.

Status: Completed1 comment

Log in to comment and vote

Comments1

  • John

    Team•

    Oct 6

    Product update from PR #6438.

    Enhancement: Total LLM Cost Now Shown on the Usage Page

    The Usage page now shows the total LLM cost for your selected report next to the LLM Usage heading, so you no longer have to add up the Total column yourself.

    Benefits

    • See total spend at a glance: The overall cost for the data on screen appears in the LLM Usage heading.
    • No manual calculations: You don't need to add up rows or copy figures into a spreadsheet to find out what you've spent.
    • Matches the table: The total is built from the same rows and dates as the usage table. It includes usage from removed apps and usage that isn't linked to a known prompt or model.
    • Stays current as you filter: The total updates when you change the date range, selected prompts, active/archived view, or grouping (by prompt, model, or Ender).
    • Always shown in USD: The total stays in USD even when the table shows token counts instead of cost.
    • Available in all supported languages: The new label is translated into English, Ukrainian, German, Polish, Russian, Czech, and Spanish.

    Who Benefits

    • Admins: Can track LLM spending for any period without extra work.
    • Finance and Operations Stakeholders: Get a reliable total for budgeting, forecasting, and checking costs.
    • QA Managers and Team Leads: Can quickly see how much specific prompts, models, or Enders cost by filtering the report and reading the total.

    Before & After

    BeforeAfter
    Each row in the Usage table showed its own cost, and you had to add up the Total column yourselfThe total cost is calculated for you and shown next to the LLM Usage heading
    Switching to a token metric hid cost figuresThe total cost in USD stays visible when you view token counts
    Costs from unidentified prompts could be left out of the viewUnidentified prompt usage is grouped into a single "unknown prompt" row and counted in the total

    Time & Effort Saved

    • Saves the few minutes it takes to add up costs by hand each time you review usage, and avoids adding-up mistakes. This matters most for long date ranges or reports with many prompts or models.

    Use Cases

    • Monthly cost review: Pick last month in the date picker and see the total LLM spend right away for reporting or invoice checks.
    • Prompt cost analysis: Select a few prompts to see how much they cost together over a period.
    • Model comparison: Group by model and use the total to track overall spend while comparing the cost of each model.
    • Token monitoring with cost context: Look at token usage in the table and keep the matching USD total in view.

    How to Use

    Go to Settings → Usage. In the LLM Usage section, the total cost appears in the heading, next to "LLM Usage". Hover over the value to see the "Total cost" label. A dash (—) shows while data is loading. Change any filter (dates, prompts, active/archived, or grouping) and the total updates to match the table.

    PR: #6438