Real data comparison
DeepSeek: DeepSeek V4 Flash 0423 vs Tencent: Hy4 preview
On price, DeepSeek: DeepSeek V4 Flash 0423 is cheaper ($0.66 vs $1.25 per 1M). In real production usage, DeepSeek: DeepSeek V4 Flash 0423 is used more (rank #4 vs #7 of 388). Across 6 real task categories where both models have classified traffic, DeepSeek: DeepSeek V4 Flash 0423 handles more of the traffic in 5 of them.
- DeepSeek: DeepSeek V4 Flash 0423
- Tencent: Hy4 preview
Head-to-head by real task
DeepSeek: DeepSeek V4 Flash 0423 leads 5 of 6 shared task categories by real classified traffic share; Tencent: Hy4 preview leads 1. Not a benchmark score - this is what developers actually route to each model for, per OpenRouter's task classification.
| Task | DeepSeek: DeepSeek V4 Flash 0423 | Tencent: Hy4 preview |
|---|---|---|
| Conversation | 13.9% | 1.6% |
| Research & Reports | 11.4% | 5.8% |
| DevOps | 5.6% | 3.0% |
| SQL & Database | 5.0% | 2.4% |
| Workflow Execution | 2.3% | 4.8% |
| Multi-step Planning | 4.3% | 2.2% |
Usage share over time
- DeepSeek: DeepSeek V4 Flash 0423
- Tencent: Hy4 preview
Frequently asked questions
DeepSeek: DeepSeek V4 Flash 0423 vs Tencent: Hy4 preview: which is better quality?
Quality data is unavailable for one or both models.
DeepSeek: DeepSeek V4 Flash 0423 vs Tencent: Hy4 preview: which is cheaper?
DeepSeek: DeepSeek V4 Flash 0423 is cheaper at $0.66/1M vs $1.25/1M.
DeepSeek: DeepSeek V4 Flash 0423 vs Tencent: Hy4 preview: which is used more?
DeepSeek: DeepSeek V4 Flash 0423 has higher real OpenRouter usage share (rank #4 vs #7 of 388).
DeepSeek: DeepSeek V4 Flash 0423 vs Tencent: Hy4 preview: which wins more real-world task categories?
DeepSeek: DeepSeek V4 Flash 0423 handles more traffic in 5 of 6 shared task categories where both models have classified OpenRouter usage.
Source: OpenRouter (openrouter.ai/rankings), as of October 21, 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.
