Problem
The current API usage graph shows total usage across an account, but it does not allow usage to be broken down by individual API keys.
For users running multiple services, environments, or projects under one account, this makes it difficult to:
Identify which service is generating usage
Debug unexpected spikes
Allocate costs internally
Requested Feature
Add the ability to view API usage metrics per API key.
Why This Matters
Many users:
Use multiple API keys for different apps, cron jobs, or customers
Need clearer observability without creating separate accounts
Want better cost control and accountability
Per-key usage visibility would significantly improve monitoring, debugging, and billing clarity.