# Kronos vs ZAYA1-8B (slim)

> ZAYA1-8B 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-zaya1-8b.md (~8,300 tokens) · this version ~630 tokens · JSON https://www.anchorterminal.com/compare/kronos-vs-zaya1-8b.json · canonical https://www.anchorterminal.com/compare/kronos-vs-zaya1-8b
- 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)

ZAYA1-8B 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
- ZAYA1-8B: C 61, rank #85 of 160 open-weight models · https://www.anchorterminal.com/tools/zaya1-8b.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 50.
- ZAYA1-8B, good for People who want a small, fast reasoning model for maths and code and can live without tool calling Ahead on Reach, 80 against 55; Risk, 55 against 50.

| Category | Kronos | ZAYA1-8B |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 55 | 80 |
| Risk (20%) | 50 | 55 |
| Agent interface (10%) | 60 | 60 |
| Documentation and upkeep (10%) | 61 | 50 |

| Fact (where they differ) | Kronos | ZAYA1-8B |
| --- | --- | --- |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | Zyphra |
| Licence | MIT | Apache-2.0 |
| Last release | 2026-04-13 | 2026-07-02 |
| Popularity | 43k stars | none |

Why the edge:
- Reach, ZAYA1-8B +25: 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…); ZAYA1-8B 80 (Memory 30, the smallest build from Zyphra is the MXFP4-Experts repository, 5.85 GB, and 5.85 GB × 1.2 = 7.0 GB, within 16 GB.)
- Documentation and upkeep, Kronos +11: Kronos 61 (Model card 11, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't.); ZAYA1-8B 50 (Model card 5, Intended use and the parameter counts are on the card.)
- Risk, ZAYA1-8B +5: Kronos 50 (File safety 15, safetensors only, but the only documented loading path is the publisher's Python package in place of a runtime.); ZAYA1-8B 55 (File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository.)