Claude API Usage and Cost Monitoring: Admin Key Setup

Track current-month Claude API costs with a Claude Console Admin API key, optionally by Workspace. Covers permissions, reporting delays, and balance limits.

Costs only · Not a balance

Guide updated

Official costs, monthly limits and organization fallback are implemented but await live-account verification. Prepaid balance retrieval is not implemented; usage, spending, and internal budgets are not account funds.

Required credentials
Anthropic Admin API Key
Monitoring currency
USD · US dollar
What is monitored
Monthly costs / official monthly limit / headroom · not account balance
Cost API spending reported from the start of the current UTC month to query time. No filter covers the entire Anthropic organization; a Workspace filter keeps that group's costs as the main amount. Organization fallback separately shows total organization costs and shared headroom without replacing Workspace costs or internal budgets. Decimal USD cents are converted exactly to dollars.

How to check Claude API usage and spend limits manually

  1. Open the Usage page in the Claude Console to review API usage.
  2. Open Settings › Billing to see your usage tier's monthly spend cap and set your own spend limit if needed.
  3. Open the Rate limits page to see the organization's current usage tier and rate limits.
Open official Anthropic / Claude API page(opens in a new tab)

Connect Anthropic / Claude API to Quota Monitor

  1. Confirm that you need costs, not a balance

    For remaining prepaid funds, use official Settings → Billing. Do not submit a privileged key for a balance feature we do not support. Check: you accept that this connection shows costs, not funds available in a wallet.

  2. Sign in to the correct API organization

    Open Claude Console with the account responsible for API spending and select the correct organization, not a claude.ai chat subscription. Individual accounts cannot use the Admin API. If needed, set up an organization through Settings → Organization and have an organization administrator proceed. Check: the organization matches your API traffic and you have the admin role.

  3. Open the dedicated Admin keys page

    Go to Settings → Admin keys, not the ordinary API keys page. If unavailable, contact the organization administrator; do not substitute a model key. Check: the page is Admin keys within the intended organization.

  4. Create and securely save a dedicated key

    Click Create key, name it QuotaMonitorCost, select an appropriate expiry, and create it. Console Admin keys have no selectable read-only scopes; stop if this risk is unacceptable. The full secret appears once. Store it in a password manager, never in chats, tickets, or screenshots. Check: you saved the complete sk-ant-admin01- value securely.

  5. Optionally choose the upstream Workspace

    Leave the filter blank for organization-wide costs. For a non-default Workspace, open Settings → Workspaces, select the target, and copy its full wrkspc_ ID from its details or URL, not its name or secret. If unavailable, ask the administrator for the official ID rather than guessing. For the Default Workspace, enter default. Check: this scope contains the business keys and is not a Quota Monitor project or workspace ID.

  6. Fill in the connection inside your project

    In the target Quota Monitor project, add a provider connection and choose Anthropic / Claude API (costs · USD). Paste the key into the masked Anthropic Admin API Key field; optionally name the connection after its business purpose. Check: the input is masked and contains no Cookie, OAuth token, or ordinary Workspace model key.

  7. Set the scope and save

    Leave Anthropic Workspace ID (optional) blank for the organization, enter a wrkspc_ ID for that Workspace, or default for the Default Workspace. Currency is fixed to USD; no organization ID or API address is needed. Click Save and connect to project. Check: the connection appears in the intended project. For save errors, check credential type and fields without sharing the secret.

  8. Sync and compare official costs and limits

    Wait for the first sync or click Sync costs. Compare costs for the same organization, Workspace and UTC month on the Cost page. Check organization caps at Settings → Billing → Spend limits, or workspace caps at Settings → Workspaces → target Workspace → Spend limits. Never compare costs or headroom with prepaid funds. If the limit is not retrieved, expand About spend limits and check the Admin key, organization permissions and early-access preview eligibility. Contact your Anthropic account team if access is not enabled; do not change production limits to troubleshoot. Check: costs, official monthly limit and headroom are separate. Zero costs do not prove that the Workspace ID is valid or funds remain.

    If the card says No Workspace limit · Using organization limit, keep the Workspace filter in Quota Monitor and remove the Workspace filter on the official Cost page to compare total organization costs for the same UTC month. This also applies to default; you do not need to clear our filter. Check: Workspace costs remain the main amount, while the organization monthly limit, total costs and remaining headroom are labeled separately. This headroom is shared by the entire organization.

  9. Maintain credentials and query status

    When the key expires or is revoked, update it in connection management with a new dedicated Admin key. Verify the new key before revoking the old one without affecting business credentials. Internal budgets do not change Anthropic limits or top up funds. Failed refreshes keep previous data with a failure notice. Check: rely on a new snapshot only after a successful timestamp, and periodically verify organization and scope.

