/v1/chat/completions
Use with OpenAI SDKs, Cherry Studio, Cline, Open WebUI, and most tool clients.
Request formats
/
Nothing matches that. Try a protocol, a capability or an endpoint path.
Three request formats cover the whole catalogue. One ChinaAPI key and one Base URL work across all of them, so send whichever one your client already speaks.
/v1/messages
Route Claude-style message payloads while keeping the same gateway key and quota controls.
/v1/responses
Use with Codex and other clients built on the Responses API. The console marks which models accept it.
Gemini models only
Native Gemini requests go to
POST /v1beta/models/{model}:generateContent. Only gemini-* models offer it, and not all of them do — each model's entry in Models lists the formats it accepts. Everything else takes one of the three formats above.
Multi-turn Responses conversations point at an earlier reply with previous_response_id. If a follow-up comes back with previous_response_not_found, the earlier reply has not been lost: wait ten to twenty seconds and send the same request again rather than rebuilding the conversation from scratch.