API Reference
Get usage summary
Aggregate the current account’s recorded requests, errors, tokens and quota.
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
Updated · Reviewed
Endpoint and authentication
GET https://api.tu-zi.com/api/log/self/stat
Transport: json
Use an account system token and New-Api-User (account ID), or a valid site login session. Manage system tokens in account settings. Inference API keys are not substitutes.
Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID
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.
Set SYSTEM_TOKEN and USER_ID in the environment; keep system tokens out of frontend code. Replace YOUR_SYSTEM_TOKEN and YOUR_USER_ID in cURL.
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
This aggregate covers recorded logs, not account balance or billing settlement. Check logs_available/coverage; missing logs must not be treated as zero consumption.
Query parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| summary | boolean | Yes | Always true. Example: true |
| start_timestamp | integer | Yes | Start Unix seconds, inclusive. |
| end_timestamp | integer | Yes | End Unix seconds; greater than start and at most 90 days apart. |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| success | boolean | Business success; do not rely only on HTTP status. |
| message | string | Result or error message. |
| data.record_count | integer | Record count. |
| data.error_count | integer | Error count. |
| data.request_count | integer | Consumption request count. |
| data.quota | integer | Consumed quota. |
| data.prompt_tokens | integer | Total input tokens. |
| data.completion_tokens | integer | Total output tokens. |
| data.refund_quota | integer | Refund quota. |
| data.logs_available | boolean | Whether the log database is available. |
| data.coverage | string | Coverage marker; normally recorded_logs_only. |
| data.start_timestamp | integer | Start Unix seconds. |
| data.end_timestamp | integer | End Unix seconds. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"success": true,
"message": "",
"data": {
"record_count": 0,
"error_count": 0,
"request_count": 0,
"quota": 0,
"prompt_tokens": 0,
"completion_tokens": 0,
"refund_quota": 0,
"logs_available": true,
"coverage": "recorded_logs_only",
"start_timestamp": 1793404800,
"end_timestamp": 1793491200
}
}
Errors and retries
Check HTTP status and success. Business validation errors may return HTTP 200 with {"success":false,"message":"..."}; some include error.code. Authentication may return 401/403 and rate limiting 429. HTTP 200 alone does not guarantee success.
Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API