FAQ

Q: Can one API key configure multiple clients?

Yes. The three clients share one key, but each has its own environment variables and config file. See one key, multiple clients.

Q: Where can I check current prices, balance, and usage?

Prices, balance, request logs, and usage details are listed in pricing, balance, and usage. Use the unit price shown on the page at that time.

Q: How are API request data and privacy handled?

Bodies are used for that request's routing and billing and are not kept long term. Usage, status, and security logs are kept. See API data and privacy and the privacy policy.

Q: Does model support mean every client protocol is supported?

No. A model, client, and request protocol combination can have different capabilities or limits, so confirm the specific combination first. See the model capabilities catalog.

Q: What should I do if my API Key leaks?

Open the API Keys page and click "Rotate Key" immediately. The old key becomes invalid at once.

Q: Why do requests return 401?

Check:

1. Whether the API Key is correct
2. Whether the API Key has expired or been disabled
3. Whether environment variables or config files are set correctly
4. Whether you reopened the terminal after changing environment variables

Q: Why do requests return 429?

This means the request rate is too high. Retry later. Add retry logic in your code when appropriate.

Q: Why do Windows environment variables not take effect?

After setting environment variables, you need to open a new PowerShell window.

Q: What if api.icodeeasy.cc is slow?

Use connection and recovery first to rule out 401, 403, and 429. After you confirm the network is slow, change the Base URL to https://jp.icodeeasy.cc or https://sg.icodeeasy.cc.

• Claude Code (including Kimi through Claude Code) / GLM / MiniMax: change ANTHROPIC_BASE_URL
• Kimi Code CLI: change the provider base_url in ~/.kimi-code/config.toml and keep /v1
• Codex: change base_url or OPENAI_BASE_URL
• Gemini CLI: change GOOGLE_GEMINI_BASE_URL; do not append /v1beta

Q: How do I report a problem?

Submit a ticket on the Tickets page. We will handle it as soon as possible.