API Reference

Compatible cumulative usage

Compatible cumulative usage. Read-only compatibility for legacy clients.

GET https://api.tu-zi.com/v1/dashboard/billing/usage
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Compatible cumulative usage

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/v1/dashboard/billing/usage

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY

Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

Constraints

An alias exists without /v1. Use an inference key. DisplayTokenStatEnabled selects key or account cumulative values; open-platform keys always use their own values. Units follow USD/CNY/TOKENS display settings, not field names alone. Date-range filtering is not implemented; use account log statistics for time filters. Unlimited quota uses a limit placeholder of 100000000.

Request parameters

No request body is needed; send the authentication described above.

Response fields

FieldTypeDescription / constraints
objectstringlist.
total_usagenumberCumulative displayed consumed amount multiplied by 100; not a sum over a date interval.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "object": "list",
  "total_usage": 100
}

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.