Usage summary
Adds up your team’s API usage over a time window: requests, credits,
errors and results. Pass group_by to split the totals by day,
product, endpoint, charge component, API key, client surface, client
platform or status class. Leave it out to get one total row.
Every row is scoped to your team. No parameter reads another team’s usage.
With the default bucket=1d and a window made of whole UTC days, the
summary is read from daily totals. Those know the day, product,
endpoint, API key, client surface and status class, so some shapes
are rejected with a 400 that tells you to retry with bucket=1h:
group_by=componentcombines only withdayandproduct, and filters only byproducts.- The
statusanderror_typefilters needbucket=1h.
A window that starts or ends mid-day, bucket=1h, or any grouping that
includes client_platform accepts every combination.
This endpoint is free: the response carries no X-Credits-Used
header. It shares a limit of 60 requests per minute with the other
/account/usage/* endpoints.
Authorizations
Headers
Query Parameters
Dimensions to split the totals by. Repeat the parameter or send a
comma-separated list, for example group_by=day,component. A
dimension can appear once. Omit it for a single total row.
Grouping by day returns the time column as bucket_start.
Grouping by component returns component and label, and
swaps errors and results for quantity.
client_platform is the tool or runtime that made the call, such
as claude-code, python or curl. New values can appear at any
time, so do not hard-code the list. It works with any bucket.
day, product, endpoint, component, api_key_id, client_surface, client_platform, status_class 
