Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For direct Anthropic API usage, start in the Claude Console Usage page and export its CSV to compare usage by API key and model. For a deeper, repeatable breakdown, use Anthropic’s organization Messages usage-report API. If requests are billed through Amazon Bedrock, investigate in AWS instead: Anthropic’s Admin, Usage, and Cost API endpoints are not supported for Bedrock.
Usage reports show where API activity is attributed; they do not by themselves establish why a balance changed or which billing arrangement applies. First identify the billing route, then compare a consistent time window with your application logs and billing information.
Choose the usage view for your billing route
| Reporting route | Best for | What it can show | Key limitation |
|---|---|---|---|
| Claude Console Usage CSV | A quick manual audit | Usage broken down by API key and model, as described in Anthropic’s usage reporting instructions. | Use this route for traffic billed directly by Anthropic; confirm the provider before interpreting the report. |
| Organization Messages usage-report API | Automated or more detailed attribution | Can group or filter by API key, workspace, model, service tier, context window, and other documented dimensions; supports daily, hourly, and minute buckets. | Requires an Admin API key with suitable organization permissions. Queries have bounded ranges and may require pagination; see the API reference. |
| AWS Bedrock reporting and logging | Requests billed through Bedrock | Use AWS-side billing and usage information and, where useful, Bedrock invocation logging. | Anthropic documents that its Admin, Usage, and Cost API endpoints are not supported for Bedrock. See Claude on Amazon Bedrock. |
Audit direct Anthropic usage in the Console
- Open the Usage page in Claude Console and export the report as a CSV, following Anthropic’s usage reporting instructions.
- Compare equivalent time periods. Check whether the change is concentrated in a particular API key or model rather than assuming the whole organization’s usage rose evenly.
- Keep the export with incident notes and compare the affected interval with application request logs, deployments, scheduled jobs, and retry behavior. This correlation can help identify a change in your system; it is an investigation method, not proof of a particular cause.
Use the usage-report API for more detailed attribution
Anthropic documents GET /v1/organizations/usage_report/messages for programmatic reporting. Its grouping and filtering options include api_key_id, workspace_id, model, service_tier, and context_window; the reference also lists account and service-account IDs and inference geography. The response includes token-usage categories and may include server tool use, so token totals alone may not explain every billable component. Check the applicable pricing and enabled features as well as the report.
Time boundaries use RFC 3339 and are snapped to UTC bucket boundaries. The documented maximum query spans are 31 daily buckets, 168 hourly buckets, or 1,440 minute buckets. When a response indicates more results with has_more, continue using the returned next-page token. These are endpoint query limits, not estimates of typical usage.
Example request shape, adapted from Anthropic’s API reference:
curl "https://api.anthropic.com/v1/organizations/usage_report/messages?starting_at=2026-10-01T00:00:00Z&group_by[]=api_key_id&group_by[]=workspace_id&group_by[]=model&bucket_width=1h&limit=24"
--header "anthropic-version: 2023-06-01"
--header "x-api-key: $ANTHROPIC_ADMIN_KEY"Choose a bounded date range and review the current endpoint reference for supported parameters. Protect the Admin API credential as you would other organization-level secrets.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Diagnose an unexpected drop or failed request
1. Confirm who bills for the traffic
Determine whether requests go directly to Anthropic or through Amazon Bedrock. For Bedrock traffic, use AWS billing and usage views and consider enabling Bedrock invocation logging; Anthropic’s Admin, Usage, and Cost endpoints do not support Bedrock usage.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
2. Compare matching reporting windows
Use the same UTC interval and bucket size when comparing reports. Inspect API key, workspace, model, and service-tier attribution for a step-change or concentration that lines up with the unexpected usage.
3. Correlate the interval with your application
Check request logs and relevant deployment changes, retries, scheduled jobs, and newly enabled features. Treat these as leads to verify against actual requests, not automatic explanations for higher usage.
4. Distinguish spend controls, billing trouble, and rate limits
Anthropic’s error documentation describes different possibilities: a 400 can indicate that an organization or workspace spend limit is configured and reached; a 402 points to billing or payment trouble; and a 429 can mean rate limiting or an applicable spending ceiling, including a monthly tier spend cap or a Claude Code workspace spending limit. A 429 alone does not establish that prepaid credits are exhausted.
Compare the error with your account’s configured limits and payment details. Anthropic says billing is based on actual monthly usage, payments are in USD, and usage tracking is available in Claude Console; review its pricing information alongside the account’s billing view and payment or credit arrangement. A usage report or one status code is not, on its own, a complete billing diagnosis.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →5. Preserve details for a specific failure
Record the affected UTC interval, organization and workspace, API key identifier (never the secret), model, HTTP status, and error body. Keep the response’s request ID: Anthropic says each response has a unique ID and asks customers to include it in support requests. See its error guidance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
