Support
This section collects the most common user issues on Dli.li AI and the recommended troubleshooting path.
API recommendation
The official default API is `https://api.dli.li/v1`. The official backup API is `https://api.dlizz.com/v1`.
Quick entry points
- FAQ: common issues around balance, tokens, models, and client integration.
- Contact: join the QQ or WeChat group for human support.
- Guide: console pages and feature explanations.
- AI Apps: step-by-step client integration guides.
- API Access: OpenAI-compatible API usage for programmatic access.
Check these three items first
- Make sure the endpoint is correct and usually includes
/v1. - Make sure the API key comes from your own
API Tokenspage and was copied completely. - Make sure the model name is actually available to your current account.
Recommended troubleshooting order
- Start with Site Links and Billing Rules to confirm the API address, CNY settlement rules, and multiplier behavior.
- Then check API Tokens and Profile to verify the key and model availability.
- If a program or client returns errors, continue with Usage Log and Task Log.
- If the problem is still unclear, go back to FAQ and compare the issue against the common cases listed there.
Useful pages by scenario
| Scenario | Check this first |
|---|---|
| You do not know how to create a key | API Tokens |
| You want to test whether a model works | Playground |
| You want to inspect billing and request details | Usage Log |
| You want to connect a desktop client or IDE | AI Apps |
| Your program returns an API error | API Access and FAQ |
Find the right page by issue type
| Issue type | Recommended entry |
|---|---|
| You are not sure which address to fill in | Site Links and Billing Rules |
| You are not sure whether the key is correct | API Tokens |
| You are not sure whether a model is available | Profile |
| You want to inspect real requests and billing records | Usage Log |
| You want to inspect image or other async task results | Task Log |
Need human support
If FAQ and log troubleshooting do not solve the issue, visit Contact and report it in the community group.