Free to start

Qwen: Qwen3.5-122B-A10B vs Tencent: Hy4 preview

Try both on us. Starter credit covers your first requests, then one key routes Qwen3.5-122B-A10B 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-122B-A10B has the lower published input-plus-output rate and more Credits provider routes. Tencent: Hy4 preview has the larger context window. There is not enough recent probe data to compare speed.

$2.4687/1MQwen: Qwen3.5-122B-A10B cheapest route

$3.518425/1MTencent: Hy4 preview cheapest route

not enough dataQwen: Qwen3.5-122B-A10B fastest measured p50 TTFT

not enough dataTencent: Hy4 preview fastest measured p50 TTFT

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-122B-A10BTencent: Hy4 preview

Model idqwen/qwen3.5-122b-a10btencent/hy4-preview

Publisher Alibaba Cloud Model Studio Tencent Cloud TokenHub

AI IQ — IQ 113#63

Context262,144 tokens1,000,000 tokens

Credits provider routes64

Cheapest route$2.4687/1M$3.518425/1M

Cached input$0.0422/1M to $0.3165/1M$0.04431/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFTnot enough datanot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough datanot enough data

Modes chat chat

Qwen: Qwen3.5-122B-A10B routes

Overview6 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-122B-A10B vs Z.ai: GLM 5.339 combined provider routes
Qwen: Qwen3.5-122B-A10B vs Z.ai: GLM 5.238 combined provider routes
Qwen: Qwen3.5-122B-A10B vs Z.ai: GLM 5.3 Flash38 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-122B-A10B34 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen: Qwen3.5-122B-A10B32 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-azure.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="qwen/qwen3.5-122b-a10b",
    messages=messages,
)

Questions

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

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

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

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

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