Get help with ZhiFlo

Start with the shortest path for your problem. Whichever route you use, never send a complete Token, sign-in password, private source code, or private request content.

Check for a service interruption

If neither the website nor your client can connect, first open ZhiFlo service status. The status page reports portal and API endpoint reachability; it does not prove that every upstream model is healthy.

If only one model fails, confirm the complete model ID currently available to your account, then follow Troubleshooting in order: authentication, model, address, quota, and network.

A configured client still does not work

Open the matching client guide and confirm, in order: the configuration is saved, ZhiFlo is enabled, the current model has been switched, the client has been fully reopened, and a minimal “Reply with OK only” message receives a response.

If you already have an HTTP status, go directly to API error handling and avoid changing several settings at once.

Account, billing, or Token issues

Sign in to the API Portal and open the page that matches the issue:

• Token creation, quota, expiration, or revocation: API Keys;
• account balance: Wallet;
• an individual request’s status and usage: Usage Logs.

This help center does not currently provide a durable human contact channel. Do not treat personal accounts from portal announcements, search results, unfamiliar groups, or direct messages as a permanent support route, and never send them a Token, password, private source code, or private request content.

Record this information for further troubleshooting

• When the problem occurred and your time zone;
• operating system, client name, and client version;
• the exact action immediately before the failure;
• HTTP status, request ID, and error text after removing Tokens, passwords, and private content;
• a screenshot with sensitive information hidden;
• the complete model ID, but never the Token.

Hide Tokens, passwords, balances, personal details, private source code, and business request content from screenshots. If a Token was exposed, revoke it in the API Portal immediately and create a new one.