Automates complex research through planning, multiple rounds of web searches, and structured report generation. Gathers and synthesizes information without manual effort.
This document applies only to the Chinese mainland (Beijing) region. To use the model, use an API key from the Chinese mainland (Beijing) region.
Getting started
Obtain an API key and export the API key as an environment variable. If you use an SDK to make calls, install the DashScope SDK.
The model uses a two-step workflow: a follow-up question step (the model clarifies your research scope) and a deep research step (the model searches, analyzes, and generates a report). The follow-up question lets the model understand exactly what to investigate before starting a lengthy research run.
Currently, the model does not support DashScope SDK for Java or OpenAI-compatible API calls.
Specifications
Model | Context window (tokens) | Max input (tokens) | Max output (tokens) |
|---|---|---|---|
qwen-deep-research | 1,000,000 | 997,952 | 32,768 |
qwen-deep-research-2025-12-15 |
qwen-deep-research: mainline model, continuously updated. qwen-deep-research-2025-12-15: snapshot version with improved depth, quality, and MCP tool calling. Both support image input and are billed separately.Core capabilities
Track progress via phase (current task) and status (task progress).
Follow-up question and report generation (phase: "answer")
Analyzes your query, asks clarifying questions to define the scope, and generates the final research report.
Status values:
typing: Generating text contentfinished: Text content generation completed
typing: Generating the research planfinished: Research plan completed
WebResultFinished signals the end of each round. finished signals the end of the phase.
Status values:
streamingThinking: Decomposing research tasks and summarizing web content (specific toqwen-deep-research-2025-12-15, replacesstreamingQueriesandstreamingWebResult)streamingQueries: Generating search queries (forqwen-deep-researchonly)streamingWebResult: Performing web searches and analyzing web content (forqwen-deep-researchonly)WebResultFinished: Search round completedfinished: Web search phase completed
Image input
Both models support image input. The model analyzes the image and incorporates that content into its research. Use array format for the content field, passing image and text objects together.
- Supported formats: JPEG, PNG, BMP, WEBP. Maximum 10 MB per image.
- Up to 5 images per request. Supports public URLs and Base64 encoding.
- The response format is identical to text-only requests. The model generates a report based on the image content.
MCP tool calling
MCP tool calling is only supported by
qwen-deep-research-2025-12-15. qwen-deep-research does not support this feature.qwen-deep-research-2025-12-15 pull from private or domain-specific data sources during the WebResearch phase—such as a knowledge base, internal documents, or a proprietary database—alongside standard web searches. Pass MCP server configuration through the research_tools parameter. The response format is identical to standard calls.
For details about research_tools and MCP tool specifications, see Qwen-Deep-Research .
Request example
Billing
Model | Input cost (per 1K tokens) | Output cost (per 1K tokens) | Free quota |
|---|---|---|---|
qwen-deep-research | $0.007742 | $0.023367 | No free quota |
qwen-deep-research-2025-12-15 | To be determined | To be determined | No free quota |
Going live
Use streaming output
The model only supports streaming output (stream=True). A single research task can run for several minutes across dozens of iterative search-and-read cycles, which exceeds the timeout of a synchronous request. Use streaming to keep the connection open and track progress via phase and status fields.
Handle errors
Check the response status code on each chunk. For non-200 status codes, read the code and message fields and handle them appropriately.
Monitor token usage
When status is finished, retrieve token usage from response.usage (input tokens, output tokens, and request ID).
Handle connection keepalive
The KeepAlive phase maintains the connection between long-running tasks. Ignore this phase and continue processing the stream.
FAQ
- Why is the output field empty for some response chunks? Early chunks carry metadata only. Content arrives in subsequent chunks as the model generates it.
-
How do I determine if a phase is complete?
A phase completes when
statuschanges tofinished. - Does the model support OpenAI-compatible API calls? No. OpenAI-compatible API calls are not supported.
- How are input and output tokens calculated? Input tokens: user messages and system prompts. Output tokens: follow-up questions, research plans, goals, search queries, and the final report.
-
What is the difference between qwen-deep-research and qwen-deep-research-2025-12-15?
qwen-deep-research: mainline model, continuously updated.qwen-deep-research-2025-12-15: snapshot version with improved depth, quality, and MCP support. Both support image input and are billed separately. -
How do I pass images for research?
Use array format for
content: pass{"image": "URL"}and{"text": "description"}as objects in the array. Both models support image input. -
How do I skip the follow-up question and go straight to research?
Set
enable_feedbacktofalseinparameters. The model skips the follow-up question and starts research immediately.