Usage lookups can ask the server to skip computing spend.
What's wrong with this entry?
The usage fetch gained an at-wall mode that asks the server to skip computing spend, reported separately in telemetry.
- Requests
/api/oauth/usage?at_wall=1&skip_spend=1and reports asapi_usage_fetch_at_wallrather thanapi_usage_fetch. - Chosen by the caller; the plain endpoint and metric remain for everything else.
/api/oauth/usage?at_wall=1&skip_spend=1
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit