Source boundary
Anthropic
Confirm source eligibility in your workspace before creating access.
- Financial source
- Organization cost report with usage attribution when supplied
- Reviewed
- 2026-09-17
- Cost bases
- net, billed, credits
- Useful dimensions
- organization, workspace, model, token type, API key, user or product feature when supplied
Known limits
- Null or default workspace attribution remains explicit.
- Cloud-marketplace charges remain with the billing cloud provider.
Prepare the connection
Eligibility
Claude Console organizations need Usage and Cost Admin API access. Claude Enterprise uses the separate Analytics API. Claude Platform on AWS does not expose this direct Usage and Cost API.
Use a reporting or Admin API key. Keyless federation remains unavailable until Anthropic provides a suitably limited read-only scope.
Authentication choices
- Reporting or Admin key — recommendedPruneFox stores the credential encrypted in the isolated credential broker and never returns it to the browser.
Connection details
| Field | Why it is needed | Example format |
|---|---|---|
| Connection mode | Choose the Anthropic product that issued this key; the two key types are not interchangeable. | Choose a mode |
| Organization ID | Anthropic organization that owns the reported cost. | org_… |
| Reporting API key | Console Admin API key or Enterprise Analytics API key for the selected mode; workspace keys do not work. | Write-only value |
Permission boundary
| Resource | Read or bounded staging permissions | Purpose |
|---|---|---|
| Selected Claude Console organization | organization usage report read, organization cost report read | Read reporting without model invocation, workspace mutation, key administration, or user management. |
Connection sequence
- Choose the correct product route: Claude Console, Claude Enterprise, or cloud marketplace.
- Choose Console or Enterprise as the connection mode, then create its dedicated reporting key rather than a workspace key.
- Enter the organization ID and key.
- Validate organization identity, key type, reporting product, pagination, cost coverage, and usage dimensions.
Validation and first sync
Validation rejects workspace keys, a different organization, Enterprise or AWS product routes presented as Console, incomplete pagination, or unavailable direct cost.
Direct cost and usage are paginated independently. Enrichment failure is visible and cannot silently convert usage into cost or erase direct financial totals.
Freshness: Direct cost is daily. Priority Tier cost is not included in the direct cost endpoint and must remain explicitly unavailable rather than reconstructed.
Remove access
Revoke the PruneFox connection, then revoke the dedicated Admin API key.
Troubleshooting
Check the Claude product, organization identity, Admin versus workspace key, pagination, daily boundaries, and whether Priority Tier or marketplace billing is outside the direct endpoint.
Verify the first completed period
Compare one bounded completed period with the provider billing source. Match currency and cost basis, inspect credits and adjustments, and confirm that missing dimensions remain unavailable rather than zero.
Troubleshoot safely
Use the visible connection state, provider name, affected date range, and expected outcome. Never send credentials, raw billing exports, payment data, or customer records through support.