Unclear How severity and is_active are used or surfaced to the user isn't stated in the finding.
What
- The rate-limits API response schema gained two new fields on each limit entry:
severityandis_active, alongside the existing group, percent, resets_at, and scope fields. - A related status-meter schema, used for usage/limit meters more broadly, changed
severityandis_activefrom optional and nullable fields to required ones, with an updated description clarifying that every row's severity and active status comes from the server, not something a client computes itself.
Why
This ensures any client displaying usage or rate-limit information always gets a definitive severity level and active/inactive status straight from the server, instead of having to infer it or handle missing values.
Names in the bundleseverityis_active
Documented inapi/api/compliance/organizations
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up severity, on Channels reference.
| `meta` | `Record<string, string>` | Optional. Each entry becomes an attribute on the `<channel>` tag for routing context like chat ID, sender name, or alert severity. Keys must be identifiers: letters, digits, and underscores only. Keys …channels-reference see the edit
Confirmed since
Anthropic's documentation has since written up is_active, on Compliance API.
- `is_active: optional boolean or null`api/compliance see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
How severity and is_active are used or surfaced to the user isn't stated in the finding.
Anthropic's documentation agrees
Anthropic's documentation has since written up is_active, on Compliance API.