{"version":"2.1.228","anchor":"gateway-protocol-document-now-matches-the-deployment","canonical_anchor":"gateway-protocol-document-now-matches-the-deployment","heading":"Gateway protocol document now matches the deployment","tier":"notice","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-protocol-document-now-matches-the-deployment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway protocol document now matches the deployment\n\nThe gateway's protocol document is now generated to match how your deployment is actually configured.\n\n**What**\n\nThe gateway used to serve one fixed protocol document at `\/protocol`. It is now generated per deployment: the wording branches on whether an identity provider is configured, and a customer-routed-inference section covering token verification, forwarding rules and the `capability_rejected` error class is appended when CRI is on. Without an identity provider, the document notes that sign-in routes return 404.\n\n**Evidence**\n\n`text\/markdown; charset=utf-8`, `# Claude Code gateway protocol`\n\n- Area: Gateway\n- Names: `\/protocol`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}