Kimi K2.5 vs Hy3
At a Glance
| Compare | Kimi K2.5Moonshot AI | Hy3Tencent |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.45Deepinfra ↗ · Aug 29, 2026 | $0.13Deepinfra ↗ · Sep 22, 2026 |
| Output priceFrom · USD / 1M tokens | $2.25Deepinfra ↗ · Aug 29, 2026 | $0.528Openrouter ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | 262K | 262K |
| Model facts checked | Aug 28, 2026View model evidence → | Aug 28, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
| Benchmark | Kimi-K2.5 | Hy3 |
|---|---|---|
| LMArena Text Arenatext-2026-09-13-d25aabda0010 · arena_rating · statistical tie | 1,445.64100% of row best · rating · kimi-k2.5-thinking; 95% CI [1442.30343195, 1448.97544647]; votes 70513; rank 53 | 1,440.58100% of row best · rating · hy3; 95% CI [1433.39024152, 1447.77894384]; votes 8047; rank 65 |
| Overall ResultCounted from the protocol-matched rows above · 1 tie | 0 benchmark winsNo overall winner | 0 benchmark winsNo overall winner |
Third-party benchmark Only like-for-like primary-publisher results are shown; raw scores, relative scores, configuration, and token spend remain visible.
Side-by-Side Facts
| Field | Kimi-K2.5 | Hy3 |
|---|---|---|
| Developer | Moonshot AI | Tencent |
| Family | Kimi K2 5 | Hy3 |
| Model | Kimi-K2.5 | Hy3 |
| Version | Kimi-K2.5 | Hy3 |
| Lifecycle | active | active |
| Released | 2026-01-27 | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text |
| Output modalities | Text | Text |
| Context window | 262K | 262K |
| Total parameters | 1T | 298.8B |
| Active parameters | 32B | 21B |
| License | other | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard) | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard) |
| Capabilities | chat, generation, reasoning, tools | chat, generation, tools |
Kimi K2.5 Capabilities
Hy3 Capabilities
Primary Evidence
Sources and Freshness
Questions
Kimi K2.5 vs Hy3 FAQs
Is Kimi K2.5 or Hy3 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Kimi K2.5 and Hy3, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Kimi K2.5 or Hy3?+
Kimi K2.5 is $0.45 and Hy3 is $0.13 per million tokens, so Hy3 is cheaper on this metric. Kimi K2.5 is $2.25 and Hy3 is $0.528 per million tokens, so Hy3 is cheaper on this metric.
Which has a larger context window, Kimi K2.5 or Hy3?+
Neither model has a larger sourced context window in this comparison. Kimi K2.5 is 262K and Hy3 is 262K.
Which performs better in benchmarks, Kimi K2.5 or Hy3?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Kimi K2.5 or Hy3 be self-hosted?+
Both models have the same recorded self-hosting status: supported. Kimi K2.5 is open weight; Hy3 is open weight.
Can Kimi K2.5 and Hy3 understand images?+
Kimi K2.5 is documented with image input; Hy3 is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Kimi K2.5 or Hy3?+
Neither has a larger sourced maximum output. Kimi K2.5 is — and Hy3 is —.
Do Kimi K2.5 and Hy3 support reasoning and tool use?+
Kimi K2.5: reasoning, tool calling, and image input. Hy3: tool calling. Feature support does not establish relative quality.
Which is available from more inference providers, Kimi K2.5 or Hy3?+
Kimi K2.5 has 3 sourced provider routes; Hy3 has 3, a tie.
Which offers better value, Kimi K2.5 or Hy3?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.