# API changes: November 8, 2026

[← Changelog](/docs/changelog) · [November 2026](/docs/changelog/2026-11)

### FIX-1108-1: Model lists in GET /v1/me for a Cowork key match the subscription models

**Before**

For a key carrying the `vibe:cowork` scope, the `ai.usableModels` and `ai.structuredOutputs.models` fields of the [GET /v1/me](/docs/keys-auth/me) response also named models outside the Cowork subscription. Calling such a model with this key answered `402 cowork_model_not_allowed`. The same extra models came in the `structuredOutputsModels` field of the `400 model_does_not_support_structured_outputs` refusal from [POST /v1/chat/completions](/docs/ai/chat/completions).

**After**

The `GET /v1/me` response remains HTTP 200. For a Cowork key, both fields and the `structuredOutputsModels` field name only the models this key can call under the subscription, the same set as [GET /v1/models](/docs/ai/models/list) and the `allowedModelIds` field of the `402 cowork_model_not_allowed` refusal. For keys without `vibe:cowork`, the lists are unchanged.

**Impact on integrators**

No changes are needed. An agent that picks a model from `GET /v1/me` no longer gets `402 cowork_model_not_allowed` for a model from these lists.

### FIX-1108-2: a call to a disabled model now counts once in AI usage statistics

**Before**

[GET /v1/ai/usage](/docs/ai/consumption/usage) counted a call redirected from a disabled model to its replacement model twice: `totals.calls` and `byScope.<scope>.calls` included both the `DISABLED_REDIRECT` record for the requested model and the record of the call itself.

**After**

The `DISABLED_REDIRECT` record no longer counts as a call, so a redirected call counts once. `recentCalls` still shows it next to the call record. Tokens and cost do not change: they are zero for this record.

**Impact on integrators**

No action needed. If you reconciled `totals.calls` with your own request counter, the mismatch on redirected calls goes away.

### NEW-1108-3: Polls in chat messages and feed posts

Vibe supports Bitrix24 polls through `/v1/polls` with the `vote` scope: discovery by posts or messages, questions, results, voters, voting, vote recall, stopping and resuming. `POST /v1/chats/:dialogId/polls` creates a chat poll with a UUID `idempotencyKey`; duplicate protection depends on the installed Bitrix24 version. The post list includes `hasPoll` to identify attached polls. Creating feed polls is unavailable. `resultsVisible` indicates result visibility: when `false`, counters and percentages are `null` and voters are hidden; voter lookup returns `403 RESULTS_HIDDEN`. All operations are denied to Cowork keys with read-only access to the Bitrix24 account.