Use z.ai in your coding agents

A base URL that ends in v4

Most OpenAI-style providers end their base URL in /v1. z.ai's ends in /api/paas/v4, and yoink keeps it exactly like that. Its URL normalizer treats any trailing /v<number> as a version, so it never appends a second /v1. The model picker therefore reads https://api.z.ai/api/paas/v4/models, and agents that want a full request path get one built on the same base: Goose, for example, is given https://api.z.ai/api/paas/v4/chat/completions.

The same rule matters if you ever add z.ai as a custom provider instead of the preset. Paste the v4 URL as is and the probe will try /chat/completions and /responses under it unchanged.

Add it

The preset id is zai, without a dot. The label is Z.ai, so the interactive flow suggests the profile id z-ai; the scripted example uses zai. Keys come from https://z.ai/manage-apikey/apikey-list.

yoink add
 
echo "$ZAI_API_KEY" | yoink add --external --name zai --preset zai \
  --models <model> --connect opencode,pi,qwen,goose --default <model> --token-stdin

GLM model ids are not built into yoink. Pick them from the live list, or pass the ids exactly as z.ai's /models returns them. Do not reuse OpenRouter ids here: OpenRouter prefixes the vendor, as in z-ai/glm-4.7, and that prefixed form belongs to the OpenRouter preset.

yoink models zai

What Qwen Code and Goose get

Qwen Code takes Chat Completions. yoink adds one entry per model under modelProviders.openai in ~/.qwen/settings.json and puts the key in the env block once (entry trimmed):

{
  "modelProviders": {
    "openai": [
      {
        "id": "<model>",
        "baseUrl": "https://api.z.ai/api/paas/v4",
        "envKey": "YOINK_ZAI_API_KEY",
        "wireApi": "chat-completions"
      }
    ]
  },
  "env": { "YOINK_ZAI_API_KEY": "<your key>" }
}

Goose (experimental) gets custom_providers/custom_zai.json with "engine": "openai" and "api_key_env": "CUSTOM_ZAI_API_KEY", plus GOOSE_PROVIDER: custom_zai in config.yaml. Unless Goose runs with GOOSE_DISABLE_KEYRING, export CUSTOM_ZAI_API_KEY in your shell or enter the key once with goose configure.

Use it in Claude Code

Connecting z.ai to Claude Code with yoink connect zai --to claude-code --default <model> writes ANTHROPIC_BASE_URL=https://api.z.ai/api/anthropic into ~/.claude/settings.json, gives every tier the same GLM model, and makes z.ai the active profile. Providers lists the seven keys, and switching back to a Claude account removes them.

Note the shape of this second URL: /api/anthropic sits beside /api/paas/v4, not under it, and has no version suffix. The preset holds the two as separate endpoints, each tagged with its own protocol, so the v4 rule above applies only to the Chat Completions address. Droid and Claude Desktop are the other two agents that take this Anthropic endpoint.

FAQ