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

LFM3-1.7B vs Nemotron 3.5 Lightning 30B A3B

Nemotron 3.5 Lightning 30B A3B scores 64.7 (B) on agent readiness against LFM3-1.7B's 61 (C), and leads in 2 of 4 scored categories. LFM3-1.7B leads on agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

LFM3-1.7B C

Best for Agents on a laptop, phone or small server that need tool calling and a long context from a model under 2 GB at 4 bits

Ahead on

  • Agent interface, 100 against 90

Watch for

vLLM and SGLang have no released support, though the card lists both

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 40
  • Documentation and upkeep, 75 against 67

Watch for

No safety evaluation results published

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.

Risk Nemotron 3.5 Lightning 30B A3B +35

LFM3-1.7B 40

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.

Nemotron 3.5 Lightning 30B A3B 75

File safety earns 25, safetensors only with no Python files, and nothing from the repository runs to load it or parse its output. Provenance earns 15, files in NVIDIA's linked organisation with a hash for every file. Safety evaluation earns 0, since NVIDIA says it evaluated content safety but publishes no results. Agent guidance earns 10, a subcard that names prompt injection and the safeguards to add, without an instruction hierarchy. Licence risk keeps all 15 under OpenMDW-1.1. The security programme earns 10 for the reporting route on the card and NVIDIA's public bulletins.

Agent interface LFM3-1.7B +10

LFM3-1.7B 100

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, tools, deferred tools, tool results and the thinking switch. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card says the model was trained on tool calls and agentic traces and with reinforcement learning inside agent harnesses. Structured output 15, Liquid's API guide documents response_format with a JSON Schema, with lfm3-1.7b as the model in its examples, and says the schema is checked before generation starts. Reasoning control 10, the card documents enable_thinking=False in the chat template to turn reasoning off per request, with reasoning on by default inside think tags, and preserve_thinking for earlier turns. Context 10, 256K tokens per the card, which says the mid-training stage extended the context window to 256K, and max_position_embeddings 262144 in config.json. 20 + 25 + 20 + 15 + 10 + 10 = 100.

Nemotron 3.5 Lightning 30B A3B 90

The chat template earns 20, a Jinja file in the repository. The tool-calling format earns 25, since the card names the qwen3_coder parser and shows a tool call declared and read back. Trained tool calling earns 20, with tool-use training and several calls per turn in the template. Structured output earns 5, claimed from training with no instructions. Reasoning control earns 10, thinking off per request with runtime parsers that return the reasoning apart. Context earns 10 for up to 1M tokens.

Documentation and upkeep Nemotron 3.5 Lightning 30B A3B +8

LFM3-1.7B 67

Model card 17, Intended use (local agents, tool calling, structured outputs, fine-tuning), a limitation (not recommended for agentic coding or complex multi-step reasoning), architecture (24 layers: 13 gated short convolutions, 5 sliding-window and 6 global attention), parameters (1.73B), context (256K) and 16 languages. Training data 5, A general description: 22T tokens of pre-training in two stages with the kinds of data added since LFM2, 1.75T tokens of supervised fine-tuning, then mixed reinforcement learning, distillation from six specialist teachers and agentic reinforcement learning. Last change 20, the last commit, on 9 November 2026, added the OpenVINO checkpoint to the card's inference table, a day before this check. Responsiveness 10, Of the 22 discussions that aren't pull requests (27 October to 8 November 2026), 7 have a reply from a LiquidAI member, which is some. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 10, Config, template and card agree on the lfm3 architecture, the 262,144-token context and the thinking switch. 17 + 5 + 20 + 10 + 5 + 10 = 67.

Nemotron 3.5 Lightning 30B A3B 75

The model card earns 20, all seven items with limitations in the linked subcard. Training data earns 20, datasets listed with sources and token counts, cut-offs and filtering, and the corpora published. Last change earns 20, counting NVIDIA's own inference code as for the other Nemotron listings. The repositories last changed on 10 September, 53 days ago, and TensorRT-LLM, which the card's serving section runs, changed its Nemotron-H model code on 14 October, 19 days ago. Responsiveness earns 5, one NVIDIA reply across 14 questions. Version policy earns 5 as a first release. File health earns 5, since reports about the card's recipes wait without a reply and the llama.cpp recipe names a quantisation the linked repository doesn't hold.

Score by category

CategoryWeight this runLFM3-1.7BNemotron 3.5 Lightning 30B A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258585even
Risk20%204075Nemotron 3.5 Lightning 30B A3B +35
Agent interface10%1010090LFM3-1.7B +10
Documentation and upkeep10%106775Nemotron 3.5 Lightning 30B A3B +8
Negative events≤1500
TotalC 61/100B 64.7/100

Facts side by side

FactLFM3-1.7BNemotron 3.5 Lightning 30B A3B
KindOpen-weight modelOpen-weight model
VendorLiquid AINVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceLFM Open License v1.0 (free commercial use below $10M annual revenue)OpenMDW-1.1
Read-only variant documentednono
llms.txtyesno
Last release2026-11-092026-08-11
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

LFM3-1.7B

A 1.73B model that fits an 8 GB machine with room to spare, with a documented tool-call format, deferred tools, a thinking switch and a 256K context. It runs today in llama.cpp, Ollama and LM Studio only, loads in Transformers through repository code, and has no safety results, security contact or data sources.

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

LFM3-1.7B

  1. Start it with llama-server -hf LiquidAI/LFM3-1.7B-GGUF:Q4_K_M --jinja or ollama run lfm3
  2. Use temperature 0.1, top_k 50 and repetition penalty 1.1 for chat, tools and agents, per the card
  3. Pass enable_thinking=False for direct answers, and expect it to reason anyway on hard tasks
  4. For a large tool catalogue mark tools defer_loading and give it a search tool
  5. Don't plan on vLLM or SGLang until a release carries LFM3
  6. Liquid doesn't recommend it for agentic coding or complex multi-step reasoning

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, LFM3-1.7B or Nemotron 3.5 Lightning 30B A3B?

Nemotron 3.5 Lightning 30B A3B scores 64.7 (B) on agent readiness against LFM3-1.7B's 61 (C), and leads in 2 of 4 scored categories. LFM3-1.7B leads on agent interface.

Other comparisons with LFM3-1.7B 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.