{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiezkhzeyyzd7x6onkcqjfprae5qlcu4twef5jrj6jlcswdofpy2ta",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3meqhzcrp5nd2"
  },
  "path": "/t/api-key-permissions-not-working-correctly/1374137#post_3",
  "publishedAt": "2026-02-13T12:09:02.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "https://platform.openai.com/settings/organization/api-keys"
  ],
  "textContent": "wow…yes that worked. I would never have guessed the problem was a UI design issue at https://platform.openai.com/settings/organization/api-keys\n\nIn other words for anyone who encounters this issue and finds this post, if you do this:\n\nset all model capabilities to ‘request’ by hitting here:\n\n\n\nand then turn off the ones you don’t want (e.g. like this I’ve turned off moderations:\n\n\n\nthen it works.\n\nGiven the initial error response mentioned an option which isn’t under the heading ‘model capabilities’, I suspect this works because initially setting model capabilitites to ‘request’ sets that hidden item to ‘request’, so that when you turn off the ones you don’t want and model capabilities goes back to ‘mixed’, you have changed the problematic item even though the UI looks exactly the same after the change as it did in my initial screenshot of the broken config.\n\nSpecifically, I think _model.request_ is the hidden item given that’s what the error message said this key didn’t have permissions for until I changed ‘model capabilities’ to request, then turned off the ones I don’t want.\n\nFor the avoidance of doubt, the UI looks exactly the same now as it did when the config was broken. It’s just the hidden item that has changed.\n\nWow.",
  "title": "API key permissions not working correctly"
}