Requesty
Sign in

identity

open weights
Alibaba (Qwen) logo

qwen3.7-plusAlibaba (Qwen)

from /1M in$0.32alibaba cloud
context1.0M262K out
providers21 region
price spread1.3x2 endpoints
endpoints
2
regions
1
api
chat
released
June 2026

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 1.3x more on fireworks ai than on alibaba cloud. That is what the endpoints table is for.

endpoints

2 / 1 region
Providers serving qwen3.7-plus, with pricing and measured performance. Best value in each column is coloured.
#flags
1Alibaba CloudGlobal1.0M$0.32$1.28$0.03zdr
2Fireworks AIGlobal262K$0.40$1.60$0.08zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
τ²-Bench93.0
GPQA Diamond90.0
Coding Index55.9
Terminal-Bench Hard47.0
SciCode46.1
Humanity's Last Exam35.6
Intelligence Index25.8
7 evalsmean56.2

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-06-01.

call it

model=
qwen3.7-plus

requesty routes this id across every provider serving qwen3.7-plus, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
from openai import OpenAI client = OpenAI(    api_key="YOUR_REQUESTY_API_KEY",    base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create(    model="qwen3.7-plus",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

Qwen3.7-Plus is a cost-effective model in Alibaba's Qwen3.7 series. It supports text and image input with text output, building on the series' text capabilities with a comprehensive upgrade to its vision-language abilities while retaining full-stack, agent-level intelligence for coding, tool use, and productivity workflows. Its distinguishing trait is multi-modal interactive hybrid agent capability: it can perceive real-world scenes, read screens and interact with GUIs, generate code from visual references, and perform end-to-end navigation within mobile apps.

questions 6

Which providers serve qwen3.7-plus?
qwen3.7-plus is available from 2 providers through Requesty: Alibaba Cloud, Fireworks AI. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does qwen3.7-plus cost?
Pricing starts at $0.32 per million input tokens and $1.28 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is qwen3.7-plus open weights?
Yes. qwen3.7-plus is an open-weights model from Alibaba (Qwen), which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of qwen3.7-plus?
qwen3.7-plus supports up to 1.0M tokens of context, with up to 262K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use qwen3.7-plus with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "qwen3.7-plus" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call qwen3.7-plus by its managed id or a provider id?
Use the managed id, "qwen3.7-plus". Requesty picks which of the 2 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "alibaba/qwen3.7-plus" only when you need one specific deployment and want no failover.

more from alibaba (qwen) 6

Other Alibaba (Qwen) models
modelcontextfrom /Mproviders
qwen3.8-2.4t-a95b1M$2.501
qwen3.8-flash-next262K$0.201
qwen3.8-flash1.0M$0.161
qwen3.8-max1.0M$2.003
qwen3.7-max1.0M$2.501
qwen3.6-plus1M$0.501

route qwen3.7-plus through one endpoint

One key for 2 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

qwen3.7-plus2 providers2 endpointsfrom $0.32 /1M inctx 1.0Mspread 1.3xupdated Sep 12