Group of 2 Under the hood
Usage and rate-limit data from the server now always states each entry's severity and whether it is currently active
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
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.