Head to head · Open-weight models you run yourself · October 2026 research run
Kronos vs MiniCPM-V 4.7 1B
MiniCPM-V 4.7 1B 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.
Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons
Which one, for what
Kronos C
Best 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 48
Watch for
Runs only through the publisher's own PyTorch code from GitHub, in no named runtime and with no quantised build
Best for Agents that need a cheap local model to read screenshots, photos and short video on a phone, a laptop or beside a bigger model
Ahead on
- Reach, 95 against 55
- Risk, 55 against 50
- Agent interface, 70 against 60
Watch for
No limitations section, safety results, agent-use guidance or security contact
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reach MiniCPM-V 4.7 1B +40
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 own PyTorch package from GitHub, and none of the six named runtimes supports it. Builds 0, FP32 safetensors only. Terms 15, MIT with nothing added. Download 10, nothing is gated. Hosted 0, no inference provider or publisher API serves it (provider mapping still empty on 4 November).
MiniCPM-V 4.7 1B 95
Memory 30, OpenBMB's own IQ4_XS GGUF is 0.64 GB, 1.54 GB with the 0.90 GB vision projector, and 1.54 GB × 1.2 = 1.9 GB, which fits 16 GB with room to spare. Runtimes 25, MiniCPMV4_7ForConditionalGeneration in vLLM's registry at v0.33.0, the minicpmv4_7 model type in SGLang's minicpmv.py at v0.5.23, the minicpmv4_7 model in Transformers at v5.22.2, a MiniCPM-V 4.7 guide and conversion code in llama.cpp at b12242, and an openbmb/minicpm-v4.7:1b tag in OpenBMB's namespace on Ollama, read as the 35B-A3B listing's is. Builds 15, OpenBMB publishes AWQ, GPTQ and int4 safetensors builds and a GGUF repository from IQ3_XS to F16, so quantised builds at two precisions or more. Terms 15, Apache 2.0 in the card's metadata and as the LICENSE of OpenBMB's MiniCPM-V repository, an OSI licence. Download 10, gated is false on the main repository and on the GGUF, AWQ, GPTQ and int4 repositories, so the files download with no account or terms. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and no provider's own list was read. 30 + 25 + 15 + 15 + 10 + 0 = 95.
Documentation and upkeep Kronos +13
Kronos 61
Model card 11, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 20, the paper lists every exchange with asset and observation counts, the filtering and a June 2024 end. Last change 5, the reference code on 13 April 2026 (still the newest commit on 4 November, 205 days) and the Hub repositories on 9 September 2025. Responsiveness 20, the publisher answered 10 of 18 Hugging Face discussions (recounted by script on 4 November), though none since 24 November 2025, and the seven opened since April 2026 have no reply from it. Version policy 5, a first release. File health 0, the cards point to example data the repository has deleted and to licence and requirements links on a branch that doesn't exist.
MiniCPM-V 4.7 1B 48
Model card 8, Intended use (image, multi-image and video understanding on device), architecture (early visual-token compression inside the vision encoder) and parameters (1B) are there. Training data 0, no description of the training data on the card. Last change 20, the last commit, on 30 October 2026, updated the card and removed an unused asset folder, eleven days before this check. Responsiveness 0, the repository has no discussions that aren't pull requests (two pull requests in all), so nobody has asked anything yet and the line reads as none answered, as settled in calibration. Version policy 10, MiniCPM-V 4.5 and 4.6 stay in their own repositories and the GitHub README dates each release. File health 10, Config, template and card agree on the architecture and the thinking switch, and no report waits without a reply, since there are no discussions. 8 + 0 + 20 + 0 + 10 + 10 = 48.
Agent interface MiniCPM-V 4.7 1B +10
Kronos 60
Read for a forecasting model, the tool-calling, trained tool calling and structured-output lines stand for what it takes and returns. The card documents the DataFrame and timestamps it takes and the DataFrame it returns, and the publisher's KronosPredictor builds and parses them (25). It was trained on six K-line fields with calendar fields, one series per forecast (10). Output is a typed DataFrame indexed by the requested timestamps, the mean of the sampled paths (15). The input format is given only as code (10). Reasoning control and context score 0, with no reasoning and a 512-bar context (2,048 for Kronos-mini).
MiniCPM-V 4.7 1B 70
Chat template 20, chat_template.jinja in the repository, 7,249 characters. Tool-calling format 10, the card shows tools declared in the OpenAI tools array in a request to Transformers' server, but not how a call comes back, and names no parser for vLLM or SGLang. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one assistant turn, and the card gives a tool-calling request as a supported use. Structured output 0, Neither JSON nor JSON Schema output is documented or claimed for the model on the card. Reasoning control 10, the card passes enable_thinking per request in its examples, the template has been off by default since 19 October 2026, and the GGUF repository keeps thinking builds in their own folder. Context 10, 262,144 tokens, max_position_embeddings in the text config. 20 + 10 + 20 + 0 + 10 + 10 = 70.
Risk MiniCPM-V 4.7 1B +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. Provenance 15, the files are in the NeoQuasar account the publisher's README links, with SHA-256 hashes. Safety evaluation 0, none published. Agent guidance 5, the README's general cautions that the fine-tuning pipeline isn't a production trading system. Licence risk 15, plain MIT; the broken licence link is charged to file health. Security programme 0, no reporting route found.
MiniCPM-V 4.7 1B 55
File safety 25, safetensors in the main repository and the AWQ, GPTQ and int4 builds, GGUF in the GGUF build, with no .bin, .pt, .pth or .py files in the main repository. Provenance 15, files in the openbmb organisation that OpenBMB's GitHub README links to (10), with a SHA-256 for both large files in the main repository (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or disclaimer section, and no prompt-injection guidance, instruction hierarchy or statement of trained refusals. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the LICENSE in OpenBMB's GitHub repository resolved on 10 November 2026. Security programme 0, no SECURITY.md in OpenBMB/MiniCPM-V and no security.txt on openbmb.cn (both 404 on 10 November 2026), and no advisories found. 25 + 15 + 0 + 0 + 15 + 0 = 55.
Score by category
| Category | Weight this run | Kronos | MiniCPM-V 4.7 1B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 55 | 95 | MiniCPM-V 4.7 1B +40 |
| Risk | 20%20 | 50 | 55 | MiniCPM-V 4.7 1B +5 |
| Agent interface | 10%10 | 60 | 70 | MiniCPM-V 4.7 1B +10 |
| Documentation and upkeep | 10%10 | 61 | 48 | Kronos +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 55.2/100 | C 61/100 |
Facts side by side
| Fact | Kronos | MiniCPM-V 4.7 1B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | OpenBMB |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-04-13 | 2026-10-30 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Popularity | 43k stars | none |
Verdicts
Kronos
Forecasts the next price bars from a history of up to 512 candlestick bars. Every size fits in under 0.5 GB and runs on a CPU, but only through the publisher's own Python package. Nobody has benchmarked it independently, its quickstart data was deleted from the repository, and the publisher hasn't replied since November 2025.
MiniCPM-V 4.7 1B
A vision-language cousin small enough for a phone, under plain Apache 2.0, that every runtime we count can load. The projector is bigger than the language model, so plan for about 2 GB. The card says nothing about limits or training data and doesn't show how a tool call comes back.
Before you call either
Kronos
- Clone https://github.com/shiyu-coder/Kronos and
pip install -r requirements.txt, then loadKronos.from_pretrained("NeoQuasar/Kronos-small")andKronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base")and wrap them in KronosPredictor - Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
- The examples read examples/data/XSHG_5min_600977.csv, which no longer exists; point them at tests/data/regression_input.csv, 2,500 five-minute bars
- Keep the lookback at or under max_context, 512 bars, and pass the future timestamps you want as y_timestamp, since the calendar fields come from them
- Raise sample_count for a steadier forecast, but expect only the mean back; call the lower-level auto_regressive_inference yourself if you need the paths
- Treat forecasts as model output to check, not signals; the README says its own backtest pipeline isn't a production trading system
MiniCPM-V 4.7 1B
- Start it with
llama-server -hf openbmb/MiniCPM-V-4.7-1B-gguf:Q4_K_M --jinja, orollama run openbmb/minicpm-v4.7:1b - For image input in llama.cpp add
mmproj-model-f16.gguf, or the smaller 4x projector - The GGUF files at the repository root have thinking off. Use the files in
thinking/when you want the trace - Use temperature 0.7, top_p 0.95 and top_k 100 in instruct mode, as the card recommends
- Check tool calls in your runtime first, since the card names no parser
- Validate JSON output yourself, since structured output isn't documented
Questions
Which is better for AI agents, Kronos or MiniCPM-V 4.7 1B?
MiniCPM-V 4.7 1B 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.
Other comparisons with Kronos or MiniCPM-V 4.7 1B
- Agents-A1-4B vs Kronos
- Agents-A1-4B vs MiniCPM-V 4.7 1B
- Apertus v1.5 8B vs Kronos
- Apertus v1.5 8B vs MiniCPM-V 4.7 1B
- Apodex-1.1-mini vs Kronos
- Apodex-1.1-mini vs MiniCPM-V 4.7 1B
- Arete-27B vs Kronos
- Arete-27B vs MiniCPM-V 4.7 1B
- BigBang-v1 vs Kronos
- BigBang-v1 vs MiniCPM-V 4.7 1B
- Carbon-X vs Kronos
- Carbon-X vs MiniCPM-V 4.7 1B
- Cosmos-Reason2-2B vs Kronos
- Cosmos-Reason2-2B vs MiniCPM-V 4.7 1B
- Darwin-36B-Opus vs Kronos
- Darwin-36B-Opus vs MiniCPM-V 4.7 1B
- DeepSeek-V3.2 vs Kronos
- DeepSeek-V3.2 vs MiniCPM-V 4.7 1B
- DeepSeek V4.1 Flash vs Kronos
- DeepSeek V4.1 Flash vs MiniCPM-V 4.7 1B
- DeepSeek-V4-Flash-0731 vs Kronos
- DeepSeek-V4-Flash-0731 vs MiniCPM-V 4.7 1B
- DiffusionGemma 26B A4B IT vs Kronos
- DiffusionGemma 26B A4B IT vs MiniCPM-V 4.7 1B
- Gemma 4 12B IT vs Kronos
- Gemma 4 12B IT vs MiniCPM-V 4.7 1B
- Gemma 4 26B A4B IT vs Kronos
- Gemma 4 26B A4B IT vs MiniCPM-V 4.7 1B
- Gemma 4 31B IT vs Kronos
- Gemma 4 31B IT vs MiniCPM-V 4.7 1B
- Gemma 4 E2B IT vs Kronos
- Gemma 4 E2B IT vs MiniCPM-V 4.7 1B
- Gemma 4 E4B IT vs Kronos
- Gemma 4 E4B IT vs MiniCPM-V 4.7 1B
- GLM-4.5-Air vs Kronos
- GLM-4.5-Air vs MiniCPM-V 4.7 1B
- GLM-4.7-Flash vs Kronos
- GLM-4.7-Flash vs MiniCPM-V 4.7 1B
- GLM-5.3-Flash vs Kronos
- GLM-5.3-Flash vs MiniCPM-V 4.7 1B
- GLM-5.3 vs Kronos
- GLM-5.3 vs MiniCPM-V 4.7 1B
- gpt-oss-120b vs Kronos
- gpt-oss-120b vs MiniCPM-V 4.7 1B
- gpt-oss-20b vs Kronos
- gpt-oss-20b vs MiniCPM-V 4.7 1B
- Granite 4.2 30B vs Kronos
- Granite 4.2 30B vs MiniCPM-V 4.7 1B
- Granite 4.2 3B vs Kronos
- Granite 4.2 3B vs MiniCPM-V 4.7 1B
- Granite 4.2 8B vs Kronos
- Granite 4.2 8B vs MiniCPM-V 4.7 1B
- Hy-Memory-30B-A3B vs Kronos
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 1B
- Hy3 vs Kronos
- Hy3 vs MiniCPM-V 4.7 1B
- Inkling-Small vs Kronos
- Inkling-Small vs MiniCPM-V 4.7 1B
- Inkling vs Kronos
- Inkling vs MiniCPM-V 4.7 1B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kronos
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiniCPM-V 4.7 1B
- Kimi K3.1 Pro vs Kronos
- Kimi K3.1 Pro vs MiniCPM-V 4.7 1B
- Kimi K3 vs Kronos
- Kimi K3 vs MiniCPM-V 4.7 1B
- Kolibri-1 vs Kronos
- Kolibri-1 vs MiniCPM-V 4.7 1B
- Kronos vs Laguna M.1
- Kronos vs Laguna S 2.1
- Kronos vs Laguna XS 2.1
- Kronos vs LBS-27B
- Kronos vs LFM2.5-2.6B
- Kronos vs LFM3-1.7B
- Kronos vs LFM3-Audio-2B
- Kronos vs LFM3-Omni-2B
- Kronos vs LFM3-VL-2B
- Kronos vs Ling-3.0-tiny
- Kronos vs Ling-3.1-flash-1019
- Kronos vs MiMo-V2.6 Distill Qwen 9B
- Kronos vs MiniCPM-o 4.5
- Kronos vs MiniCPM-V 4.7 35B-A3B
- Kronos vs MiniCPM5-2B
- Kronos vs MiniMax-M2.5
- Kronos vs MiniMax-M2.7
- Kronos vs MiniMax-M3.1-Flash
- Kronos vs Mistral Large 4
- Kronos vs Muse Glimmer 30B
- Kronos vs Nanbeige4.3-33B
- Kronos vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kronos vs Nemotron 3.5 Lightning 30B A3B
- Kronos vs Nemotron 3 Nano 30B A3B
- Kronos vs Nemotron 3 Nano 4B
- Kronos vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kronos vs Nemotron 3 Super 120B A12B
- Kronos vs Nemotron 3 Ultra 550B A55B
- Kronos vs occamy-1.0
- Kronos vs Olmo 3 7B Think
- Kronos vs Ornith-1.5-122B
- Kronos vs Ornith-1.5-35B-A3B
- Kronos vs Ornith-1.5-397B
- Kronos vs Ornith-1.5-9B
- Kronos vs Qwen-AgentWorld-35B-A3B
- Kronos vs Qwen3-30B-A3B-Instruct-2507
- Kronos vs Qwen3-4B-Instruct-2507
- Kronos vs Qwen3.5-0.8B
- Kronos vs Qwen3.5-122B-A10B
- Kronos vs Qwen3.5-2B
- Kronos vs Qwen3.5-397B-A17B
- Kronos vs Qwen3.5-4B
- Kronos vs Qwen3.5-9B
- Kronos vs Qwen3.6-27B
- Kronos vs Qwen3.6-35B-A3B
- Kronos vs Qwen3.8-27B
- Kronos vs Qwen3.8-Flash-Next
- Kronos vs Qwen3-Coder-30B-A3B-Instruct
- Kronos vs Qwen3-Coder-Next
- Kronos vs Qwen3-Omni-30B-A3B-Instruct
- Kronos vs Qwen3-VL-2B-Instruct
- Kronos vs Qwen3-VL-30B-A3B-Instruct
- Kronos vs Qwen3-VL-32B-Instruct
- Kronos vs Qwen3-VL-4B-Instruct
- Kronos vs Qwen3-VL-8B-Instruct
- Kronos vs Qwopus3.8-27B-Flash-V2
- Kronos vs Recursive Flint
- Kronos vs Ripple-65B Preview
- Kronos vs SmolLM3-3B
- Kronos vs Spark-X2.6-4B
- Kronos vs Swift 1.5 Qwen3.8-27B
- Kronos vs Swift 1.5 Qwen3.8-Flash-Next
- Kronos vs ThinkingCap (Qwen3.8 27B)
- Kronos vs Baidu Unlimited-OCR-2
- Laguna M.1 vs MiniCPM-V 4.7 1B
- Laguna S 2.1 vs MiniCPM-V 4.7 1B
- Laguna XS 2.1 vs MiniCPM-V 4.7 1B
- LBS-27B vs MiniCPM-V 4.7 1B
- LFM2.5-2.6B vs MiniCPM-V 4.7 1B
- LFM3-1.7B vs MiniCPM-V 4.7 1B
- LFM3-Audio-2B vs MiniCPM-V 4.7 1B
- LFM3-Omni-2B vs MiniCPM-V 4.7 1B
- LFM3-VL-2B vs MiniCPM-V 4.7 1B
- Ling-3.0-tiny vs MiniCPM-V 4.7 1B
- Ling-3.1-flash-1019 vs MiniCPM-V 4.7 1B
- MiMo-V2.6 Distill Qwen 9B vs MiniCPM-V 4.7 1B
- MiniCPM-o 4.5 vs MiniCPM-V 4.7 1B
- MiniCPM-V 4.7 1B vs MiniCPM-V 4.7 35B-A3B
- MiniCPM-V 4.7 1B vs MiniCPM5-2B
- MiniCPM-V 4.7 1B vs MiniMax-M2.5
- MiniCPM-V 4.7 1B vs MiniMax-M2.7
- MiniCPM-V 4.7 1B vs MiniMax-M3.1-Flash
- MiniCPM-V 4.7 1B vs Mistral Large 4
- MiniCPM-V 4.7 1B vs Muse Glimmer 30B
- MiniCPM-V 4.7 1B vs Nanbeige4.3-33B
- MiniCPM-V 4.7 1B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- MiniCPM-V 4.7 1B vs Nemotron 3.5 Lightning 30B A3B
- MiniCPM-V 4.7 1B vs Nemotron 3 Nano 30B A3B
- MiniCPM-V 4.7 1B vs Nemotron 3 Nano 4B
- MiniCPM-V 4.7 1B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- MiniCPM-V 4.7 1B vs Nemotron 3 Super 120B A12B
- MiniCPM-V 4.7 1B vs Nemotron 3 Ultra 550B A55B
- MiniCPM-V 4.7 1B vs occamy-1.0
- MiniCPM-V 4.7 1B vs Olmo 3 7B Think
- MiniCPM-V 4.7 1B vs Ornith-1.5-122B
- MiniCPM-V 4.7 1B vs Ornith-1.5-35B-A3B
- MiniCPM-V 4.7 1B vs Ornith-1.5-397B
- MiniCPM-V 4.7 1B vs Ornith-1.5-9B
- MiniCPM-V 4.7 1B vs Qwen-AgentWorld-35B-A3B
- MiniCPM-V 4.7 1B vs Qwen3-30B-A3B-Instruct-2507
- MiniCPM-V 4.7 1B vs Qwen3-4B-Instruct-2507
- MiniCPM-V 4.7 1B vs Qwen3.5-0.8B
- MiniCPM-V 4.7 1B vs Qwen3.5-122B-A10B
- MiniCPM-V 4.7 1B vs Qwen3.5-2B
- MiniCPM-V 4.7 1B vs Qwen3.5-397B-A17B
- MiniCPM-V 4.7 1B vs Qwen3.5-4B
- MiniCPM-V 4.7 1B vs Qwen3.5-9B
- MiniCPM-V 4.7 1B vs Qwen3.6-27B
- MiniCPM-V 4.7 1B vs Qwen3.6-35B-A3B
- MiniCPM-V 4.7 1B vs Qwen3.8-27B
- MiniCPM-V 4.7 1B vs Qwen3.8-Flash-Next
- MiniCPM-V 4.7 1B vs Qwen3-Coder-30B-A3B-Instruct
- MiniCPM-V 4.7 1B vs Qwen3-Coder-Next
- MiniCPM-V 4.7 1B vs Qwen3-Omni-30B-A3B-Instruct
- MiniCPM-V 4.7 1B vs Qwen3-VL-2B-Instruct
- MiniCPM-V 4.7 1B vs Qwen3-VL-30B-A3B-Instruct
- MiniCPM-V 4.7 1B vs Qwen3-VL-32B-Instruct
- MiniCPM-V 4.7 1B vs Qwen3-VL-4B-Instruct
- MiniCPM-V 4.7 1B vs Qwen3-VL-8B-Instruct
- MiniCPM-V 4.7 1B vs Qwopus3.8-27B-Flash-V2
- MiniCPM-V 4.7 1B vs Recursive Flint
- MiniCPM-V 4.7 1B vs Ripple-65B Preview
- MiniCPM-V 4.7 1B vs SmolLM3-3B
- MiniCPM-V 4.7 1B vs Spark-X2.6-4B
- MiniCPM-V 4.7 1B vs Swift 1.5 Qwen3.8-27B
- MiniCPM-V 4.7 1B vs Swift 1.5 Qwen3.8-Flash-Next
- MiniCPM-V 4.7 1B vs ThinkingCap (Qwen3.8 27B)
- MiniCPM-V 4.7 1B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/kronos-vs-minicpm-v-4-7-1b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kronos.json·/api/v1/tools/minicpm-v-4-7-1b.json - From a terminal
anchor compare kronos minicpm-v-4-7-1b(the CLI) - Over MCP
compare_tools {"a": "kronos", "b": "minicpm-v-4-7-1b"}at/mcp, no key