API Reference

Get current key usage

Get current key usage. Fields and permissions follow this gateway implementation.

GET https://api.tu-zi.com/api/usage/token/
Preview guide

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

Preview guide

Get current key usage

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/api/usage/token/

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.

Request parameters

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

Response fields

FieldTypeDescription / constraints
codebooleanSuccess flag; this endpoint uses code, not success.
messagestringResult message.
data.objectstringAlways token_usage.
data.namestringToken name.
data.total_grantedintegerRemaining plus used quota.
data.total_usedintegerUsed quota.
data.total_availableintegerRemaining quota.
data.unlimited_quotabooleanWhether quota is unlimited.
data.model_limitsobjectModel restriction map.
data.model_limits_enabledbooleanWhether model restrictions are enabled.
data.expires_atintegerUnix seconds; 0 means no expiry.

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

{
  "code": true,
  "message": "ok",
  "data": {
    "object": "token_usage",
    "name": "demo",
    "total_granted": 1000,
    "total_used": 100,
    "total_available": 900,
    "unlimited_quota": false,
    "model_limits": {},
    "model_limits_enabled": false,
    "expires_at": 0
  }
}

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.