FAQ

​

What is the difference between Token Plan and Coding Plan?

​

Important resources

• Token Plan page: Manage your subscription and view usage on the Token Plan page
• API Keys page: View and reset your API keys on the API Keys page
• Supported models: See the full list of models
• Setup guides: Configuration instructions for Claude Code, OpenCode, OpenClaw, and more

​

Start here: 60-second diagnosis

If your tool is not working and you see errors like 401, 403, 404, invalid access token, invalid api-key, quota exceeded, or connection failures, check these first:

1. API key: Must be the Token Plan dedicated key, not a pay-as-you-go sk- key or a Coding Plan sk-sp- key
2. Base URL: Must contain token-plan, not dashscope-intl or coding
3. Authentication header: Must use Authorization: Bearer, not x-api-key
4. Subscription status: Check whether your subscription is active and credits are not depleted
5. Updated config: Restart the tool after updating the API key or base URL

If you are still blocked, continue with the questions below.

​

Text generation

​

Which text generation models are supported?

Token Plan supports the following text generation models:

• qwen3.6-plus
• glm-5
• MiniMax-M2.5
• deepseek-v3.2

For the complete and up-to-date list, see Supported models.

​

Common errors and solutions

​

Image generation

​

Which image generation models are supported?

Token Plan supports the following image generation models:

• qwen-image-2.0
• qwen-image-2.0-pro
• wan2.7-image
• wan2.7-image-pro

For details, see Supported models.

​

Can I use image models in coding tools?

Image generation models use separate APIs and cannot be called directly through the text model's base URL. You must integrate them through your tool's skill or extension mechanism. For configuration steps, see the image generation model integration section in each tool's setup guide.

​

Common errors & fixes

​

Which API key and base URL should I use?

Use a Token Plan dedicated key and a Token Plan base URL:

• API key: Get it from the Token Plan page
• OpenAI compatible: https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1
• Anthropic compatible: https://token-plan.ap-southeast-1.maas.aliyuncs.com/apps/anthropic

Pay-as-you-go dashscope-intl URLs and Coding Plan coding-intl URLs do not work with Token Plan keys.

​

I got 401 or 403. Is my API key invalid?

If you see 401 invalid access token, InvalidApiKey, or 403 invalid api-key, the problem is usually a wrong key type, an expired subscription, a malformed key, or a key and URL mismatch. Check these points:

1. Confirm the key is your Token Plan dedicated key
2. Re-copy the key to remove hidden spaces or line breaks
3. Confirm your subscription is active on the Token Plan page
4. Make sure the base URL contains token-plan

In most cases:

• 401 invalid access token means wrong key type, expired subscription, or malformed key
• 403 invalid api-key means you are using a Token Plan key with a non-Token Plan URL
• Incorrect API key provided means you are using a Token Plan key with the general dashscope-intl URL

​

Why do I get 404 or connection errors?

If you get 404 status code (no body), endpoint not found, or connection errors, the base URL path is usually wrong for your tool. Use the correct path for your protocol:

• Anthropic-compatible tools use /apps/anthropic
• OpenAI-compatible tools use /compatible-mode/v1

Also check that the domain is exactly token-plan.ap-southeast-1.maas.aliyuncs.com.

​

Why is my model "not supported"?

If you get model 'xxx' is not supported or model 'xxx' not found, the model ID is usually incorrect, case-sensitive, or copied with extra spaces. Check these points:

1. Use the exact model name from Supported models
2. Remove any leading or trailing spaces
3. Verify capitalization exactly as documented
4. If using deepseek-v3.2, confirm you are using the OpenAI-compatible endpoint, not the Anthropic-compatible endpoint

​

How to handle input length limits?

If you get 400 InvalidParameter: Range of input length should be [1, xxx], your context or request exceeds model limits. Try these fixes:

1. Create a new session
2. Switch to a model with a larger context window
3. In your tool, configure context length limits if available

​

What should I do if I see data_inspection_failed?

If you see data_inspection_failed, refer to Troubleshooting data inspection errors.

​

Product features

​

Can I mix Token Plan, Coding Plan, and pay-as-you-go keys?

No. The API keys and base URLs for Token Plan, Coding Plan, and Qwen Cloud pay-as-you-go are not interchangeable. Do not mix them. Using an incorrect API key will not deduct credits from your Token Plan quota.

​

Can I use one subscription across multiple tools?

Yes. You can use the same API key in all compatible AI tools, and all usage draws from the same quota.

​

Are there usage restrictions?

The service is for interactive use in compatible AI programming and agent tools only. It cannot be used for automated scripts or application backends. Violating these terms may result in subscription suspension or revocation of your API key.

​

Are the models full-featured or quantized?

All supported models in Token Plan are full-featured, unquantized versions.

​

How do I reset or manage my API key?

Use the Reset button on the API Keys page to reset your key. Keep these rules in mind:

• After reset, update the key in all tools
• If you resubscribe after expiration, the key changes
• Token Plan supports one key per subscription

​

Billing and quota

​

How are credits deducted?

Credit consumption is calculated based on the input, cached, and output tokens in each request. The system first deducts credits from your seat quota. After the seat quota is depleted, credits are deducted from the shared usage package. If all credits are used, the service is suspended until the next billing cycle or until you purchase a shared usage package to add more credits.

​

What happens when my quota runs out?

Once your seat quota is depleted, the system automatically begins deducting from the shared usage package. If you run out of credits entirely, the service is suspended. You can resume the service in one of the following ways:

• Upgrade to a higher-tier plan
• Purchase a shared usage package to add more credits
• Wait for your quota to automatically reset at the start of the next billing cycle

There is no automatic fallback to pay-as-you-go when credits are exhausted.

​

When do my credits reset?

The seat quota resets at the end of each subscription month. Unused credits do not roll over to the next month. Similarly, unused credits in the shared usage package expire at the end of each billing cycle.

​

How can I view my usage?

Check the Token Plan page for overall usage, including seat quota and shared usage package details.

​

Can I buy multiple subscriptions?

No. Each Qwen Cloud account is limited to one Token Plan subscription.

​

Can I get a refund?

No. Token Plan does not support refunds. Please review the Usage rules for details before you subscribe.

​

Does an overdue account balance affect my plan?

Token Plan is a prepaid subscription product. As long as your plan's credits are not depleted and the subscription is still valid, an overdue balance on your Qwen Cloud account will not affect your use of the service.

​

Can multiple people share one key?

No. Token Plan API keys are for the subscriber's personal use only. Public exposure or account sharing may result in automatic key suspension.

​

Data security

​

How is my data protected?

Token Plan does not use your conversation data for model training.