Stale Alibaba Token Plan catalogs: phantom glm-5.3 rows, wrong qwen3.8-max window, missing callable ids #4787

Client or integration

Other (provider catalog data; surfaces in the Codex model picker)

Summary

Both alibaba-token-plan presets (Beijing and International) ship catalog facts that do not match what the Token Plan gateway actually serves. Four classes of defect, all re-verified on 2026-09-07 and 2026-09-09 against the live gateway on both regions and both subscription tiers:

1. Phantom rows. glm-5.3 and glm-5.3-flash are listed on both Token Plan presets. These models exist on Z.AI endpoints, but the Token Plan gateway has never served either id; selecting the row fails with model-not-found. They arrived via the 260826 seed commit that propagated GLM-5.3 across every GLM-carrying catalog, including the plan presets.
2. Wrong context window. qwen3.8-max is pinned to 983_616 in both presets. That number is the CLAUDE_CODE_MAX_CONTEXT_TOKENS client setting, not a model window; the real window is 1,000,000. The same figure circulated through two other third-party catalogs before, so it is easy to re-import by accident.
3. Missing callable ids. qwen3.8-flash (GA, listed by /models on both tiers), deepseek-v4-pro-0813 and deepseek-v4-flash-0731 (callable snapshots; the 0813 one is notably absent from the gateway's own /models listing) are not in the presets. And deepseek-v4-pro was recently dropped from the international lineup, but the plan gateway still lists and serves it on both regions (this is the plan roster, not the DeepSeek API, so upstream retirement does not apply).
4. Stale windows and missing ceilings. glm-5/glm-5.1 are 202,752 (not 1M) and MiniMax-M2.5 is 196,608 (not 204,800). Both presets also ship no modelMaxOutputTokens at all, so nothing clamps or advertises the output ceilings (deepseek-v4 family 393,216 on this gateway, probed at the boundary).

Expected: selecting any row in the Token Plan pickers routes to a model the subscription can actually call, with windows and output ceilings that match the gateway.

Reproduction

1. Configure the alibaba-token-plan-intl preset with any Token Plan key (Personal or Team tier).
2. In a routed client, select glm-5.3 from the model list.
3. The request fails at the gateway: the id is not in the plan's served set. On the free /models surface (probed 2026-09-07 and 2026-09-09, both regions, both tiers) Token Plan lists only glm-5, glm-5.1 and glm-5.2, and the vendor's own plan overview page lists the same three.
4. Same for a qwen3.8-flash request that is never offered at all: it is callable and listed by the gateway /models on both tiers, but it is not in the preset, so liveModels: false static users cannot select it.

Version

2.51.0 (also present in 2.31.0 through 2.46.0)

Operating system

Ubuntu 24.04 (arm64)

Provider and model

alibaba-token-plan-intl / glm-5.3, qwen3.8-max, qwen3.8-flash, deepseek-v4-pro-0813

Logs or error output

# GET /compatible-mode/v1/models on a Team key and a Personal key, SG and Beijing (2026-09-09):
glm ids returned: glm-5, glm-5.1, glm-5.2   (no glm-5.3, no glm-5.3-flash)
# qwen3.8-flash IS returned on both tiers but is absent from the preset.

Screenshots and supporting files

No UI involved. Per-value evidence (gateway probes with dates and methods, including max_tokens boundary probes for every output ceiling) is maintained in the machine-readable catalog at https://github.com/oliver-mee/alibaba-token-plan-wiki

Redacted configuration

{
  "providers": {
    "alibaba-token-plan-intl": { "adapter": "openai-chat", "authMode": "key", "liveModels": false }
  }
}

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.