Troubleshooting

The goal is to isolate whether the issue is in credentials, protocol, model, routing, network, client behavior, or an upstream service.

1. Bypass the third-party client

curl https://aikey365.com/v1/models \
  -H "Authorization: Bearer $AIKEY365_API_KEY"

If this fails, fix the API key, network, or platform-side issue first.

2. Test the target endpoint

Chat Completions, Responses, Messages, and Gemini are different protocols. Use a minimal request that matches the client you are configuring.

3. Re-fetch the model ID

Do not depend on old screenshots or copied configuration.

4. Review key policy

Check that the key is enabled, not expired, has quota, permits the model, satisfies IP rules, and has eligible routing candidates.

5. Review usage and logs

Use request time, model, HTTP status, and error text to locate the relevant failure.

6. Return to the client

If curl works but the client does not, inspect cached configuration, path concatenation, environment variables, proxy settings, and the actual wire protocol.

When requesting support, provide time, client version, endpoint, model ID, HTTP status, and error text. Never share a full API key or password.