Free to start

Qwen: Qwen3.5 397B A17B vs Tencent: Hy4 preview

Try both on us. Starter credit covers your first requests, then one key routes Qwen3.5 397B A17B and Hy4 preview. Switch by changing the model name.

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

Qwen: Qwen3.5 397B A17B has more Credits provider routes and the lower measured p50 time to first token. Tencent: Hy4 preview has the lower published input-plus-output rate and the larger context window.

$3.63975/1MQwen: Qwen3.5 397B A17B cheapest route

$3.518425/1MTencent: Hy4 preview cheapest route

1649 msQwen: Qwen3.5 397B A17B fastest measured p50 TTFT via scaleway

3177 msTencent: Hy4 preview fastest measured p50 TTFT via gmi

The price comparison adds each route's rate for one million input tokens and one million output tokens; your cost depends on your input/output mix. 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.

Qwen: Qwen3.5 397B A17BTencent: Hy4 preview

Model idqwen/qwen3.5-397b-a17btencent/hy4-preview

Publisher Alibaba Cloud Model Studio Tencent Cloud TokenHub

AI IQ — IQ 113#63

Context262,144 tokens1,000,000 tokens

Credits provider routes114

Cheapest route$3.63975/1M$3.518425/1M

Cached input$0.047475/1M to $0.58025/1M$0.04431/1M

Privacy posturehas Confidential route (E2EE + ZDR)provider posture varies

Fastest measured p50 TTFT1649 ms via scaleway3177 ms via gmi

Highest measured throughputnot enough datanot enough data

Recent route uptime range0.00% to 100.00%100.00%

Modes chat chat

Qwen: Qwen3.5 397B A17B routes

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

Tencent: Hy4 preview routes

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

Related comparisons

Browse every comparison

Qwen: Qwen3.5 397B A17B vs Z.ai: GLM 5.344 combined provider routes
Qwen: Qwen3.5 397B A17B vs Z.ai: GLM 5.243 combined provider routes
Qwen: Qwen3.5 397B A17B vs Z.ai: GLM 5.3 Flash43 combined provider routes
MoonshotAI: Kimi K3 vs Qwen: Qwen3.5 397B A17B39 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen: Qwen3.5 397B A17B37 combined provider routes
Tencent: Hy4 preview vs Z.ai: GLM 5.337 combined provider routes
Tencent: Hy4 preview vs Z.ai: GLM 5.236 combined provider routes
Tencent: Hy4 preview vs Z.ai: GLM 5.3 Flash36 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.5-397b-a17b",
    messages=messages,
)

Questions

Which should I use, Qwen: Qwen3.5 397B A17B or Tencent: Hy4 preview?

Is Qwen: Qwen3.5 397B A17B or Tencent: Hy4 preview cheaper?

The current cheapest TrustedRouter route is $3.63975/1M for Qwen: Qwen3.5 397B A17B and $3.518425/1M for Tencent: Hy4 preview. The comparison uses current catalog prices and updates as provider pricing changes.

Is Qwen: Qwen3.5 397B A17B or Tencent: Hy4 preview faster?

Current measured p50 time to first token is 1649 ms for Qwen: Qwen3.5 397B A17B and 3177 ms for Tencent: Hy4 preview. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Qwen: Qwen3.5 397B A17B and Tencent: Hy4 preview 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.5-397b-a17b and tencent/hy4-preview. This makes side-by-side evals possible without maintaining two provider integrations.