SmophyAI

Published daily · Next update 02:00 UTC

Real data comparison

Z.ai: GLM 5.3 Flash (batch) vs Tencent: Hy3

On price, Z.ai: GLM 5.3 Flash (batch) is cheaper ($0.12 vs $0.23 per 1M). In real production usage, Tencent: Hy3 is used more (rank #4 vs #5 of 325). Across 4 real task categories where both models have classified traffic, Z.ai: GLM 5.3 Flash (batch) handles more of the traffic in 4 of them.

  • Z.ai: GLM 5.3 Flash (batch)
  • Tencent: Hy3
Price ($/1M blended)$0.12 / $0.23
Average usage share9.80% / 9.96%
Best provider uptime100.0% / 100.0%
Context window1,310,720 / 262,144

Head-to-head by real task

Z.ai: GLM 5.3 Flash (batch) leads 4 of 4 shared task categories by real classified traffic share; Tencent: Hy3 leads 0. Not a benchmark score - this is what developers actually route to each model for, per OpenRouter's task classification.

TaskZ.ai: GLM 5.3 Flash (batch)Tencent: Hy3
Research & Reports14.5%2.1%
Multi-step Planning11.6%2.0%
Workflow Execution10.6%4.1%
File I/O10.1%4.5%

Usage share over time

22.45%16.84%11.23%5.61%0.00%Share of usageJul 6Aug 7Sep 8
  • Z.ai: GLM 5.3 Flash (batch)
  • Tencent: Hy3

Frequently asked questions

Z.ai: GLM 5.3 Flash (batch) vs Tencent: Hy3: which is better quality?

Quality data is unavailable for one or both models.

Z.ai: GLM 5.3 Flash (batch) vs Tencent: Hy3: which is cheaper?

Z.ai: GLM 5.3 Flash (batch) is cheaper at $0.12/1M vs $0.23/1M.

Z.ai: GLM 5.3 Flash (batch) vs Tencent: Hy3: which is used more?

Tencent: Hy3 has higher real OpenRouter usage share (rank #4 vs #5 of 325).

Z.ai: GLM 5.3 Flash (batch) vs Tencent: Hy3: which wins more real-world task categories?

Z.ai: GLM 5.3 Flash (batch) handles more traffic in 4 of 4 shared task categories where both models have classified OpenRouter usage.

Source: OpenRouter (openrouter.ai/rankings), as of September 9, 2026.

Benchmark scores: Artificial Analysis (artificialanalysis.ai) via OpenRouter (openrouter.ai/rankings).

Methodology: www.smophy.ai/benchmark/methodology

Token counts originate from each provider's own tokenizer and are not directly comparable across providers.