# Kronos vs North Mini Code 1.0 (slim)

> North Mini Code 1.0 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-north-mini-code-1-0.md (~9,450 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/kronos-vs-north-mini-code-1-0.json · canonical https://www.anchorterminal.com/compare/kronos-vs-north-mini-code-1-0
- 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)

North Mini Code 1.0 scores 61 (C) 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.

- Kronos: C 55.2, rank #122 of 160 open-weight models · https://www.anchorterminal.com/tools/kronos.min.md
- North Mini Code 1.0: C 61, rank #80 of 160 open-weight models · https://www.anchorterminal.com/tools/north-mini-code-1-0.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.
- North Mini Code 1.0, good for Developers who want a coding agent on their own GPU with a permissive licence Ahead on Reach, 85 against 55; Risk, 60 against 50; Agent interface, 85 against 60.

| Category | Kronos | North Mini Code 1.0 |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 55 | 85 |
| Risk (20%) | 50 | 60 |
| Agent interface (10%) | 60 | 85 |
| Documentation and upkeep (10%) | 61 | 36 |

| Fact (where they differ) | Kronos | North Mini Code 1.0 |
| --- | --- | --- |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | Cohere |
| Licence | MIT | Apache-2.0 |
| Last release | 2026-04-13 | 2026-07-29 |
| Popularity | 43k stars | none |

Why the edge:
- Reach, North Mini Code 1.0 +30: 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…); North Mini Code 1.0 85 (Memory 25, the smallest build from Cohere is the w4a16 repository, 19.38 GB, and 19.38 GB × 1.2 = 23.3 GB, within 24 GB.)
- Agent interface, North Mini Code 1.0 +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.); North Mini Code 1.0 85 (Chat template 20, chat_template.jinja in the repository (12,397 characters).)
- 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.); North Mini Code 1.0 36 (Model card 11, Intended use, the architecture, the parameters and the context are on the card.)
- Risk, North Mini Code 1.0 +10: Kronos 50 (File safety 15, safetensors only, but the only documented loading path is the publisher's Python package in place of a runtime.); North Mini Code 1.0 60 (File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository.)