# Get current key usage

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

## 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.

```http
Authorization: Bearer YOUR_API_KEY
```

## Request parameters

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

## 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.

## Code examples

### curl

```bash
curl --request GET 'https://api.tu-zi.com/api/usage/token/' \
  --header 'Authorization: Bearer YOUR_API_KEY'
```

### python

```python
import json
import os
import requests

url = "https://api.tu-zi.com/api/usage/token/"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.
```

### javascript

```javascript
// Node.js 20+
const url = "https://api.tu-zi.com/api/usage/token/";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.
```

## Response fields

| Field | Type | Description / constraints |
| --- | --- | --- |
| code | boolean | Success flag; this endpoint uses code, not success. |
| message | string | Result message. |
| data.object | string | Always token_usage. |
| data.name | string | Token name. |
| data.total_granted | integer | Remaining plus used quota. |
| data.total_used | integer | Used quota. |
| data.total_available | integer | Remaining quota. |
| data.unlimited_quota | boolean | Whether quota is unlimited. |
| data.model_limits | object | Model restriction map. |
| data.model_limits_enabled | boolean | Whether model restrictions are enabled. |
| data.expires_at | integer | Unix seconds; 0 means no expiry. |

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

```json
{
  "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.

## Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-token-usage

This export contains documentation and examples only, without real credentials, account data or user requests.