Usage records
Find request times, models, status, and cost in AIXHUB to investigate errors and unexpected usage.
Usage records are the most important panel view for API diagnosis. They help connect local errors and HTTP status codes to account activity in the same time window.
Prerequisites
- You are signed in, and the account has sent at least one API request.
- You know the approximate time, key purpose, and model ID for the call.
- You saved the request ID if the client returned one.
Steps
-
Open Usage records from the console navigation.
-
Narrow the time range around the incident and note the time zone displayed by the console.
-
Compare the model, request status, tokens, or cost fields offered by the page. Use model or status filters when available.
-
Open the target entry and save only the request ID, time, and error summary that are safe to share. Do not copy API keys, full prompts, or other sensitive data.
-
If the entry succeeded but the client received no content, inspect streaming and client timeouts. If no entry exists, start with Base URL, proxy, and local network checks.
Verification
Troubleshooting
- A recent call is missing: Wait briefly, refresh, widen the time range, and verify the time zone.
- Calls to the same model have different cost: Compare input, output, cache, and other billing fields instead of counting requests alone.
- The record succeeded but the app failed: The error may be in response parsing, streaming, or later application logic.
- Unknown calls appear: Revoke the related key, replace it, and inspect every device that used it.
Next step
Pair this page with Dashboard and balance, or continue by status code in Troubleshooting.