Get usage breakdown by request label

Returns per-label token and cost aggregates. Requests carrying several labels count once per label, so rows overlap and do not sum to the period totals. Unlabelled requests are omitted.

GET {base_url}/admin/usage/labels

Error

A valid request URL is required to generate request examples

200

[
  {
    "input_cost": 123,
    "input_tokens": 123,
    "label": "<string>",
    "output_cost": 123,
    "output_tokens": 123,
    "requests": 123,
    "total_cost": 123,
    "total_tokens": 123
  }
]

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

days · integer

Number of days (default 30)

start_date · string

Start date (YYYY-MM-DD)

end_date · string

End date (YYYY-MM-DD)

model · string

Filter by exact model name

provider · string

Filter by provider name or provider type

label · string

Filter by request label (exact match)

user_path · string

Filter by tracked user path subtree

cache_mode · string

Cache mode filter: uncached, cached, all (default uncached)

Response

200

application/json

OK

input_cost · number | null

input_tokens · integer

label · string

output_cost · number | null

output_tokens · integer

requests · integer

total_cost · number | null

total_tokens · integer