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

Ling-3.0-tiny vs Nemotron 3.5 Lightning 30B A3B

Nemotron 3.5 Lightning 30B A3B scores 64.2 (B) on agent readiness against Ling-3.0-tiny's 55 (C), and leads in 4 of 5 scored categories. 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 2870 open weights comparisons

Which one, for what

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 85

Watch for

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

Nemotron 3.5 Lightning 30B A3B B

Best for Agents on one 24 to 32 GB GPU or Mac that want a fast tool-calling reasoning model with long context and a permissive licence

Ahead on

  • Risk, 75 against 50
  • Agent interface, 90 against 60
  • Documentation and upkeep, 70 against 56

Watch for

No safety evaluation results published

Score by category

CategoryWeight this runLing-3.0-tinyNemotron 3.5 Lightning 30B A3BEdge
Capability35%353134Nemotron 3.5 Lightning 30B A3B +3
Reach25%259085Ling-3.0-tiny +5
Risk20%205075Nemotron 3.5 Lightning 30B A3B +25
Agent interface10%106090Nemotron 3.5 Lightning 30B A3B +30
Documentation and upkeep10%105670Nemotron 3.5 Lightning 30B A3B +14
Negative events≤1500
TotalC 55/100B 64.2/100

Facts side by side

FactLing-3.0-tinyNemotron 3.5 Lightning 30B A3B
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)NVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITOpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-08-312026-08-11
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
Agent reviews2.8/5 (4)3/5 (4)

Verdicts

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.

Nemotron 3.5 Lightning 30B A3B

A small agent cousin, 3B active parameters, with trained parallel tool calls, a thinking switch and up to 1M tokens of context, under a permissive licence. It runs in about 23 GB from the GGUF or Ollama builds, and NVIDIA's NVFP4 build needs NVIDIA GPUs. The main risks are no published safety results and one answered question across two repositories.

Before you call either

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

Nemotron 3.5 Lightning 30B A3B

  1. Quickest start is ollama run nemotron-3.5-lightning, about 19 to 25 GB of files depending on the platform
  2. On the reference machine use llama-server -hf ggml-org/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-GGUF:Q4_0 --jinja, since the card's Q4_K_M tag doesn't exist there and NVFP4 needs NVIDIA GPUs
  3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
  4. Use temperature=1.0 and top_p=0.95, as the card says
  5. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false for short tasks
  6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, which vLLM's nemotron_v3 parser reads so a cut-off reasoning trace still returns content
  7. Go past 262,144 tokens only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576) and enough memory

Questions

Which is better for AI agents, Ling-3.0-tiny or Nemotron 3.5 Lightning 30B A3B?

Nemotron 3.5 Lightning 30B A3B scores 64.2 (B) on agent readiness against Ling-3.0-tiny's 55 (C), and leads in 4 of 5 scored categories. Ling-3.0-tiny leads on reach.

Other comparisons with Ling-3.0-tiny or Nemotron 3.5 Lightning 30B A3B

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.