{"version":"2.1.225","anchor":"gateway-spend-precheck-returns-headers-for-allowed-requests-","canonical_anchor":"gateway-spend-precheck-returns-headers-for-allowed-requests-","heading":"Gateway spend precheck returns headers for allowed requests too","tier":"notice","area":"Admin Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/gateway-spend-precheck-returns-headers-for-allowed-requests-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Gateway spend precheck returns headers for allowed requests too\n\nSuccessful gateway calls now return rate-limit headers, so you can see overage state before being blocked.\n\n**What**\n\nThe admin gateway spend precheck now returns `{ blocked, headers }`, so rate-limit headers reach the client on successful calls and not just on a blocking 429.\n\n**Details**\n\n- Previously only the blocking 429 response carried the precheck headers.\n- When the request is allowed and the upstream response is ok, the precheck headers are copied onto that response.\n- This is how clients see overage state, for example `anthropic-ratelimit-unified-overage-disabled-reason`, on a call that went through.\n\n**Evidence**\n\n`anthropic-ratelimit-unified-overage-disabled-reason`\n\n- Area: Admin Gateway\n- Names: `anthropic-ratelimit-unified-overage-disabled-reason`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}