Feature Description
This is a request based on the commandcode.ai user interface, specifically the Usage section.
When viewing the Usage section, the data is lacking a bit of context that could help users in managing their API utilization. Currently, it shows the Model, Mode, and Status, but this isn't helpful in determining the source of the activity when a specific model is used across multiple API key.
Fix:
Add an "API Key" column that shows which API key was associated with each activity in the table, and allow for filtering by key name, so a user can identify instances when a service associated with a particular key ramps usage unexpectedly.
Use Case
No response
Additional Context
No response
How important is this to you?
None
Feature Description
This is a request based on the commandcode.ai user interface, specifically the Usage section.
When viewing the Usage section, the data is lacking a bit of context that could help users in managing their API utilization. Currently, it shows the Model, Mode, and Status, but this isn't helpful in determining the source of the activity when a specific model is used across multiple API key.
Fix:
Add an "API Key" column that shows which API key was associated with each activity in the table, and allow for filtering by key name, so a user can identify instances when a service associated with a particular key ramps usage unexpectedly.
Use Case
No response
Additional Context
No response
How important is this to you?
None