OpenAI compatible API · Attested · Public status

Qwen3 235B A22B Instruct 2507 vs Qwen3.7 Max

Qwen3 235B A22B Instruct 2507 vs Qwen3.7 Max: compare current API pricing, context, provider routes, privacy, p50 latency, and OpenAI-compatible access.

Verify gateway

Onebase URL to migrate

100sof models and routes

0prompt or output logs. Always.

Compare routesProviders, price, context, and policy posture in one view.

Use auto when uptime mattersKeep a primary model and let fallback handle provider failures.

Same API shapeUse the OpenAI client and set the model you want.

Practical read

Monthly evidence

Qwen3 235B A22B Instruct 2507 has the lower cheapest prompt+completion route on TrustedRouter. Qwen3 235B A22B Instruct 2507 has more provider fallback routes, while Qwen3.7 Max has the larger context window. Current TrustedRouter probes show Qwen3 235B A22B Instruct 2507 with the lower p50 TTFT.

$0.6752/1MQwen3 235B A22B Instruct 2507 cheapest route

$5.275/1MQwen3.7 Max cheapest route

2924 msQwen3 235B A22B Instruct 2507 fastest measured p50 TTFT via scaleway

3597 msQwen3.7 Max fastest measured p50 TTFT via atlas-cloud

Prices and live route measurements can change. Use the monthly reports when you need a stable evidence window, then run a small task-specific eval before choosing a production default.

Qwen3 235B A22B Instruct 2507Qwen3.7 Max

Model idqwen/qwen3-235b-a22b-instruct-2507qwen/qwen3.7-max

Publisher Novita AI Novita AI

AI IQ — IQ 119#31

Context131,072 tokens1,000,000 tokens

Credits provider routes64

Cheapest route$0.6752/1M$5.275/1M

Cached input$0.024265/1M$0.26375/1M to $0.5275/1M

Privacy postureprovider posture variesprovider posture varies

Fastest measured p50 TTFT2924 ms via scaleway3597 ms via atlas-cloud

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

Qwen3 235B A22B Instruct 2507 routes

Overview6 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Qwen3.7 Max routes

Overview4 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Related comparisons

Browse every comparison

Qwen3 235B A22B Instruct 2507 vs Z.ai: GLM 5.234 combined provider routes
Qwen3 235B A22B Instruct 2507 vs Z.ai: GLM 5.333 combined provider routes
Qwen3 235B A22B Instruct 2507 vs Z.ai: GLM 5.3 Flash32 combined provider routes
Qwen3.7 Max vs Z.ai: GLM 5.232 combined provider routes
Qwen3.7 Max vs Z.ai: GLM 5.331 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen3 235B A22B Instruct 250730 combined provider routes
MoonshotAI: Kimi K3 vs Qwen3 235B A22B Instruct 250730 combined provider routes
Qwen3.7 Max vs Z.ai: GLM 5.3 Flash30 combined provider routes

Production choice

Pick a default model. Keep fallback enabled.

TrustedRouter is useful when you know the model you want, but still need provider rollover, budget limits, usage records, and a prompt path you can verify.

OpenAI clientPython

client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="qwen/qwen3-235b-a22b-instruct-2507",
    messages=messages,
)

Questions

Which should I use, Qwen3 235B A22B Instruct 2507 or Qwen3.7 Max?

Is Qwen3 235B A22B Instruct 2507 or Qwen3.7 Max cheaper?

The current cheapest TrustedRouter route is $0.6752/1M for Qwen3 235B A22B Instruct 2507 and $5.275/1M for Qwen3.7 Max. The comparison uses current catalog prices and updates as provider pricing changes.

Is Qwen3 235B A22B Instruct 2507 or Qwen3.7 Max faster?

Current measured p50 time to first token is 2924 ms for Qwen3 235B A22B Instruct 2507 and 3597 ms for Qwen3.7 Max. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Qwen3 235B A22B Instruct 2507 and Qwen3.7 Max with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between qwen/qwen3-235b-a22b-instruct-2507 and qwen/qwen3.7-max. This makes side-by-side evals possible without maintaining two provider integrations.