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

Ling-3.0-tiny vs Nemotron 3 Ultra 550B A55B

Nemotron 3 Ultra 550B A55B scores 68.8 (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 55

Watch for

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

Nemotron 3 Ultra 550B A55B B

Best for Agents with a multi-GPU Blackwell or Hopper node, or using a hosted endpoint, that want NVIDIA's strongest open model for long agent runs

Ahead on

  • Capability, 73 against 31
  • Risk, 70 against 50
  • Agent interface, 90 against 60
  • Documentation and upkeep, 65 against 56

Watch for

The smallest build is 352 GB and needs at least four B200-class GPUs

Score by category

CategoryWeight this runLing-3.0-tinyNemotron 3 Ultra 550B A55BEdge
Capability35%353173Nemotron 3 Ultra 550B A55B +42
Reach25%259055Ling-3.0-tiny +35
Risk20%205070Nemotron 3 Ultra 550B A55B +20
Agent interface10%106090Nemotron 3 Ultra 550B A55B +30
Documentation and upkeep10%105665Nemotron 3 Ultra 550B A55B +9
Negative events≤1500
TotalC 55/100B 68.8/100

Facts side by side

FactLing-3.0-tinyNemotron 3 Ultra 550B A55B
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-06-04
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)2.8/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 Ultra 550B A55B

NVIDIA's frontier-scale agent cousin with trained parallel tool calls, up to a 1M-token context and training against prompt injection through tool output. It needs at least four Blackwell GPUs for the 352 GB NVFP4 build, so most agents will use NVIDIA's API or a provider. The main risks are serving commands that run repository code and no published safety results.

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 Ultra 550B A55B

  1. It doesn't fit the 128 GB reference machine at any precision. Call NVIDIA's API (model nvidia/nemotron-3-ultra-550b-a55b) or a provider instead
  2. With vLLM serve the NVFP4 build with --trust-remote-code --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on 4 × B200 or more
  3. With SGLang use --reasoning-parser nemotron_3, not the BF16 card's nemotron_v3, which SGLang doesn't register
  4. On SGLang with tools, pass chat_template_kwargs with enable_thinking true and force_nonempty_content true, as the card says, or reasoning and calls won't both parse
  5. Thinking is on by default. Pass enable_thinking: false for short tasks or medium_effort: true to cut reasoning tokens
  6. Use temperature=1.0 and top_p=0.95, as the generation config sets

Questions

Which is better for AI agents, Ling-3.0-tiny or Nemotron 3 Ultra 550B A55B?

Nemotron 3 Ultra 550B A55B scores 68.8 (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 Ultra 550B A55B

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.