I can't use my Alibaba Token Plan

[mabdelfattah]

When I run ocr configure provider, I can see only Alibaba DashScope Token Plan API and not Alibaba Token Plan where I got from https://modelstudio.console.alibabacloud.com/

[basil-k-aji-dev]

The entry you're seeing is region-pinned, and that is the whole problem.

dashscope-tokenplan is preset to
https://token-plan.cn-beijing.maas.aliyuncs.com/compatible-mode/v1
(internal/llm/providers.go:161-165, and the provider table in
docs/en/configuration.md). That host is cn-beijing. A key issued from
modelstudio.console.alibabacloud.com belongs to the international
(ap-southeast-1) region, and Model Studio keys do not cross regions — the docs
are explicit that each region has its own endpoint, API keys and model list. So
picking that entry would fail on auth even if the label read the way you expected.

There is no missing menu item to add, and this is the part worth knowing.
The international OpenAI-compatible base URL is workspace-scoped:

https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1

with the Beijing form being the same shape under cn-beijing. Because the
hostname embeds your workspace id, it can never be a fixed preset the way
dashscope is. Looked at that way, token-plan in the preset above is just the
workspace slot for one specific Beijing workspace.

What works today, no new build required — override the URL on any preset
that speaks the OpenAI protocol:

ocr config set provider                    dashscope
ocr config set providers.dashscope.api_key "$MODELSTUDIO_API_KEY"
ocr config set providers.dashscope.url     https://<WorkspaceId>.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1
ocr config set model                       qwen3.8-max
ocr llm test

providers.<name>.url takes precedence over the preset Base URL and falls back
to the preset when cleared, so nothing else about the provider changes. Your
WorkspaceId is in the Model Studio console; set model to whatever that
workspace actually exposes, since the model list is regional too.

On the PR you linked: #1396 adds dashscope-codingplan and
dashscope-codingplan-intl. Coding Plan and Token Plan are different products,
so that PR will not add the entry you're asking about — the -intl preset it
adds is for Coding Plan subscribers. Worth knowing before you wait on it.

If what you actually want is an international Token Plan preset, that is a
separate request, and the workspace-scoped URL above is the reason it would have
to be configured rather than preset.