{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicellgrktmi3iaereuon6jeripv6j3c7nhy36ymayvadxxontxupa",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mphkrulug3x2"
  },
  "path": "/t/feature-request-include-api-key-name-or-group-by-api-key-name-in-the-usage-costs-api-responses/1385288#post_1",
  "publishedAt": "2026-06-29T22:01:31.000Z",
  "site": "https://community.openai.com",
  "textContent": "Our team manages a large number of API keys, and we use the Usage and Costs endpoints (`/v1/organization/usage/*`, `/v1/organization/costs` to break down spend by key. Today these endpoints group only by `api_key_id`, which makes it hard to tell at a glance which key is which. With many keys, our teams cannot tell at a glance which key maps to which product surface, so reconciling spend means manually and frequently cross-referencing IDs and building mapping logic against our own records.\n\nWe’d like these endpoints-- most importantly the costs endpoint, to include `api_key_name` as a new group_by option to avoid extra lookups to map IDs back to keys.",
  "title": "Feature Request: include API key name (or group_by=api_key_name) in the Usage & Costs API responses"
}