{"version":"2.1.239","anchor":"requests-can-now-be-marked-as-running-against-a-slow-usage-b","canonical_anchor":"requests-can-now-be-marked-as-running-against-a-slow-usage-b","heading":"Requests can now be marked as running against a slow usage budget","tier":"internal","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/requests-can-now-be-marked-as-running-against-a-slow-usage-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Requests can now be marked as running against a slow usage budget\n\nRequests can be tagged as running against a slower usage budget, with a matching reset header recognised.\n\n**What**\n\nRequests to the messages endpoint can carry a new header, `anthropic-usage-limit: slow`, set when an internal usage-limit phase reports as active. The build also recognises a matching response header naming when a slow budget resets. The previous build had neither, only an \"extended\" value.\n\n**Details**\n\n- The header is added by the shared request layer when the URL path ends in `\/v1\/messages` and the phase check passes.\n- Nothing in the build forces the phase active, so whether you ever see this is decided elsewhere.\n\n**Evidence**\n\n`anthropic-ratelimit-unified-slow-budget-reset`\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}