Pull organization usage and cost reports from the Anthropic Admin API and manage workspaces and API keys programmatically

Documented steps

1. Authenticate with an Admin API key (prefix sk-ant-admin01-) in the x-api-key header plus anthropic-version: 2023-06-01. Standard sk-ant-api03- keys are rejected by /v1/organizations/* endpoints.
2. Usage: GET https://api.anthropic.com/v1/organizations/usage_report/messages with required starting_at, ending_at (ISO 8601) and bucket_width of 1m, 1h, or 1d.
3. Slice with group_by[] (model, api_key_id, workspace_id, service_tier, context_window, inference_geo) and filter with models[], service_tiers[], context_window[], api_key_ids[], workspace_ids[], inference_geos[].
4. Respect bucket ceilings: 1m defaults to 60 buckets and maxes at 1440; 1h defaults to 24 and maxes at 168; 1d defaults to 7 and maxes at 31. Split long ranges into multiple requests.
5. Cost: GET https://api.anthropic.com/v1/organizations/cost_report with starting_at / ending_at and optional group_by[] of workspace_id and/or description. Amounts come back as decimal strings in USD.
6. Paginate both endpoints with limit and page: when has_more is true, pass the returned next_page value as the page parameter on the following request.
7. Workspaces: POST /v1/organizations/workspaces to create, GET /v1/organizations/workspaces and /{workspace_id} to read, PATCH /{workspace_id} to update, POST /{workspace_id}/archive to archive.
8. Workspace members: POST and GET /v1/organizations/workspaces/{workspace_id}/members, POST /{workspace_id}/members/{user_id} to change role, DELETE the same path to remove.
9. API keys: GET /v1/organizations/api_keys (filter by status and workspace_id) and POST /v1/organizations/api_keys/{api_key_id} to rename or change status. There is no key-creation endpoint — keys are created in the Console.
10. Users and invites: GET /v1/organizations/me, GET/POST/PATCH/DELETE on /v1/organizations/users and /users/{user_id}, and POST/GET/DELETE on /v1/organizations/invites.
11. Poll no more than about once per minute for sustained integrations, and expect roughly a 5-minute lag before a completed request appears in the reports.
12. Official docs: https://platform.claude.com/docs/en/manage-claude/admin-api and https://platform.claude.com/docs/en/manage-claude/usage-cost-api