{"version":"2.1.293","anchor":"fable-and-model-specific-billing-check-reworked","canonical_anchor":"fable-and-model-specific-billing-check-reworked","heading":"Model choices now depend on your billing state","tier":"notice","area":"Models","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/fable-and-model-specific-billing-check-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Model choices now depend on your billing state\n\nAutomatic moves to a larger-context model and Fable-style model handling now check how the account is billed and whether extra usage was agreed\n\n**Unclear.** It is not clear what this model-specific behaviour does for a user who gets it.\n\n**What**\n\nA new helper sorts each account into a billing state: `pay_per_request`, `admin_billed`, `included_in_plan`, `needs_consent`, `needs_credits`, `out_of_credits` or `consented`. Two model checks now use it.\n\n- The automatic switch to a model with a larger context window, used when the conversation is about to be too long, now also calls `Mar`. `Mar` allows the switch when the model is not recognised, the account is pay-per-request or admin-billed, or you have agreed to extra usage and have credits. The old `Bve(w)` condition was removed.\n\n- The path for Fable and similar models now applies when the model family's billing mode is neither `pay_per_request` nor `included_in_plan`.\n\n**Why**\n\nAccounts that have not agreed to extra usage, or have no credits, will likely no longer be moved to the bigger-context model automatically. That avoids charges you did not agree to. Which accounts see the Fable-specific behaviour now depends on how the account is billed.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}