{"version":"2.1.277","anchor":"fablevoice-model-availability-logic-reworked-around-gateway","canonical_anchor":"fablevoice-model-availability-logic-reworked-around-gateway","heading":"Fable\/voice model availability logic reworked around gateway vs first-party routing","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/fablevoice-model-availability-logic-reworked-around-gateway","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Fable\/voice model availability logic reworked around gateway vs first-party routing\n\nAvailability logic for the fable voice model was reworked around whether requests go through a gateway or directly to Anthropic\n\n**Unclear.** Whether this changes fable's actual availability for any specific group of users, versus just restructuring how the check is computed, isn't clear from the evidence.\n\n**What**\n\nThe logic that decides whether the \"fable\" voice model is available was reworked. It now checks a gate together with another condition earlier in the process, and for accounts not using multi-account routing, it branches on whether requests are routed \"firstParty\" (directly to Anthropic, always available) or through a \"gateway\" (routed through an intermediary, where availability is checked separately). This replaces the previous logic, which gated first-party availability differently and had separate fallback handling.\n\n**Why**\n\nThis changes how fable's availability is determined depending on how a user's requests are routed, though the finding doesn't specify what practical difference users will see.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}