Access and Testing

Usage logs

Configuration notes

Usage logs show recorded calls: model, endpoint, streaming state, quota usage, and billing source.
Log types differ: Consume is billed or settled calls only; Error is only some failures that already reached upstream and can be empty; Refund appears only after a charge is returned.
A client-side 401, 403, 504, or connection failure often has no consume row. That does not mean the platform never received the request. Start from the client status, error body, and request_id.
When a consume row exists, check request_id, model, tokens, channel, and deduction. When it does not, follow the API error guide.
For async image or video tasks, use task logs.

For status-specific actions, empty usage logs on failed calls, streaming failures, and the support checklist, see [API errors and troubleshooting](/en/docs/api-errors-and-troubleshooting).