{"version":"2.1.225","anchor":"spend-cap-responses-carry-unified-rate-limit-headers","canonical_anchor":"spend-cap-responses-carry-unified-rate-limit-headers","heading":"Spend-cap responses carry unified rate-limit headers","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/spend-cap-responses-carry-unified-rate-limit-headers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Spend-cap responses carry unified rate-limit headers\n\nSpend-limit blocks now tell you which cap period you hit and when it resets.\n\n**What**\n\nThe spend precheck now picks the most binding cap period that has spend against it and returns `anthropic-ratelimit-unified-*` headers describing that period.\n\n**Details**\n\n- headers cover status, reset, overage utilization, surpassed threshold, retry-after and the period itself\n- the surpassed-threshold header trips at utilization 0.95 and 0.75\n- blocked responses name the offending period and its reset time rather than a generic message\n- failures reading the spend store now surface a `fetch_error` disabled reason instead of a bare error string\n\n**Evidence**\n\n`anthropic-ratelimit-unified-overage-surpassed-threshold`\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}