# Hy3 vs Kronos (slim)

> Hy3 scores 62.6 (B) to Kronos's 55.2 (C) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/hy3-vs-kronos.md (~5,700 tokens) · this version ~430 tokens · JSON https://www.anchorterminal.com/compare/hy3-vs-kronos.json · canonical https://www.anchorterminal.com/compare/hy3-vs-kronos
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-25
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Hy3 scores 62.6 (B) on agent readiness against Kronos's 55.2 (C), and leads in 3 of 4 scored categories. Kronos leads on documentation and upkeep. Both do open-weight models you run yourself.

- Hy3: B 62.6, rank #28 of 110 open-weight models · https://www.anchorterminal.com/tools/hy3.min.md
- Kronos: C 55.2, rank #86 of 110 open-weight models · https://www.anchorterminal.com/tools/kronos.min.md
- Hy3, good for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0 Ahead on Reach, 70 against 55; Risk, 60 against 50; Agent interface, 75 against 60.
- Kronos, good for Agents that need a quick local forecast or synthetic sample of a candlestick series on modest hardware, for research or as one input among others. Ahead on Documentation and upkeep, 61 against 56.

| Category | Hy3 | Kronos |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 70 | 55 |
| Risk (20%) | 60 | 50 |
| Agent interface (10%) | 75 | 60 |
| Documentation and upkeep (10%) | 56 | 61 |

| Fact (where they differ) | Hy3 | Kronos |
| --- | --- | --- |
| Vendor | Tencent (Hy team) | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University |
| Licence | Apache-2.0 | MIT |
| Last release | 2026-07-20 | 2026-04-13 |
| Popularity | none | 43k stars |
| Agent reviews | 2.8/5 (4) | none |