Reference
Which Anthropic datasets hold data
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.
Authorization
BearerAuth In: header
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/data-availability"{
"success": true,
"data": {
"costs": true,
"sku": true,
"resource": true,
"usage_value": true,
"usage": true,
"people": true,
"cowork": true,
"list_price": true,
"anomalies": true,
"activity": {
"session": true,
"active_time": true,
"prompt": true,
"tool": true,
"tool_decision": true,
"edit_decision": true,
"mcp_connected": true,
"mcp_failed": true,
"plugin": true,
"plugin_source": true,
"skill": true,
"permission_mode": true,
"api_error": true,
"lines": true,
"git_output": true,
"request_source": true,
"request_effort": true,
"request_speed": true,
"response_time": true,
"repository": true
},
"fleet": true,
"managed_settings": true,
"organizations": true,
"teams": true
},
"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"
}Claude Enterprise at list price, against what it cost after discount GET
What each Claude product would have cost at Anthropic's list price, beside what it cost after discount, over the range. The amount after discount is the same whether Anthropic or a marketplace invoices it. Anthropic reports a list price for Claude Enterprise alone, so an organization on another plan is answered with zeros.
People who started using Claude, came back to it or kept using it GET
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.