← ClaudeAtlas

anthropic-admin-cost-apilisted

This skill should be used when provisioning Anthropic Admin API access, minting an Admin API key or an org:admin OAuth token, querying the Usage & Cost API (`/v1/organizations/cost_report` or `/v1/organizations/usage_report/messages`), diagnosing why the Console's "Admin keys" page 404s or the "+ Create key" dialog has no type selector, or investigating unexpected/high Anthropic spend by workspace or model. Trigger phrases include "anthropic admin api key", "anthropic cost report", "anthropic usage api", "sk-ant-admin", "ant auth login", "org:admin scope", "anthropic organization cost_report", "platform.claude.com/settings/admin-keys 404", "anthropic individual org admin api unavailable", "cache_creation.ephemeral_5m_input_tokens", "anthropic cost by workspace".
jackson2w/claude-code-skills · ★ 1 · AI & Automation · score 64
Install: claude install-skill jackson2w/claude-code-skills
# Anthropic Admin/Cost API: org-tier gating, the `ant` CLI, and cost_report mechanics ## The org tier gates everything, before any credential type **The Admin API (and everything behind it — Usage & Cost API, Rate Limits API, Compliance API) is completely unavailable on an "Individual" org**, regardless of credential type. This isn't a missing permission or a hidden settings page — it's the account tier. Symptoms, all three confirmed live on an Individual org (2026-08-23): - `platform.claude.com/settings/admin-keys` and `console.anthropic.com/settings/admin-keys` (the two documented Console paths) both 404. - The Console's own "+ Create API key" dialog has no type/scope selector at all — only Name and Workspace, same as every regular workspace-scoped key. - Even a genuine `org:admin`-scoped OAuth token (see below) issues successfully, but a real call to `cost_report` returns `{"type":"error","error":{"type":"permission_error","message":"Missing permissions..."}}`. **Diagnostic shortcut**: run `ant auth status` (see below) — if it names the org "**\<Name\>'s Individual Org**", that's the root cause, full stop. Don't spend more time hunting Console UI paths or trying different credential types; converting the org to Team tier (a billing/plan decision, not something to do on the user's behalf) unlocks Admin API access **immediately with the same already-issued OAuth token** — no new login needed, confirmed by re-running the identical `cost_report` call right after a t