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

LFM3-1.7B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB

LFM3-1.7B and NVIDIA Nemotron 3.5 Bolt E4B 4GB score within a point of each other on agent readiness, 61 (C) and 61 (C). NVIDIA Nemotron 3.5 Bolt E4B 4GB leads on reach and risk. 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 85

Watch for

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

NVIDIA Nemotron 3.5 Bolt E4B 4GB C

Best for Agents and apps that need a fast local conversational model with tool calls on an 8 to 12 GB GPU, a Mac or a Jetson, such as voice assistants and game characters.

Ahead on

  • Reach, 90 against 85
  • Risk, 80 against 40

Watch for

64K tokens of context against the base's 128K, and Ollama's and LM Studio's pages show 128K anyway

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 NVIDIA Nemotron 3.5 Bolt E4B 4GB +40

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.

NVIDIA Nemotron 3.5 Bolt E4B 4GB 80

File safety earns 25, safetensors and GGUF only, and the documented routes run no repository code (an undocumented Inference Endpoints handler.py sits in the BF16 repository). Provenance earns 15, NVIDIA's linked organisation with a hash for every file. Safety evaluation earns 0, since NVIDIA names its content-safety and bias datasets but publishes no results. Agent guidance earns 15, for instruction-hierarchy training NVIDIA documents and a subcard on prompt injection and the safeguards to add. Licence risk keeps all 15 under OpenMDW-1.1 and Apache 2.0. The security programme earns 10 for the card's reporting route and NVIDIA's public bulletins.

Agent interface LFM3-1.7B +15

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.

NVIDIA Nemotron 3.5 Bolt E4B 4GB 85

The chat template earns 20, a Jinja file in the repository and the GGUF. The tool-calling format earns 25, with OpenAI-style tools, the gemma4 parser named and an asynchronous pattern documented. Trained tool calling earns 20, multi-step tool-use training and several calls per turn. Structured output earns 5, trained but with no instructions. Reasoning control earns 10, thinking per request, the reasoning returned apart and a budget. Context earns 5 for 64K, half the base's 128K.

Reach NVIDIA Nemotron 3.5 Bolt E4B 4GB +5

LFM3-1.7B 85

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB, and 1.10 GB × 1.2 = 1.3 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture (src/models/lfm3.cpp at b12242), Ollama's library has an lfm3 entry, and LM Studio's catalogue runs the architecture (its liquid/lfm3-vl-2b entry; lmstudio-community publishes a GGUF of this model). Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-1.7b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.

NVIDIA Nemotron 3.5 Bolt E4B 4GB 90

Memory earns 30, since NVIDIA's Q4_K_M GGUF is 6.18 GB, 7.4 GB with a fifth added. Runtimes earn the full 25 from released llama.cpp, vLLM, Transformers, SGLang, Ollama and LM Studio. Builds earn 10, as NVIDIA's only quantised build is the Q4_K_M GGUF and the DFlash repositories are drafters. Terms earn 10, because OpenMDW-1.1 is permissive with no threshold or use policy but isn't an OSI licence, and the Gemma 4 base adds plain Apache 2.0. Download earns 10, with no gate. Hosted earns 5, as NVIDIA's own API serves it.

Score by category

CategoryWeight this runLFM3-1.7BNVIDIA Nemotron 3.5 Bolt E4B 4GBEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258590NVIDIA Nemotron 3.5 Bolt E4B 4GB +5
Risk20%204080NVIDIA Nemotron 3.5 Bolt E4B 4GB +40
Agent interface10%1010085LFM3-1.7B +15
Documentation and upkeep10%106765LFM3-1.7B +2
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactLFM3-1.7BNVIDIA Nemotron 3.5 Bolt E4B 4GB
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-10-23
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone4/5 (4)

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.

NVIDIA Nemotron 3.5 Bolt E4B 4GB

A small cousin for voice and device assistants, game characters and robot interfaces, trained for multi-turn tool calls, instruction hierarchy and short spoken replies, with thinking switchable per request. NVIDIA's Q4_K_M GGUF needs about 8 GB, and Ollama and LM Studio carry it. Context is 64K, half the Gemma 4 base, and NVIDIA publishes no safety results.

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

NVIDIA Nemotron 3.5 Bolt E4B 4GB

  1. Quickest start is ollama run nemotron-3.5-bolt:e4b, about 8 GB of files, and set num_ctx to 65536 or less, since NVIDIA supports 64K
  2. With NVIDIA's GGUF use llama-server -m Nemotron-3.5-Bolt-E4B-Q4_K_M.gguf -c 65536 -ngl 999 --jinja, and add --reasoning on --reasoning-budget <tokens> to cap thinking
  3. With vLLM 0.31.0 or later pass --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4 and the repository's chat_template.jinja
  4. Pass enable_thinking explicitly in chat_template_kwargs, since the template defaults to off whatever the card says, and set skip_special_tokens false as the card's examples do
  5. Use temperature=1.0 and top_p=0.95 in both modes, as the card says
  6. Set conversational_mode true for spoken replies, which appends a brevity instruction to the system prompt
  7. Answer a slow tool at once with a pending tool message, then send the result later as a user message starting TOOL RESULT, as the card's asynchronous pattern says
  8. Keep persistent rules in the system prompt and send state updates as separate user or system messages in order, per the card's prompting guidelines

Questions

Which is better for AI agents, LFM3-1.7B or NVIDIA Nemotron 3.5 Bolt E4B 4GB?

LFM3-1.7B and NVIDIA Nemotron 3.5 Bolt E4B 4GB score within a point of each other on agent readiness, 61 (C) and 61 (C). NVIDIA Nemotron 3.5 Bolt E4B 4GB leads on reach and risk.

Other comparisons with LFM3-1.7B or NVIDIA Nemotron 3.5 Bolt E4B 4GB

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.