[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-11-14":3,"docs-tabs-changelog\u002F2026-11-14":6},{"content":4,"lastmod":5},"# API changes: November 14, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [November 2026](\u002Fdocs\u002Fchangelog\u002F2026-11)\n\n### BC-1114-1: Partner Connect application keys grant access to AI models only\n\n> Old format supported until: not provided\n\n**Before**\n\nA partner application key issued through Partner Connect with the `vibe:ai` scope could both call models and manage external model keys through `\u002Fv1\u002Fai\u002Fproviders`, `\u002Fv1\u002Fai\u002Fcredentials` and `\u002Fv1\u002Fai\u002Fcredentials\u002F*`.\n\n**After**\n\nThese routes return `403 INSUFFICIENT_SCOPE` for such a key. This refusal has no `error.cause` or other scope refusal fields. Model calls with the same key continue to work as before.\n\n**What integrators should do**\n\nRemove calls to external model key management routes from Partner Connect applications. Changing scopes or asking the user to consent again does not lift this restriction. See [Partner Connect](\u002Fdocs\u002Fpartner-connect#using-the-api-key).\n",null,{},1794739487577]