Reference
The people behind the largest activity figures
Activity is what Claude Code and Cowork reported about themselves, kept as daily totals: names, counts and durations, never the text of a prompt, a response or a command. Each list names at most three people, the largest figure first, and nobody whose figure is zero. behind_on_version and without_managed_settings count everyone they apply to among the people who reported usage in the range, and name three. The answer names people, so it is sent with Cache-Control: no-store.
Authorization
BearerAuth In: header
Query Parameters
First day, ISO 8601 (YYYY-MM-DD or a datetime)
Last day, ISO 8601 (YYYY-MM-DD or a datetime), included
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/providers/anthropic/activity/people?start=string&end=string"{
"success": true,
"data": {
"most_active": [
{
"person": "string",
"active_seconds": 0
}
],
"most_errors": [
{
"person": "string",
"api_errors": 0,
"rate_limits": 0
}
],
"most_lines": [
{
"person": "string",
"lines_added": 0,
"lines_removed": 0
}
],
"most_commits": [
{
"person": "string",
"commits": 0,
"pull_requests": 0
}
],
"behind_on_version": {
"people": 0,
"items": [
{
"person": "string",
"version": "string"
}
]
},
"without_managed_settings": {
"people": 0,
"items": [
{
"person": "string"
}
]
}
},
"timestamp": "string"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}{
"success": false,
"error": {
"code": "string",
"message": "string",
"details": null
},
"timestamp": "2019-08-24T14:15:22Z"
}The Claude Code installs of the people who used Claude GET
The people counted are the ones who reported usage in the range. A profile is kept per person, not per install: someone with two installs, such as a terminal and an editor extension on different versions, is shown as the one that reported last. Versions, terminals, operating systems, managed settings, Claude organizations and team tags, each as a count of people. Someone whose install did not report a value is left out of that list. Names nobody.
What Claude Code was used for, by kind of activity GET
Activity is what Claude Code and Cowork reported about themselves, kept as daily totals: names, counts and durations, never the text of a prompt, a response or a command. sections has one entry per kind of activity over the range, with its largest rows. response_times estimates, per model, how long a request took and how long its first token took: the times are kept in buckets, so each figure can be off by the width of one. people says how many people each kind of activity reached, and names nobody.