Real data comparison
DeepSeek: DeepSeek V4.1 Flash (batch) vs Tencent: Hy3
On price, DeepSeek: DeepSeek V4.1 Flash (batch) is cheaper ($0.20 vs $0.23 per 1M). In real production usage, DeepSeek: DeepSeek V4.1 Flash (batch) is used more (rank #4 vs #7 of 353). Across 5 real task categories where both models have classified traffic, DeepSeek: DeepSeek V4.1 Flash (batch) handles more of the traffic in 5 of them.
- DeepSeek: DeepSeek V4.1 Flash (batch)
- Tencent: Hy3
Head-to-head by real task
DeepSeek: DeepSeek V4.1 Flash (batch) leads 5 of 5 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.
| Task | DeepSeek: DeepSeek V4.1 Flash (batch) | Tencent: Hy3 |
|---|---|---|
| Multi-step Planning | 11.4% | 1.9% |
| File I/O | 14.9% | 5.7% |
| Tool Dispatch | 9.1% | 1.6% |
| Research & Reports | 9.4% | 2.1% |
| Workflow Execution | 10.2% | 4.4% |
Usage share over time
- DeepSeek: DeepSeek V4.1 Flash (batch)
- Tencent: Hy3
Frequently asked questions
DeepSeek: DeepSeek V4.1 Flash (batch) vs Tencent: Hy3: which is better quality?
Quality data is unavailable for one or both models.
DeepSeek: DeepSeek V4.1 Flash (batch) vs Tencent: Hy3: which is cheaper?
DeepSeek: DeepSeek V4.1 Flash (batch) is cheaper at $0.20/1M vs $0.23/1M.
DeepSeek: DeepSeek V4.1 Flash (batch) vs Tencent: Hy3: which is used more?
DeepSeek: DeepSeek V4.1 Flash (batch) has higher real OpenRouter usage share (rank #4 vs #7 of 353).
DeepSeek: DeepSeek V4.1 Flash (batch) vs Tencent: Hy3: which wins more real-world task categories?
DeepSeek: DeepSeek V4.1 Flash (batch) handles more traffic in 5 of 5 shared task categories where both models have classified OpenRouter usage.
Source: OpenRouter (openrouter.ai/rankings), as of September 23, 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.