{"version":"2.1.277","anchor":"new-gate-function-jce-for-first-party-base-url-eligibility","canonical_anchor":"new-gate-function-jce-for-first-party-base-url-eligibility","heading":"New gate function jce for first-party base-URL eligibility","tier":"internal","area":"Feature Gates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-gate-function-jce-for-first-party-base-url-eligibility","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New gate function jce for first-party base-URL eligibility\n\nA new internal check gates a capability to first-party accounts using the default API endpoint\n\n**Unclear.** What capability this eligibility check controls is not stated.\n\n**What**\n\nA new helper function checks whether the account's auth type is `firstParty` and several other conditions, including that `ANTHROPIC_BASE_URL` (which overrides the API endpoint, for example to route through a proxy) is not set, plus region and configuration checks, before allowing some capability to proceed.\n\n**Why**\n\nThe finding doesn't say what capability this gates, but requiring first-party auth and the default API endpoint fits the existing pattern where certain features are disabled when requests are routed through a non-Anthropic endpoint.\n\n- Area: Feature Gates\n- Names: `ANTHROPIC_BASE_URL`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}