The frontend UI is showing a fatal symbol error (misuse of the dollar sign):
-
-
In the latest MAX fast request details, the UI displays the format as
Cache Read: $13.05. -
The Issue: This “13.05” is actually the token count (13.05k Tokens). However, because of the
$sign in front of it, users will mistakenly think a single cache read just cost them $13. -
Suggestion: Update the frontend to display a clear unit, such as
13.05k Tokensor13,050 Tokens.
-
-
Missing unit descriptions for Credits in the CSV export:
-
In the exported usage spreadsheet, data like
Input Credits: 538.4442lacks any unit clarification. -
The Issue: It is incredibly easy for users to mistake 538.44 for $538 (especially for a single request). While I personally know that 1 Credit = 1 Cent (meaning the cost is actually $5.38), I highly recommend adding a clarification to the column name, such as
Input Credits (Cents), or adding a clear formula to the dashboard:100 Credits = 1 USD.
-
-
Damaged User Experience:
- As a user, the first reaction to the illusion of “spending over $500 on a single conversation” is sheer panic, followed by immediately stopping the use of the product. Clear billing units are not only a basic form of respect for the user, but they will also save your customer support team from drowning in a flood of “Am I bankrupt?” tickets.
------The articles above were translated and researched with the help of AI.
