Free to start

Qwen: Qwen3.8 27B vs Tencent: Hy3

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

$0.385075/1MQwen: Qwen3.8 27B cheapest route

$0.6963/1MTencent: Hy3 cheapest route

710 msQwen: Qwen3.8 27B fastest measured p50 TTFT via engy

not enough dataTencent: Hy3 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.8 27BTencent: Hy3

Model idqwen/qwen3.8-27btencent/hy3

Publisher Alibaba Cloud Model Studio Tencent Cloud TokenHub

AI IQ IQ 115#57 IQ 99#133

Context65,536 tokens262,144 tokens

Credits provider routes224

Cheapest route$0.385075/1M$0.6963/1M

Cached input$0.01/1M to $0.19834/1M$0.034815/1M to $0.05275/1M

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

Fastest measured p50 TTFT710 ms via engynot enough data

Highest measured throughput244 tok/s via munanot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

Qwen: Qwen3.8 27B routes

Overview22 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 27B vs Z.ai: GLM 5.355 combined provider routes
Qwen: Qwen3.8 27B vs Z.ai: GLM 5.254 combined provider routes
Qwen: Qwen3.8 27B vs Z.ai: GLM 5.3 Flash54 combined provider routes
MoonshotAI: Kimi K3 vs Qwen: Qwen3.8 27B50 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Qwen: Qwen3.8 27B48 combined provider routes
DeepSeek: DeepSeek V4.1 Flash vs Qwen: Qwen3.8 27B46 combined provider routes
OpenAI: gpt-oss-120b vs Qwen: Qwen3.8 27B46 combined provider routes
MoonshotAI: Kimi K2.6 vs Qwen: Qwen3.8 27B39 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-27b",
    messages=messages,
)

Questions

Which should I use, Qwen: Qwen3.8 27B or Tencent: Hy3?

Qwen: Qwen3.8 27B has the lower published input-plus-output rate and more Credits provider routes. Tencent: Hy3 has the larger context window. There is not enough recent probe data to compare speed.

Is Qwen: Qwen3.8 27B or Tencent: Hy3 cheaper?

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

Is Qwen: Qwen3.8 27B or Tencent: Hy3 faster?

Current measured p50 time to first token is 710 ms for Qwen: Qwen3.8 27B and not enough data for Tencent: Hy3. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Qwen: Qwen3.8 27B 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-27b and tencent/hy3. This makes side-by-side evals possible without maintaining two provider integrations.