FAQ

Troubleshooting errors

Error	Cause	Fix
401 Unauthorized	Token invalid, copied incompletely, or expired	Check it on the console's “Tokens” page, and regenerate if needed
403 / insufficient quota	Token or account balance is insufficient	Check the token's remaining quota and account balance
404 model not found	Model name is wrong, or the token's group doesn't include it	Verify the model name and token group against the “Model Square”
429 Too Many Requests	Rate limit triggered	Lower the request rate and retry later
Connection timeout / unreachable	Network issue or wrong address	Check that the address is https://api.treenew.online/v1 (the /v1 is required)

Billing

How is it billed? By the tokens actually consumed. Prices vary by model — see each model's rate description in the console's “Model Square”.

Where can I see consumption details? The console's “Logs” page shows the model, token count and cost of each call; the “Dashboard” provides summary statistics.

Usage

Does the API address need /v1? Always use https://api.treenew.online/v1. The gateway only accepts paths with /v1; without it you do not get a 404 — you get an HTML page, which clients usually surface as "failed to parse response" or an empty model list, making the real cause hard to spot. A few clients append the version path themselves; if that produces /v1/v1 and a 404, use https://api.treenew.online instead.

Streaming output stalls or hangs? The gateway is optimized for SSE streaming (buffering disabled). If problems persist, check your local network proxy settings, or use non-streaming to verify the token works.

Which models are supported? Refer to the live list in the console's “Model Square”, which is updated continuously.

Still have questions?

Sign in to the console to view announcements, or contact the administrator.