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

LFM3-1.7B vs Qwen3-30B-A3B-Instruct-2507

LFM3-1.7B scores 61 (C) on agent readiness against Qwen3-30B-A3B-Instruct-2507's 56.6 (C), and leads in 2 of 4 scored categories. Qwen3-30B-A3B-Instruct-2507 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 75
  • Documentation and upkeep, 67 against 26

Watch for

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

Qwen3-30B-A3B-Instruct-2507 C

Best for Agents that want an instruct model with tool calling on one 24 GB GPU or a 32 GB Mac, with a plain licence and a 262,144-token context.

Ahead on

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

Watch for

No safety results, prompt-injection guidance or security contact

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.

Documentation and upkeep LFM3-1.7B +41

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.

Qwen3-30B-A3B-Instruct-2507 26

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, named languages and a knowledge cut-off aren't. Training data 5, the cited Qwen3 report describes the data in general terms without a cut-off. Last change 0, the files and card last changed on 17 September 2025 (Hub lastModified on 4 November), and QwenLM/Qwen3's commits since are documentation only (the newest 8 January 2026). Responsiveness 0, counted by script on 4 November, with 32 discussions, 23 not pull requests (the newest 18 June 2026), and the only reply from a Qwen organisation member is Haihao's on discussion 3 (30 July 2025), who isn't counted as the publisher's staff (the ehartford and danielhanchen reading). Version policy 5, the older Qwen3-30B-A3B stays in its own repository without a note. File health 5, the files agree with the card but reports about the 1M mode wait without a reply. 11 + 5 + 0 + 0 + 5 + 5 = 26.

Agent interface LFM3-1.7B +25

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.

Qwen3-30B-A3B-Instruct-2507 75

Chat template 20, a Jinja template in tokenizer_config.json. Tool-calling format 25, Qwen's own Function Calling guide documents the Hermes-style declaration and how calls come back, and names vLLM's hermes parser. Trained tool calling 20, the template allows one or more calls a turn. Structured output 0, not documented for the model, and Qwen's docs only point to vLLM's generic guided decoding. Reasoning control 0, this edition has no thinking. Context 10, 262,144 tokens native, with the 1M mode not counted. Template and config unchanged on 4 November. 20 + 25 + 20 + 0 + 0 + 10 = 75.

Risk Qwen3-30B-A3B-Instruct-2507 +15

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.

Qwen3-30B-A3B-Instruct-2507 55

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, plain Apache 2.0 whose only change was the copyright year before release. Security programme 0, no security.txt, disclosure policy or security contact for Qwen was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent. Files unchanged on 4 November, and QwenLM/Qwen3 still has no SECURITY.md. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Reach Qwen3-30B-A3B-Instruct-2507 +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.

Qwen3-30B-A3B-Instruct-2507 90

Memory 25 of 30, LM Studio's MLX 4-bit build is 17.2 GB and Ollama's 4-bit build 19 GB, 21 to 23 GB with a fifth added, which fits 24 GB. Runtimes 25, released Transformers, vLLM, SGLang and llama.cpp run the qwen3_moe architecture, and Ollama's library and LM Studio's catalogue carry it. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, Featherless AI on Hugging Face plus DekaLLM and SiliconFlow on OpenRouter serve it. On 4 November both repositories were still ungated with no file changed since 17 September 2025, and Featherless AI was still live in the Hub's provider mapping (OpenRouter's providers per 21 October). 25 + 25 + 10 + 15 + 10 + 5 = 90.

Score by category

CategoryWeight this runLFM3-1.7BQwen3-30B-A3B-Instruct-2507Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258590Qwen3-30B-A3B-Instruct-2507 +5
Risk20%204055Qwen3-30B-A3B-Instruct-2507 +15
Agent interface10%1010075LFM3-1.7B +25
Documentation and upkeep10%106726LFM3-1.7B +41
Negative events≤1500
TotalC 61/100C 56.6/100

Facts side by side

FactLFM3-1.7BQwen3-30B-A3B-Instruct-2507
KindOpen-weight modelOpen-weight model
VendorLiquid AIAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceLFM Open License v1.0 (free commercial use below $10M annual revenue)Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-11-092025-09-17
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/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.

Qwen3-30B-A3B-Instruct-2507

A general-purpose instruct model with 3.3B of 30.5B parameters active per token, for instruction following, tool calling and long documents without a thinking step. It needs about 21 to 23 GB at 4 bits under Apache 2.0, and providers host it. Its files haven't changed in over a year, Alibaba hasn't answered its discussions, and no safety results are published.

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

Qwen3-30B-A3B-Instruct-2507

  1. Quickest start is ollama run qwen3:30b-instruct, 19 GB. Plain qwen3:30b and qwen3:30b-a3b are the Thinking-2507 edition, not this one
  2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-30B-A3B-Instruct-2507 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser hermes, 61 GB of weights fits the GPU share
  3. Use the hermes parser in vLLM or qwen25 in SGLang, the template emits JSON inside tool_call tags
  4. Don't pass enable_thinking, this edition never thinks and the card says the flag isn't needed
  5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and min_p 0, with presence_penalty up to 2 against repetition
  6. Leave config.json as it is unless you need more than 262,144 tokens, the 1M mode swaps in config_1m.json and runs one sequence at a time
  7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented

Questions

Which is better for AI agents, LFM3-1.7B or Qwen3-30B-A3B-Instruct-2507?

LFM3-1.7B scores 61 (C) on agent readiness against Qwen3-30B-A3B-Instruct-2507's 56.6 (C), and leads in 2 of 4 scored categories. Qwen3-30B-A3B-Instruct-2507 leads on reach and risk.

Other comparisons with LFM3-1.7B or Qwen3-30B-A3B-Instruct-2507

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.