Free to start

Qwen: Qwen3.8 2.4T A95B vs Tencent: Hy3

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

$5.275/1MQwen: Qwen3.8 2.4T A95B cheapest route

$0.6963/1MTencent: Hy3 cheapest route

1535 msQwen: Qwen3.8 2.4T A95B fastest measured p50 TTFT via lyceum

2249 msTencent: Hy3 fastest measured p50 TTFT via tencent

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.8 2.4T A95BTencent: Hy3

Model idqwen/qwen3.8-2.4t-a95btencent/hy3

Publisher Alibaba Cloud Model Studio Tencent Cloud TokenHub

AI IQ IQ 123#32 IQ 99#128

Context1,000,000 tokens262,144 tokens

Credits provider routes64

Cheapest route$5.275/1M$0.6963/1M

Cached input$0.26375/1M to $0.66465/1M$0.034815/1M to $0.05275/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFT1535 ms via lyceum2249 ms via tencent

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

Qwen: Qwen3.8 2.4T A95B routes

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

Tencent: Hy3 routes

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

Related comparisons

Browse every comparison

Qwen: Qwen3.8 2.4T A95B vs Z.ai: GLM 5.339 combined provider routes
Qwen: Qwen3.8 2.4T A95B vs Z.ai: GLM 5.238 combined provider routes
Qwen: Qwen3.8 2.4T A95B vs Z.ai: GLM 5.3 Flash38 combined provider routes
Tencent: Hy3 vs Z.ai: GLM 5.337 combined provider routes
Tencent: Hy3 vs Z.ai: GLM 5.236 combined provider routes
Tencent: Hy3 vs Z.ai: GLM 5.3 Flash36 combined provider routes
MoonshotAI: Kimi K3 vs Qwen: Qwen3.8 2.4T A95B34 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen: Qwen3.8 2.4T A95B32 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.8-2.4t-a95b",
    messages=messages,
)

Questions

Which should I use, Qwen: Qwen3.8 2.4T A95B or Tencent: Hy3?

Qwen: Qwen3.8 2.4T A95B has more Credits provider routes, the larger context window and the lower measured p50 time to first token. Tencent: Hy3 has the lower published input-plus-output rate.

Is Qwen: Qwen3.8 2.4T A95B or Tencent: Hy3 cheaper?

The current cheapest TrustedRouter route is $5.275/1M for Qwen: Qwen3.8 2.4T A95B and $0.6963/1M for Tencent: Hy3. The comparison uses current catalog prices and updates as provider pricing changes.

Is Qwen: Qwen3.8 2.4T A95B or Tencent: Hy3 faster?

Current measured p50 time to first token is 1535 ms for Qwen: Qwen3.8 2.4T A95B and 2249 ms for Tencent: Hy3. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Qwen: Qwen3.8 2.4T A95B and Tencent: Hy3 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.8-2.4t-a95b and tencent/hy3. This makes side-by-side evals possible without maintaining two provider integrations.