Get usage over time
What the workspace's answers cost over a range, from the ledger of settled answers: answers and credits per day, week or month, and broken down by query mode, assistant, who asked (a person or an API key) and API key, plus the words stored and the pages extracted this month against the plan's allowances. With no parameters it returns the last 30 days. Granularity defaults to the range length: day up to 31 days, week up to 180, month beyond.
GET/v1/usage
Requires usage:read.
Usage comes from the ledger of settled answers, so it counts what was charged, not what was reserved. Besides the totals and one point per bucket, it breaks the usage down by query mode, by assistant, by who asked (a person or an API key) and by API key, and reports the words stored against your plan’s allowance.
Without parameters, the range is the last 30 days. When you omit granularity, it follows the length of the range: day up to 31 days, week up to 180, month beyond. from and to accept a date such as 2026-07-01 or a full ISO 8601 timestamp, and a date-only to means the end of that day.
Answers given through a widget are part of these figures.
Authorizations
Authorizationbearerin headerrequiredQuery parameters
fromstringtostringgranularityenum<string>one of: day, week, monthResponse
Retrieve credit usage over time
dataobjectrequiredrequest_idstringrequiredPossible codes: invalid_request, unknown_field, invalid_parameter, invalid_cursor
errorobjectrequiredrequest_idstringrequiredPossible codes: authentication_required, invalid_api_key, api_key_expired, api_key_revoked, invalid_access_key
errorobjectrequiredrequest_idstringrequiredPossible codes: insufficient_scope, feature_not_available, admin_required, permission_denied
errorobjectrequiredrequest_idstringrequiredPossible codes: rate_limited
errorobjectrequiredrequest_idstringrequiredPossible codes: internal_error
errorobjectrequiredrequest_idstringrequired