Card #464 · OpenAI Platform & APIs
Lack of API key names in Usage and Costs API responses
The Usage and Costs endpoints only group data by API key ID, making it difficult to identify which key corresponds to which product surface. This forces teams to manually cross-reference IDs and build custom mapping logic to reconcile spending.
Pain score
0.24/ 1.00 · weighted product of four components
Reach1.00distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.87upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 2 verified quotes
Today these endpoints group only by api_key_id , which makes it hard to tell at a glance which key is which.
reconciling spend means manually and frequently cross-referencing IDs and building mapping logic against our own records.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro