Qwen-Coder is a language model designed for code tasks. You can use the API to generate code, complete code, and call tools to interact with external systems.
推荐使用最新的通用模型替代 Qwen-Coder 模型,请参见Text Generation选择适合您场景的模型。
Quick Start
API 使用前提:已获取与配置 API Key并完成配置API Key到环境变量。如果通过SDK调用,需要安装 OpenAI 或 DashScope SDK
The following example will demonstrate how to callqwen-coder-plus-latestthe Model to write a Python function that finds prime numbers.
- OpenAI兼容-Chat Completions API
- DashScope
- Python
- Node.js
- curl
Request ExampleResponse
Core Capabilities
Calling Tools
To enable the Model to interact with the external environment (for example, reading and writing files, calling APIs, and operating databases), you can provide it with a series of tools. The Model decides whether and how to call these tools based on your instructions. For details, see Function Calling。
The complete tool calling workflow includes:
- Define tools and initiate a request: Define the tool list in the request, and present to the model the task that needs to be completed using tools.
- Execute tools: Parse what the model returns
tool_calls, and call the corresponding tool function you have implemented locally to execute the task. - Return execution result: Package the tool's execution result into a specific format and send it back to the model, allowing it to complete the final task based on the result.
write_file tool to save it to a local file.
- OpenAI兼容-Chat Completions API
- DashScope
- Python
- Node.js
- curl
Code generation
Qwen-Coder supports two code completion methods. Please choose based on your needs:
- Prefix Continuation (Partial Mode): Applicable to all Qwen-Coder models and regions, supports prefix completion, simple to implement, recommended.
- Completions API: Only supports North China 2 (Beijing)
qwen-coder-turbo-latestmodels. Supports prefix completion and prefix-suffix completion.
Prefix Continuation (Partial Mode)
This feature lets the model automatically complete the remaining part based on the code (prefix) you have half-written.
By messages list, adding one role 为 assistant 的消息,并设置 partial: true 来实现。assistant 消息的 content 即为您提供的代码前缀。详情请参见Prefix Continuation。
- OpenAI兼容
- DashScope
- Python
- Node.js
- curl
请求示例Response
Completions API
Supported Models:
qwen-coder-turbo-latest
Completions APIPass in prompt Use special fim (Fill-in-the-Middle) tags to guide the Model to perform completion.
- 基于前缀补全
- 基于前缀和后缀补全
Prompt template:
<|fim_prefix|>and<|fim_suffix|>are special Tokens, used to guide the Model to perform text completion, no modification needed.{prefix_content}Need to be replaced with the input prefix information, such as function name, Input Parameters, Use Description, and other information.
Applied to Production Environment
To optimize the usage efficiency of the Qwen code Model and reduce costs, refer to the following suggestions:
- EnableStream: Settings
stream=Truecan return intermediate results in real time, reducing timeout risks and improving user experience. - Lower the temperature parameter: Code generation tasks usually require deterministic and accurate results. It is recommended to lower the
temperatureparameter to reduce the randomness of the generated results. - Use a model that supports context caching: In scenarios with a large amount of repeated prefixes (such as code completion, code review), it is recommended to use a model that supportsContext Cache model to effectively reduce costs.
- Control tool count: To ensure the efficiency and cost-effectiveness of model calls, it is recommended that the tools passed in a single call
toolsnot exceed 20. Passing a large number of tool descriptions consumes excessive input tokens, which not only increases costs and slows response speed, but also makes it harder for the model to select the correct tool. For details, seeFunction Calling。
Billing and Rate Limiting
-
Basic Billing: Billed based on the input
Tokencount and outputTokencount of each request. Different models have different unit prices; for specific prices, please refer to Models。 -
Special Billing Items:
- Tiered Pricing:
qwen3-coderseries models adopt tiered pricing. When singleAfter the request's input Token count reaches a specific tier, all input and output Tokens of that request are billed at the unit price of this tier. - Context Cache: For models that support context caching, when multiple requests contain large amounts of repeated input (such as code review), the cache mechanism can significantly reduce costs. HitImplicit Cache of input text is billed at 20% of the unit price, hitExplicit Cache of input text is billed at 10% of the unit price. For details, seeContext Cache。
- Built-in Tools (Function Calling): When using the Built-in Tools feature, you are in
toolsThe tool description defined in the Parameter is counted as input content intoTokentotal and incurs fees.
- Tiered Pricing:
- Rate Limit:API Calling is subject to dual limits of requests per minute (RPM) and Tokens per minute (TPM). For details, seeRate Limit。
- Free Quota (Beijing region only) (Singapore region only):The Validity is calculated from the date of activating Bailian or Model application Pass; within the 90-day Validity, each Qwen-Coder Model provides 1 million Tokens respectivelynew user Free Quota。
API Reference
For the Input Parameters and output parameters of the Qwen Code Model, seeText Generation。
FAQ
Why does using development tools like Qwen Code, Claude Code, etc. consume a large amount of Token?
When calling the Qwen-Coder model through external development tools to handle problems, the tool may call the API multiple times, thereby consuming a large amount of Token. For specific methods on monitoring and reducing Token consumption, please refer toQwen Code and Claude CodeDocs. You can enableFree Quota Onlyfunction to avoid additional costs after the free quota is exhausted.
You can also purchase an AI coding plan, adopting a fixed monthly fee, providing monthly request quota, supporting use in AI tools. For details, please refer toCoding Plan Overview。
How to view model call volume?
After a model call occursminute-levelyou can view it in monitoring charts. Log in to Monitoring page (BeijingOrSingapore), select from the left navigation barOperations Management > MonitoringEnter the monitoring overview page, set the query conditions (for example, select the time range, workspace, etc.), then in the Modelsarea, locate the target model and click View Details to view the calling statistics results of the model. For details, see the Monitoring & Alerts docs.
Monitoring data is updated at the minute level and is for reference only, not for billing purposes.
How to make the model output only code without any explanatory text?
You can refer to the following methods:
- Prompt Constraints: Clearly instruct in the prompt, for example: "Only return code, do not include any explanations, comments, or markdown markers."
- Settings
stopsequence: Usestop=["\n# 解释:", "说明", "Explanation:", "Note:"]etc. phrases to early-terminate when the Model begins generating explanatory text; for details, see Qwen API Reference。