Zhipu AI

Every Zhipu AI model in the catalog, grouped by family: the request formats each one accepts, a request you can send, and what the gateway does with each field. Back to all model makers.

Families

GLM · CogView · CogVideoX

Models

12

Tasks

LLM · Image · Video · ASR · TTS

Request formats

OpenAI-compatible · Anthropic Messages · Images API · Video API · Speech API · Transcription API

Capability profiles

9 / 12

Models

Request formats are declared per model. A format listed for the maker does not mean every one of its models accepts it.

GLM

CogView

CogVideoX

Request formats

One key and one Base URL serve every format, so send the one your client already speaks. A format that no model from this maker declares says so, instead of showing a request that would fail.

curl https://api.chinaapi.ai/v1/chat/completions \
  -H "Authorization: Bearer $CHINAAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "glm-5.3",
    "messages": [{ "role": "user", "content": "Hello" }]
  }'

curl https://api.chinaapi.ai/v1/messages \
  -H "x-api-key: $CHINAAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "glm-5.3",
    "max_tokens": 1024,
    "messages": [{ "role": "user", "content": "Hello" }]
  }'

What the gateway does with each field

From the published capability manifest, one table per capability profile. A row covers every model in the profile; where the models differ, the row names each one and how it handles the field.

• Native: forwarded unchanged.
• Translated: carried across to the field the model's own format uses.
• Normalized: rewritten before the request leaves the gateway.
• Model-specific: the models in the profile handle the field differently, or only some of them accept it.
• Partial: checked on some models in the profile, not yet on the others.
• Accepted but ignored: taken without an error, and not used.
• Not supported: the gateway does not carry the field for that model.
• Not verified: nobody has checked yet. It is not a claim that the field works.
• Not audited: the model has no published capability profile, so nothing is stated about its fields.

Capability profile glm-text

Models: glm-5 glm-5-turbo glm-5.1 glm-5.2 glm-5.3 glm-5.3-flash glm-5v-turbo

Capabilities

Parameters

Capability profile glm-speech

Models: glm-asr-2512 glm-tts

Parameters

Evidence levels

A row, like a model, is shown at the weakest level of evidence among the fields it covers, never above it.

• Catalogue-declared: stated in the catalog; the gateway's handling has not been checked.
• Code-checked: the gateway's request code was checked to send it as stated.
• Live-verified: confirmed with a real request.

Each model's full profile, with its notes and value ranges, is on Model parameters & capabilities.