Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Qwen3.6 Max Preview - Model - OpenSmartRoute
Modelv1.0.0
Qwen3.6 Max Preview
Qwen3.6-Max-Preview is a proprietary frontier model from Alibaba Cloud built on a sparse mixture-of-experts architecture with approximately 1 trillion total parameters.
Reference model card from the OpenRouter listing - model qwen/qwen3.6-max-preview. Prices are per million tokens as listed; ratings and installs below are from this marketplace.
Qwen3.6 Max Preview
Qwen3.6-Max-Preview is a proprietary frontier model from Alibaba Cloud built on a sparse mixture-of-experts architecture with approximately 1 trillion total parameters. It is optimized for agentic coding, tool use, and...
Facts
Vendor
Qwen
Context window
262,144 tokens
Max output
65,536 tokens
Input price
$1.03 / 1M tokens
Output price
$6.16 / 1M tokens
Input
text
Output
text
Tool calling
yes
Structured outputs
yes
Reasoning
yes
Open weights
no
Endpoint: https://openrouter.ai/api/v1 (OpenAI-compatible), model qwen/qwen3.6-max-preview
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "model-qwen-qwen3-6-max-preview", ...}
Installed into a catalogue, chosen by a router
Install Qwen3.6 Max Preview and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
