Free to start

Qwen: Qwen3.5-9B vs Tencent: Hy4 preview

Try both on us. Starter credit covers your first requests, then one key routes Qwen3.5-9B 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-9B has the lower published input-plus-output rate, more Credits provider routes and the lower measured p50 time to first token. Tencent: Hy4 preview has the larger context window.

$0.110775/1MQwen: Qwen3.5-9B cheapest route

$3.518425/1MTencent: Hy4 preview cheapest route

1413 msQwen: Qwen3.5-9B fastest measured p50 TTFT via regolo

2149 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-9BTencent: Hy4 preview

Model idqwen/qwen3.5-9btencent/hy4-preview

Publisher Alibaba Cloud Model Studio Tencent Cloud TokenHub

AI IQ IQ 96#139 IQ 113#63

Context262,144 tokens1,000,000 tokens

Credits provider routes74

Cheapest route$0.110775/1M$3.518425/1M

Cached input$0.0211/1M$0.04431/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFT1413 ms via regolo2149 ms via gmi

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

Qwen: Qwen3.5-9B routes

Overview7 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-9B vs Z.ai: GLM 5.340 combined provider routes
Qwen: Qwen3.5-9B vs Z.ai: GLM 5.239 combined provider routes
Qwen: Qwen3.5-9B vs Z.ai: GLM 5.3 Flash39 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
MoonshotAI: Kimi K3 vs Qwen: Qwen3.5-9B35 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen: Qwen3.5-9B33 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-9b",
    messages=messages,
)

Questions

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

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

Is Qwen: Qwen3.5-9B or Tencent: Hy4 preview cheaper?

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

Is Qwen: Qwen3.5-9B or Tencent: Hy4 preview faster?

Current measured p50 time to first token is 1413 ms for Qwen: Qwen3.5-9B and 2149 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-9B 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-9b and tencent/hy4-preview. This makes side-by-side evals possible without maintaining two provider integrations.