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

Hy-Memory-30B-A3B vs LFM3-1.7B

Hy-Memory-30B-A3B and LFM3-1.7B score within a point of each other on agent readiness, 61 (C) and 61 (C). 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 4969 open weights comparisons

Which one, for what

Hy-Memory-30B-A3B C

Best for Agents with an external memory framework that want a local model for the write path on a 24 GB card

Ahead on

  • Risk, 60 against 40

Watch for

Not a general assistant or a tool caller

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 65

Watch for

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

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.

Agent interface LFM3-1.7B +35

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

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.

Risk Hy-Memory-30B-A3B +20

Hy-Memory-30B-A3B 60

File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

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.

Score by category

CategoryWeight this runHy-Memory-30B-A3BLFM3-1.7BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258585even
Risk20%206040Hy-Memory-30B-A3B +20
Agent interface10%1065100LFM3-1.7B +35
Documentation and upkeep10%106867Hy-Memory-30B-A3B +1
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactHy-Memory-30B-A3BLFM3-1.7B
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)Liquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0LFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-162026-11-09
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

Verdicts

Hy-Memory-30B-A3B

A specialist that writes an agent's long-term memory, built to slot into Mem0, MemOS or Tencent's own framework in place of a general model. It fits a 24 GB card from Tencent's own GGUF, under plain Apache 2.0, and Tencent answers on the repository. Its results are Tencent's own and nobody has rerun them.

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.

Before you call either

Hy-Memory-30B-A3B

  1. Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
  2. Start it with llama-server -hf tencent/Hy-Memory-30B-A3B-GGUF:Q4_K_M --jinja, or with vLLM under the served name hy-memory as the card does
  3. Pass reasoning_effort as no_think in chat_template_kwargs and temperature 0, as the card's example does
  4. Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
  5. Treat what it stores as unverified. It keeps what a conversation says, true or not

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

Questions

Which is better for AI agents, Hy-Memory-30B-A3B or LFM3-1.7B?

Hy-Memory-30B-A3B and LFM3-1.7B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-1.7B leads on agent interface.

Other comparisons with Hy-Memory-30B-A3B or LFM3-1.7B

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.