What Quota Monitor reads from Anthropic / Claude API

  • This integration uses the official Cost API and Spend Limits read endpoint, not prepaid balance endpoints. It accepts neither browser Cookies nor Claude Code OAuth tokens and never estimates remaining account funds.
  • Cost reporting typically arrives about 5 minutes after a request and can take longer. Refresh reads the latest reported data, not instant settlement. Priority Tier costs are excluded; this is not an all-product invoice total.
  • Cost Report supports Workspace grouping, not individual API key cost filtering. An Anthropic Workspace is separate from a Quota Monitor workspace or project. We do not create upstream workspaces.
  • The Default Workspace is null in reports, so enter default to filter it; blank means the entire organization. Claude Pro/Max/Team/Enterprise subscriptions, Bedrock/Vertex billing, and Claude Platform on AWS are outside this connection.
  • Limit reads use the spend-limit-reads-2026-09-26 beta, require Anthropic early-access preview eligibility, and await live-account verification. The Workspace monthly limit takes priority; organization fallback occurs only after a complete successful list confirms it is unconfigured. Default Workspace has no separate cap, so it attempts organization fallback directly. Access denial, throttling, unavailable endpoints or incomplete data leave costs visible and the limit marked as not retrieved, never unconfigured.
  • Headroom is the matching monthly limit minus reported costs, not real-time funds. Costs excluded from the report, including Priority Tier, can affect actual available capacity. Organization fallback uses total organization costs for the same UTC month. All Workspaces share this headroom; never add it across cards. An unconfigured organization cap is explicitly labeled and does not mean unlimited usage. Invalid organization limits or costs never produce an invented zero or headroom.
  • The dashboard shows the latest successful cost snapshot. Refresh cannot remove upstream reporting delays. An old cost and timestamp after a failed query are not a new report.

Anthropic / Claude API FAQ and troubleshooting

Why is Admin keys missing, or why do I get 401 / 403?
Use the intended organization on platform.claude.com with an organization admin account. Individual accounts and Workspace model keys cannot substitute for the Console Admin key in this guide. Check expiry, revocation, and incomplete copying. Report only the error code and query time, never the key.
Why is there no remaining balance after a successful sync?
This connection reports costs and matching monthly limits, not prepaid funds. balanceAmount is always null. Neither headroom nor an internal budget is a wallet balance; check official Billing for funds.
Why is organization headroom low when this Workspace has spent little?
This Workspace has no separate monthly limit, or is the Default Workspace, so we attempt to use the organization limit. Headroom subtracts reported costs for all Workspaces in the month, not just this one. Remove the Workspace filter on the official Cost page to compare. Never add the same organization's shared headroom across connections.
Why are costs available but the organization limit is still not retrieved?
Successful Cost API access does not imply access to the limits beta. Expand About spend limits and verify the Admin key and organization. Console limit reads require early-access preview eligibility; contact your Anthropic account team if it is not enabled. Retry later for throttling. Workspace costs are preserved, but errors never mean no configured limit and never produce zero or invented organization headroom.
Why are costs zero or lower than expected?
Check the UTC month, organization, and Workspace ID. Enter default for the Default Workspace, not its wrkspc_ ID; a blank filter covers the organization. Reporting usually takes about 5 minutes and may take longer. Priority Tier is excluded. Zero costs neither mean zero funds nor validate the filter ID.
Can I query a single model key, a Claude subscription, or a cloud platform?
Cost Report groups by Workspace and does not allocate costs to individual keys. This connection excludes chat subscriptions, Bedrock/Vertex, and Claude Platform on AWS. Token counts multiplied by model prices are not substituted for official costs.
Is there a read-only alternative to custody of an Admin key?
Console Admin keys have no selectable read-only scopes. Our read-only requests do not reduce the key's underlying management permissions. If that risk is unacceptable, use the official Cost page. This integration does not offer Cookie or OAuth alternatives.
What errors does the Claude API return when a spend limit is reached?
When a spend limit you set for the organization or a Workspace is reached, requests return HTTP 400 with type invalid_request_error and a message beginning You have reached your specified API usage limits. When your usage tier's monthly spend cap is reached, requests return HTTP 429 with type rate_limit_error, error.details.error_code enforced_spend_limit_reached, and no retry-after header; retries keep failing until 00:00 UTC on the first day of the next month or until you move to a higher tier. Billing or payment problems return 402 billing_error.

Official Anthropic / Claude API references

Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.

Monitor Anthropic / Claude API automatically

Checking a console by hand is easy to forget. Quota Monitor reads Anthropic / Claude API through its official API for you.

  • Refreshes every 10 minutes by default, and you can refresh manually at any time.
  • Internal budget warnings, invalid credentials and sync failures rise to the top; reported costs are not wallet funds.
  • Group cost reports by project and read the same scoped costs through remote MCP. Internal budgets never change provider limits.
Start for free

See current Claude API prices