Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Confirm provider modelName and limits/pricing with DashScope docs
“qwen3-max-preview” may be a temporary alias; prices/limits can change. Please validate before merge.
🌐 Web query:
💡 Result:
Short answers:
Model identifier: Alibaba/DashScope uses qwen-max (not “qwen3-max”) for the Qwen-Max family; Qwen3 commercial models use names like qwen-plus, qwen3-coder-plus, qwen3-235b-... (see official models list). [1]
The prices you listed (input $3/M, output $15/M, cached input $0.6/M) match a tier in the qwen3-coder-plus tiered pricing (the 128K–256K and 256K–1M tiers shown in the qwen3-coder pricing tables), but those prices are for qwen3-coder-plus variants (tiered pricing) — they are not the published qwen-max prices. Check the qwen3-coder-plus pricing table in the official docs for exact tiered rows. [2]
Limits: the official docs show different context/output limits per model:
Your stated values (256k context, 32.8k max output) do not match the published qwen-max or qwen3-coder-plus rows; they match some Qwen3 snapshot/variants but are not the canonical qwen-max numbers. [1][2]
Capabilities: Qwen3 family supports reasoning modes (thinking/deep-thinking), vision (VL) variants, and strong tool-calling / agent capabilities (Qwen3-Coder and Qwen-Agent are explicitly described for tool-calling). Whether a particular model supports vision or tool-calling depends on the specific model variant (e.g., Qwen-VL models for vision; qwen3-coder-plus for agent/tool use). [1][3]
Parameter reasoning_output="omit": I could not find any official DashScope / Model Studio parameter named reasoning_output="omit". The Qwen3/docs reference parameters such as enable_thinking, incremental_output, result_format and streaming fields (and a separate reasoning_content field in streamed responses), but not a reasoning_output="omit" parameter. So that parameter is not documented / not supported in the official docs. [3][4]
Official documentation / pricing pages (canonical references):
If you want, tell me which exact model/endpoint you plan to call (qwen-max, qwen-plus, qwen3-coder-plus, etc.) and I’ll extract the exact model string and the precise pricing/limits row for that model version.
Citations:
Align modelName and specs with official DashScope docs
"qwen-max"for Qwen-Max) instead of"qwen3-max-preview".inputPrice,outputPrice,cachedInputPrice) and limits (contextSize,maxOutput) to match the published Alibaba Cloud Models & pricing and Qwen-Coder tables.reasoningOutput: "omit"and adopt documented parameters (enable_thinking,streaming, etc.).