FAQ

Open Agent API Keys, create a new key in the API Keys area, then export it as GPT88_API_KEY and follow the Quickstart.

Yes. The request shape, error envelope, and streaming behavior are designed to stay compatible with OpenAI-style SDKs. In most cases you only replace base_url and the API key.

Yes. Any framework that supports an OpenAI-compatible provider can usually work by pointing it to https://api.gpt88.cc.

Kimi K3 (Model ID kimi-k3) is a strong candidate for long-context coding, knowledge work, reasoning, native visual understanding, and tool-calling workflows. In GPT88, use https://api.gpt88.cc and confirm account access and live pricing in model navigation or the console.

Yes. A group multiplier converts official API usage into the RMB deduction: actual deduction (RMB) = official usage (USD) x the selected group multiplier. A 2.0 multiplier deducts RMB 2.0 for $1 of usage, while 0.5 deducts RMB 0.5.

The multiplier appears in the group selector on the API Keys page. Groups use different upstream routes and may have different stability. Top-ups are 1:1: RMB 1 = 1.00 balance, even when the page uses a $ symbol.

Not recommended. API keys should stay on the server side. Use your own backend or edge route to proxy requests.

• error.request_id or X-Request-Id
• HTTP status and business error code
• Model ID and request timestamp with timezone
• Whether the issue is reproducible and under what pattern