# Kronos vs Ripple-65B Preview (slim)

> Kronos scores 55.2 (C) to Ripple-65B Preview's 53.3 (D) 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-ripple-65b-preview.md (~7,650 tokens) · this version ~1,630 tokens · JSON https://www.anchorterminal.com/compare/kronos-vs-ripple-65b-preview.json · canonical https://www.anchorterminal.com/compare/kronos-vs-ripple-65b-preview
- 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-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Kronos scores 55.2 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 2 of 4 scored categories. Ripple-65B Preview leads on risk and agent interface. Both do open-weight models you run yourself.

- Kronos: C 55.2, rank #94 of 121 open-weight models · https://www.anchorterminal.com/tools/kronos.min.md
- Ripple-65B Preview: D 53.3, rank #103 of 121 open-weight models · https://www.anchorterminal.com/tools/ripple-65b-preview.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 Reach, 55 against 45; Documentation and upkeep, 61 against 49.
- Ripple-65B Preview, good for Teams with Blackwell GPUs or a DGX Spark who want an Apache 2.0 coding model to try for terminal and agentic coding work, and can run the publisher's code to serve it. Ahead on Risk, 55 against 50; Agent interface, 75 against 60.

| Category | Kronos | Ripple-65B Preview |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 55 | 45 |
| Risk (20%) | 50 | 55 |
| Agent interface (10%) | 60 | 75 |
| Documentation and upkeep (10%) | 61 | 49 |

| Fact (where they differ) | Kronos | Ripple-65B Preview |
| --- | --- | --- |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | Ricursive Intelligence |
| Licence | MIT | Apache-2.0 |
| Last release | 2026-04-13 | 2026-11-04 |
| Terms last updated | no document linked | not read yet |
| Popularity | 43k stars | none |

Why the edge:
- Agent interface, Ripple-65B Preview +15: 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).); Ripple-65B Preview 75 (Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, Ricursive's server README says how tools are declared and calls come back, with the ripple parser in SGLang 0.5.19. Trained tool calling 20, one or more calls a turn and agentic-coding RL. Structured output 0, not documented. Reasoning control 0, the template has no thinking switch or effort levels. Context 10, long-context training at 2M-token sequences for a stated 1M.)
- Documentation and upkeep, Kronos +12: 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.); Ripple-65B Preview 49 (Model card 14 of 20, no limitations and no knowledge cut-off. Training data 5, a general description with token counts and no cut-off. Last change 20, released today. Responsiveness 0, no discussions yet, read as none answered. Version policy 5, a first release, with the NVFP4 checkpoint replaced in place on release day under a commit note. File health 5, tokenizer_config.json carries a second, tool-less chat template and a 131,072-token limit against the card's 1M.)
- Reach, Kronos +10: 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).); Ripple-65B Preview 45 (Memory 10 of 30, the smallest 4-bit build is Ricursive's NVFP4 at 57.2 GB, 68.7 GB with a fifth added, which is over 64 GB and fits our reference machine. Runtimes 0, no released runtime runs the ricursive architecture with its own code; Ricursive's SGLang plugin and Transformers' remote code don't count. Builds 10, one quantised precision (NVFP4) from Ricursive. Terms 15, Apache 2.0 with nothing added. Download 10, not gated. Hosted 0, Ricursive serves no API, Hugging Face maps no provider, Together AI's page says coming soon, and GMI Cloud's and OpenRouter's pages weren't read.)
- Risk, Ripple-65B Preview +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.); Ripple-65B Preview 55 (File safety 15, safetensors only, less 10 because the documented way to run it loads Ricursive's Python. Provenance 15, the files are in the organisation ricursive.com links to, with a checksum on every file. Safety evaluation 10, Ricursive's own FORTRESS and StrongREJECT results. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, Apache 2.0. Security programme 0, no way to report a flaw.)