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

Kronos vs Ling-3.0-tiny

Kronos and Ling-3.0-tiny score within a point of each other on agent readiness, 55.2 (C) and 55 (C). Ling-3.0-tiny leads on reach. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 3260 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 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.0-tiny C

Best for Agents on a laptop or small GPU that want a fast local model for tool calls and short reasoning, under MIT

Ahead on

  • Reach, 90 against 55

Watch for

No hosted provider today, and Ollama support is only an unmerged pull request

Score by category

CategoryWeight this runKronosLing-3.0-tinyEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255590Ling-3.0-tiny +35
Risk20%205050even
Agent interface10%106060even
Documentation and upkeep10%106156Kronos +5
Negative events≤1500
TotalC 55.2/100C 55/100

Facts side by side

FactKronosLing-3.0-tiny
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-08-31
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity43k starsnone
Agent reviewsnone2.8/5 (4)

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.0-tiny

A small, quick hybrid reasoning cousin for local agent work, tool calls and coding, under MIT. It runs in about 6 GB from inclusionAI's 4-bit GGUF in released Transformers, vLLM, SGLang and llama.cpp, with no host. The main risks are a card that doesn't match the files in places, the vLLM route running repository code, and no model 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.0-tiny

  1. Start it with llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF:Q4_K_M --jinja -c 32768, which needs llama.cpp b11772 or a recent release with bailingmoe3
  2. With vLLM 0.32.0, vllm serve inclusionAI/Ling-3.0-tiny --trust-remote-code --enable-prefix-caching --mamba-cache-mode align --enable-auto-tool-choice --tool-call-parser ling3 --reasoning-parser ling3, which runs the repository's config code
  3. With SGLang 0.5.22, its cookbook uses --reasoning-parser deepseek-r1 --tool-call-parser glm45 for this model, and drop the card's NEXTN flags since tiny has no MTP layer
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks
  5. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 20
  6. The template keeps earlier reasoning in the prompt, which grows long agent sessions
  7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
  8. For a guardrail, inclusionAI's Ling-3.0-tiny-singprobe scores intent, unsafe output and hallucination per token, but only through SGLang and vLLM integration branches

Questions

Which is better for AI agents, Kronos or Ling-3.0-tiny?

Kronos and Ling-3.0-tiny score within a point of each other on agent readiness, 55.2 (C) and 55 (C). Ling-3.0-tiny leads on reach.

Other comparisons with Kronos or Ling-3.0-tiny

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.