Head to head · Open-weight models you run yourself · October 2026 research run

Kronos vs Ling-3.1-flash-1019

Kronos and Ling-3.1-flash-1019 score within a point of each other on agent readiness, 55.2 (C) and 54.8 (C). Ling-3.1-flash-1019 leads on reach. 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

  • Risk, 50 against 45
  • Documentation and upkeep, 61 against 56

Watch for

Runs only through the publisher's own PyTorch code from GitHub, in no named runtime and with no quantised build

Ling-3.1-flash-1019 C

Best for Teams with a multi-GPU server that want an MIT-licensed flagship for long agent runs and coding

Ahead on

  • Reach, 60 against 55

Watch for

574 GB in FP8 with no smaller build from inclusionAI, so no single machine under 690 GB of GPU memory runs it

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 Ling-3.1-flash-1019 +5

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).

Ling-3.1-flash-1019 60

Memory 0, inclusionAI's only build is the FP8 release at 573.78 GB, × 1.2 = 688.5 GB, above 256 GB, and no runtime's library has a build. Runtimes 25, Released model code in Transformers 5.22.2 (bailing_hybrid), vLLM 0.33.0 (BailingMoeV3ForCausalLM, with ling3 tool and reasoning parsers), SGLang 0.5.23 (bailing_moe_v3.py, its bailing_hybrid config and MTP module) and llama.cpp b12242 (bailingmoe3), and Ollama, credited through its pinned llama.cpp as on the Ling-3.0-tiny listing: v0.40.16 sets LLAMA_CPP_VERSION to b12177. Builds 10, the release is FP8, the one quantised precision inclusionAI publishes for it. Terms 15, MIT in the card's metadata, with no use policy or other terms added on the card or in the repository. Download 10, the Hub API's model info gives gated false on 10 November 2026, so the files download with no account and no terms to accept. Hosted 0, the Hub API's provider mapping is empty for this repository on 10 November 2026. 0 + 25 + 10 + 15 + 10 + 0 = 60.

Risk Kronos +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.

Ling-3.1-flash-1019 45

File safety 15, safetensors only, no .bin, .pt or .pth files (25), less 10 because the card's documented vLLM command passes --trust-remote-code, which runs the repository's configuration_bailing_moe_v3.py, since vLLM 0.33.0 registers no bailing_hybrid config of its own. Provenance 15, files in the inclusionAI organisation that inclusion-ai.org links to, per the Ling-3.0-tiny listing (10). Safety evaluation 0, no safety results for the model on its card or in the training-content summary. Agent guidance 0, the card has nothing on prompt injection, refusals or safeguards, and inclusionAI publishes no guardrail probe for this model as it did for Ling 3.0. Licence risk 15, MIT with no use policy, no field-of-use limits, no threshold and no clause letting inclusionAI change or revoke it. Security programme 0, www.inclusion-ai.org answers 404 for security.txt on 10 November 2026, and the Ling-3.0-tiny listing found no SECURITY.md or disclosure policy in the inclusionAI .github repository. 15 + 15 + 0 + 0 + 15 + 0 = 45.

Documentation and upkeep Kronos +5

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.

Ling-3.1-flash-1019 56

Model card 11, Intended use (complex reasoning, multi-step tasks and agentic workflows), architecture, parameters (560B total, 25B active) and context (1M claimed) are on the card. Training data 15, the training-content summary the card links names the source categories (Common Crawl and other public datasets, commercially licensed data, the Ant Spider crawler, synthetic data), the size band (over 10 trillion text tokens), data collected up to about July 2026 and the filtering, without listing datasets with sizes. Last change 20, the newest commit, on 4 November 2026, edited the card, six days before this check, and the files went up on 27 October. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (both opened on 27 October 2026) has a reply from an inclusionAI member. Version policy 5, the update went into a repository of its own and Ling-3.1-flash and Ling 3.0 stay in theirs. File health 5, the card states a 1M-token context while config.json gives 262,144 with no rope scaling, and its serve commands name the earlier repository as the model path. 11 + 15 + 20 + 0 + 5 + 5 = 56.

Score by category

CategoryWeight this runKronosLing-3.1-flash-1019Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255560Ling-3.1-flash-1019 +5
Risk20%205045Kronos +5
Agent interface10%106060even
Documentation and upkeep10%106156Kronos +5
Negative events≤1500
TotalC 55.2/100C 54.8/100

Facts side by side

FactKronosLing-3.1-flash-1019
KindOpen-weight modelOpen-weight model
VendorYu Shi (shiyu-coder, NeoQuasar), Tsinghua UniversityinclusionAI (Ant Group)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITMIT
Read-only variant documentednono
llms.txtnono
Last release2026-04-132026-11-04
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity43k starsnone

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.

Ling-3.1-flash-1019

inclusionAI's newest flagship, a 560B hybrid mixture of experts under plain MIT that vLLM, SGLang, Transformers and llama.cpp run in released versions. It ships only as 574 GB of FP8, so it needs a multi-GPU server. The card overstates the context, documents little about tool calls, and has no safety results.

Before you call either

Kronos

  1. Clone https://github.com/shiyu-coder/Kronos and pip install -r requirements.txt, then load Kronos.from_pretrained("NeoQuasar/Kronos-small") and KronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base") and wrap them in KronosPredictor
  2. Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
  3. 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
  4. 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
  5. 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
  6. Treat forecasts as model output to check, not signals; the README says its own backtest pipeline isn't a production trading system

Ling-3.1-flash-1019

  1. Serve it with SGLang 0.5.23 or later on 8 H200 or 4 GB300 GPUs, per the card, and use this repository's name as the model path, not the earlier one the card's command shows
  2. With vLLM pass --trust-remote-code, --tool-call-parser ling3 and --reasoning-parser ling3
  3. Set chat_template_kwargs enable_thinking false for direct answers. Reasoning comes back in reasoning_content per SGLang's cookbook
  4. Plan on 262,144 tokens of context. The 1M figure needs the YaRN override in SGLang's cookbook
  5. Use temperature 1.0, top_p 0.95 and top_k 20, per the card
  6. Validate JSON output yourself, since structured output isn't documented

Questions

Which is better for AI agents, Kronos or Ling-3.1-flash-1019?

Kronos and Ling-3.1-flash-1019 score within a point of each other on agent readiness, 55.2 (C) and 54.8 (C). Ling-3.1-flash-1019 leads on reach.

Other comparisons with Kronos or Ling-3.1-flash-1019

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.