Reference
People who started using Claude, came back to it or kept using it
Everyone who reported usage in the range is one of three: new when they were first seen inside it, continuing when they also reported usage in the range of the same length just before, and returning otherwise. At most five are named: up to three of the new and up to two of the returning, each kind taking the places the other leaves empty. 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/usage/adoption?start=string&end=string"{
"success": true,
"data": {
"active": 0,
"continuing": 0,
"new": 0,
"returning": 0,
"items": [
{
"person": "string",
"status": "new",
"first_seen": "2019-08-24",
"away_days": 0
}
]
},
"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"
}Which Anthropic datasets hold data GET
True for each dataset that has something to show, so the board hides the cards that do not. costs is billed spend, sku and resource are billed spend with a token type or a named key or person, usage_value is Claude Code and Cowork usage rolled into the cost tables, and usage is that usage as it was reported, which is what the usage routes read. people and cowork say more about the reported usage: whether two or more people reported any, and whether Cowork did. list_price is Claude Enterprise spend that carries a list price. activity has one flag per kind of activity Claude Code reported, and fleet, managed_settings, organizations and teams say what its installs reported about themselves. The activity flags and those four look at no range: each is true while anything of it is stored, whatever its day.
Claude Code and Cowork usage by person, by model or by product GET
Usage is what Claude Code and Cowork reported about themselves, valued at API list price. It is not what the organization is billed, and it includes the current day. Rows are ordered by usage value, largest first. share is a row's part of the whole range, whatever search narrows the rows to. Grouped by person the answer names people, so it is sent with Cache-Control: no-store.