{"version":"2.1.225","anchor":"unified-rate-limit-tracking-now-also-applies-on-the-gateway-","canonical_anchor":"unified-rate-limit-tracking-now-also-applies-on-the-gateway-","heading":"Unified rate-limit tracking now also applies on the gateway auth source","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/unified-rate-limit-tracking-now-also-applies-on-the-gateway-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Unified rate-limit tracking now also applies on the gateway auth source\n\nGateway-authenticated sessions now get the same rate-limit tracking and 429 handling as subscription ones.\n\n**What**\n\nSessions authenticating through the gateway get the same unified rate-limit handling that subscription sessions already had.\n\n**Details**\n\n- the guarding predicate changed from \"caller says so, or the subscription check passes\" to additionally accepting a `gateway` auth source\n- covers unified rate-limit header parsing, 429 handling and the background usage probe\n\n**Evidence**\n\n`anthropic-ratelimit-unified-overage-status`\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}