Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Alibaba Token Plan providers point at the undocumented region-scoped hosts

Open Beginner friendly
  • Is something wrong?
#7,974 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend-api-design

Research direction

The issue points to two provider TOML files: providers/alibaba-token-plan/provider.toml and providers/alibaba-token-plan-cn/provider.toml. Update the api field in each file to the new canonical hosts provided. Verify the change by checking the file structure and ensuring no other lines are altered. Done when both URLs are updated and the PR is submitted.

Written by the indexing model from the issue text.

Description

Both Alibaba Token Plan providers still point at the region-scoped maas.aliyuncs.com base URLs:

  • providers/alibaba-token-plan/provider.toml: https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1
  • providers/alibaba-token-plan-cn/provider.toml: https://token-plan.cn-beijing.maas.aliyuncs.com/compatible-mode/v1

The vendor replaced those on its own Token Plan documentation on 2026-09-23. The quickstart, FAQ and best-practice pages on both the international and mainland China sites now give brand-scoped canonical hosts instead:

  • International: https://token-plan.maas.qwencloudapi.com/compatible-mode/v1
  • Mainland China: https://token-plan.maas.qianwenaiapi.com/compatible-mode/v1

That matches the branding split described in #4296, where qwencloud serves markets outside mainland China and the Qwen AI Platform brand serves mainland China.

What I checked

On 2026-09-24, with a live Token Plan key, GET /compatible-mode/v1/models against both the old and the new international host returned HTTP 200 with a byte-identical list of model ids. The new host is the same service, not a different catalogue.

Without a key both hosts return the same 401, so the new host is in service and behind the same auth gate rather than being a documentation typo.

The old hosts still answer today. The concern is that they are no longer the documented ones, so they are the pair likely to be retired, and downstream consumers reading the api field would break at that point with no warning.

Suggested fix

Change the api line in each of the two provider TOMLs. Two lines, no model rows touched.

This is deliberately narrower than the provider ID and display-name migration under discussion in #4296. The base URL change is a concrete, verifiable fact today and does not depend on how that naming question is resolved.

Dominant language
TypeScript
Stars
6.9k
Forks
1.7k
Avg merge
2h 57m
Merged PRs (30d)
850

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anomalyco/models.dev

All issues in anomalyco/models.dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.