# Kronos vs Ornith-1.5-122B (slim)

> Ornith-1.5-122B scores 61 (C) 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/kronos-vs-ornith-1-5-122b.md (~8,900 tokens) · this version ~680 tokens · JSON https://www.anchorterminal.com/compare/kronos-vs-ornith-1-5-122b.json · canonical https://www.anchorterminal.com/compare/kronos-vs-ornith-1-5-122b
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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

- Kronos: C 55.2, rank #122 of 160 open-weight models · https://www.anchorterminal.com/tools/kronos.min.md
- Ornith-1.5-122B: C 61, rank #81 of 160 open-weight models · https://www.anchorterminal.com/tools/ornith-1-5-122b.min.md
- 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 36.
- Ornith-1.5-122B, good for Local coding and terminal agents on a 128 GB unified-memory machine or a 96 GB GPU setup, where a clear licence file and an answering publisher aren't required Ahead on Reach, 75 against 55; Agent interface, 85 against 60.

| Category | Kronos | Ornith-1.5-122B |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 55 | 75 |
| Risk (20%) | 50 | 50 |
| Agent interface (10%) | 60 | 85 |
| Documentation and upkeep (10%) | 61 | 36 |

| Fact (where they differ) | Kronos | Ornith-1.5-122B |
| --- | --- | --- |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | Ornith |
| Last release | 2026-04-13 | 2026-10-24 |
| Popularity | 43k stars | none |

Why the edge:
- Agent interface, Ornith-1.5-122B +25: Kronos 60 (Read for a forecasting model, the tool-calling, trained tool calling and structured-output lines stand for what it takes and returns.); Ornith-1.5-122B 85 (Chat template 20, a Jinja file in the repository.)
- Documentation and upkeep, Kronos +25: Kronos 61 (Model card 11, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't.); Ornith-1.5-122B 36 (Model card 11, it covers intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off.)
- Reach, Ornith-1.5-122B +20: Kronos 55 (Memory 30, the publisher's Kronos-mini with its tokeniser is 0.03 GB and even Kronos-base is 0.43 GB in FP32. Runtimes 0, it runs only through the publisher's o…); Ornith-1.5-122B 75 (Memory 10, since Ornith's own MLX 4-bit build is 69.7 GB and needs about 83.6 GB with the fifth added, over 64 GB and inside the reference machine's 107.4 GB, a…)