Head to head · Open-weight models you run yourself · October 2026 research run
Hy3 vs LFM3-Omni-2B
Hy3 scores 62.6 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in 3 of 4 scored categories. LFM3-Omni-2B leads on reach. 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
Hy3 B
Best for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0
Ahead on
- Risk, 60 against 40
- Agent interface, 75 against 70
- Documentation and upkeep, 56 against 49
Watch for
597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build
Best for Voice and camera agents on a laptop or phone that want one small model for hearing, seeing, speaking and calling tools
Ahead on
- Reach, 80 against 70
Watch for
Only llama.cpp and Ollama run it in a release
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 Hy3 +20
Hy3 60
File safety earns the full 25, safetensors only with no pickle files, and the documented route runs vLLM or SGLang from their own code with a Jinja template, so nothing from the repository runs at load or prompt time. Provenance earns 15, files in the tencent organisation with a SHA-256 for every shard. Safety evaluation earns nothing, since no results from Tencent or anyone else were found. Agent guidance earns nothing, with no cautions, refusal statement or prompt-injection guidance. Licence risk keeps all 15 under plain Apache 2.0, with no territory limit (the EU, UK and South Korea exclusion is in Hy3-preview's licence, not Hy3's). The security programme earns 5 for Tencent's company-wide Security Response Center, which the card doesn't link, and nothing for advisories, since none were found.
LFM3-Omni-2B 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.
Reach LFM3-Omni-2B +10
Hy3 70
Memory earns 5, because the smallest build of 4-bit precision or better is AngelSlim's GPTQ-Int4 of 168.5 GB, about 202 GB with the fifth added, which is within 256 GB but beyond any single workstation. The 1-bit IQ1_M GGUF fits our reference machine but sits below the 4-bit line. Runtimes earn 20, for model code in released Transformers, vLLM, SGLang and llama.cpp; Ollama and LM Studio have no entry for it. Builds earn the full 15, with Tencent's FP8 repository and AngelSlim's GPTQ and GGUF builds. Terms earn 15 for plain Apache 2.0. Download earns 10, with no gate and no account. Hosted earns 5, since Featherless AI and DeepInfra serve it live through Hugging Face.
LFM3-Omni-2B 80
Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. 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-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.
Documentation and upkeep Hy3 +7
Hy3 56
The model card earns 11, covering intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off. Training data earns 5 for a general statement with no cut-off. The last change earns 10, a config.json edit on 20 July and AngelSlim uploads on 21 July, within 180 days on 2 November 2026; the line drops to 5 after 17 January 2027 unless the files change. Responsiveness earns 10, with Tencent replies on 7 of 19 discussions and none since 22 July. Version policy earns the full 10, since the preview stays in its own repository and the card dates it and says what changed. File health earns 10, with files that agree and no broken-file report waiting.
LFM3-Omni-2B 49
Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.
Agent interface Hy3 +5
Hy3 75
The chat template earns 20, a chat_template.jinja in the repository. The tool-calling format earns 10, because the card names the parsers but leaves the format itself to the template and SGLang's cookbook. Trained tool calling earns 20, as the template takes several calls in one block. Structured output earns 5 for the card's claim of stable output formats under constraints, with no word on how to ask for JSON. Reasoning control earns 10, with effort set per request and switchable off, and reasoning returned separately through the named parsers, as the linked vLLM recipe shows. Context earns 10 for 262,144 tokens native.
LFM3-Omni-2B 70
Chat template 20, chat_template.jinja in the repository (13,513 characters), with roles, images, video and audio, tools, deferred tools and tool results. 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 documents tool calling from spoken or written requests. Structured output 0, the card doesn't mention JSON or structured output for this model. Reasoning control 0, the card says this is a non-reasoning model and that enable_thinking=True is not supported, so there is no thinking to turn off or budget. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 0 + 0 + 5 = 70.
Score by category
| Category | Weight this run | Hy3 | LFM3-Omni-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 70 | 80 | LFM3-Omni-2B +10 |
| Risk | 20%20 | 60 | 40 | Hy3 +20 |
| Agent interface | 10%10 | 75 | 70 | Hy3 +5 |
| Documentation and upkeep | 10%10 | 56 | 49 | Hy3 +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.6/100 | C 61/100 |
Facts side by side
| Fact | Hy3 | LFM3-Omni-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | Liquid AI |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | LFM Open License v1.0 (free commercial use below $10M annual revenue) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-07-20 | 2026-11-03 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.8/5 (4) | none |
Verdicts
Hy3
Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.
LFM3-Omni-2B
One 2.17B model that sees, listens and talks on an 8 GB machine and turns spoken requests into tool calls. Only llama.cpp and Ollama run it in a release. The context is 32K, it doesn't reason, Liquid hasn't answered a question on the repository, and there are no safety results or data sources.
Before you call either
Hy3
- Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
- In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
- Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
- With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
- Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
- Use temperature 0.9 and top_p 1.0, the card's recommended sampling
- On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
- Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers
LFM3-Omni-2B
- Start it with
llama-server -hf LiquidAI/LFM3-Omni-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-omni - Greedy decoding for text. For speech use audio_temperature 0.4 and audio_repetition_penalty 1.2, per the card
- The context is 32K, and llama.cpp samples video at 2 frames a second up to 384 frames
- Parse tool calls yourself from the XML it returns
- It doesn't reason, so don't pass enable_thinking
- Validate JSON output yourself
Questions
Which is better for AI agents, Hy3 or LFM3-Omni-2B?
Hy3 scores 62.6 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in 3 of 4 scored categories. LFM3-Omni-2B leads on reach.
Other comparisons with Hy3 or LFM3-Omni-2B
- Agents-A1-4B vs Hy3
- Agents-A1-4B vs LFM3-Omni-2B
- Apertus v1.5 8B vs Hy3
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apodex-1.1-mini vs Hy3
- Apodex-1.1-mini vs LFM3-Omni-2B
- Arete-27B vs Hy3
- Arete-27B vs LFM3-Omni-2B
- BigBang-v1 vs Hy3
- BigBang-v1 vs LFM3-Omni-2B
- Carbon-X vs Hy3
- Carbon-X vs LFM3-Omni-2B
- Cosmos-Reason2-2B vs Hy3
- Cosmos-Reason2-2B vs LFM3-Omni-2B
- Darwin-36B-Opus vs Hy3
- Darwin-36B-Opus vs LFM3-Omni-2B
- DeepSeek-V3.2 vs Hy3
- DeepSeek-V3.2 vs LFM3-Omni-2B
- DeepSeek V4.1 Flash vs Hy3
- DeepSeek V4.1 Flash vs LFM3-Omni-2B
- DeepSeek-V4-Flash-0731 vs Hy3
- DeepSeek-V4-Flash-0731 vs LFM3-Omni-2B
- DiffusionGemma 26B A4B IT vs Hy3
- DiffusionGemma 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 12B IT vs Hy3
- Gemma 4 12B IT vs LFM3-Omni-2B
- Gemma 4 26B A4B IT vs Hy3
- Gemma 4 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 31B IT vs Hy3
- Gemma 4 31B IT vs LFM3-Omni-2B
- Gemma 4 E2B IT vs Hy3
- Gemma 4 E2B IT vs LFM3-Omni-2B
- Gemma 4 E4B IT vs Hy3
- Gemma 4 E4B IT vs LFM3-Omni-2B
- GLM-4.5-Air vs Hy3
- GLM-4.5-Air vs LFM3-Omni-2B
- GLM-4.7-Flash vs Hy3
- GLM-4.7-Flash vs LFM3-Omni-2B
- GLM-5.3-Flash vs Hy3
- GLM-5.3-Flash vs LFM3-Omni-2B
- GLM-5.3 vs Hy3
- GLM-5.3 vs LFM3-Omni-2B
- gpt-oss-120b vs Hy3
- gpt-oss-120b vs LFM3-Omni-2B
- gpt-oss-20b vs Hy3
- gpt-oss-20b vs LFM3-Omni-2B
- Granite 4.2 30B vs Hy3
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 3B vs Hy3
- Granite 4.2 3B vs LFM3-Omni-2B
- Granite 4.2 8B vs Hy3
- Granite 4.2 8B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy3 vs Inkling
- Hy3 vs Inkling-Small
- Hy3 vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy3 vs Kimi K3
- Hy3 vs Kimi K3.1 Pro
- Hy3 vs Kolibri-1
- Hy3 vs Kronos
- Hy3 vs Laguna M.1
- Hy3 vs Laguna S 2.1
- Hy3 vs Laguna XS 2.1
- Hy3 vs LBS-27B
- Hy3 vs LFM2.5-2.6B
- Hy3 vs LFM3-1.7B
- Hy3 vs LFM3-Audio-2B
- Hy3 vs LFM3-VL-2B
- Hy3 vs Ling-3.0-tiny
- Hy3 vs Ling-3.1-flash-1019
- Hy3 vs MiMo-V2.6 Distill Qwen 9B
- Hy3 vs MiniCPM-o 4.5
- Hy3 vs MiniCPM-V 4.7 1B
- Hy3 vs MiniCPM-V 4.7 35B-A3B
- Hy3 vs MiniCPM5-2B
- Hy3 vs MiniMax-M2.5
- Hy3 vs MiniMax-M2.7
- Hy3 vs MiniMax-M3.1-Flash
- Hy3 vs Mistral Large 4
- Hy3 vs Muse Glimmer 30B
- Hy3 vs Nanbeige4.3-33B
- Hy3 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Hy3 vs Nemotron 3.5 Lightning 30B A3B
- Hy3 vs Nemotron 3 Nano 30B A3B
- Hy3 vs Nemotron 3 Nano 4B
- Hy3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy3 vs Nemotron 3 Super 120B A12B
- Hy3 vs Nemotron 3 Ultra 550B A55B
- Hy3 vs occamy-1.0
- Hy3 vs Olmo 3 7B Think
- Hy3 vs Ornith-1.5-122B
- Hy3 vs Ornith-1.5-35B-A3B
- Hy3 vs Ornith-1.5-397B
- Hy3 vs Ornith-1.5-9B
- Hy3 vs Qwen-AgentWorld-35B-A3B
- Hy3 vs Qwen3-30B-A3B-Instruct-2507
- Hy3 vs Qwen3-4B-Instruct-2507
- Hy3 vs Qwen3.5-0.8B
- Hy3 vs Qwen3.5-122B-A10B
- Hy3 vs Qwen3.5-2B
- Hy3 vs Qwen3.5-397B-A17B
- Hy3 vs Qwen3.5-4B
- Hy3 vs Qwen3.5-9B
- Hy3 vs Qwen3.6-27B
- Hy3 vs Qwen3.6-35B-A3B
- Hy3 vs Qwen3.8-27B
- Hy3 vs Qwen3.8-Flash-Next
- Hy3 vs Qwen3-Coder-30B-A3B-Instruct
- Hy3 vs Qwen3-Coder-Next
- Hy3 vs Qwen3-Omni-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-2B-Instruct
- Hy3 vs Qwen3-VL-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-32B-Instruct
- Hy3 vs Qwen3-VL-4B-Instruct
- Hy3 vs Qwen3-VL-8B-Instruct
- Hy3 vs Qwopus3.8-27B-Flash-V2
- Hy3 vs Recursive Flint
- Hy3 vs Ripple-65B Preview
- Hy3 vs SmolLM3-3B
- Hy3 vs Spark-X2.6-4B
- Hy3 vs Swift 1.5 Qwen3.8-27B
- Hy3 vs Swift 1.5 Qwen3.8-Flash-Next
- Hy3 vs ThinkingCap (Qwen3.8 27B)
- Hy3 vs Baidu Unlimited-OCR-2
- Inkling-Small vs LFM3-Omni-2B
- Inkling vs LFM3-Omni-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-Omni-2B
- Kimi K3.1 Pro vs LFM3-Omni-2B
- Kimi K3 vs LFM3-Omni-2B
- Kolibri-1 vs LFM3-Omni-2B
- Kronos vs LFM3-Omni-2B
- Laguna M.1 vs LFM3-Omni-2B
- Laguna S 2.1 vs LFM3-Omni-2B
- Laguna XS 2.1 vs LFM3-Omni-2B
- LBS-27B vs LFM3-Omni-2B
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM3-1.7B vs LFM3-Omni-2B
- LFM3-Audio-2B vs LFM3-Omni-2B
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs Ling-3.0-tiny
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-Omni-2B vs MiniCPM-o 4.5
- LFM3-Omni-2B vs MiniCPM-V 4.7 1B
- LFM3-Omni-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-Omni-2B vs MiniCPM5-2B
- LFM3-Omni-2B vs MiniMax-M2.5
- LFM3-Omni-2B vs MiniMax-M2.7
- LFM3-Omni-2B vs MiniMax-M3.1-Flash
- LFM3-Omni-2B vs Mistral Large 4
- LFM3-Omni-2B vs Muse Glimmer 30B
- LFM3-Omni-2B vs Nanbeige4.3-33B
- LFM3-Omni-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-Omni-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 4B
- LFM3-Omni-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-Omni-2B vs Nemotron 3 Super 120B A12B
- LFM3-Omni-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-Omni-2B vs occamy-1.0
- LFM3-Omni-2B vs Olmo 3 7B Think
- LFM3-Omni-2B vs Ornith-1.5-122B
- LFM3-Omni-2B vs Ornith-1.5-35B-A3B
- LFM3-Omni-2B vs Ornith-1.5-397B
- LFM3-Omni-2B vs Ornith-1.5-9B
- LFM3-Omni-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-Omni-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-Omni-2B vs Qwen3-4B-Instruct-2507
- LFM3-Omni-2B vs Qwen3.5-0.8B
- LFM3-Omni-2B vs Qwen3.5-122B-A10B
- LFM3-Omni-2B vs Qwen3.5-2B
- LFM3-Omni-2B vs Qwen3.5-397B-A17B
- LFM3-Omni-2B vs Qwen3.5-4B
- LFM3-Omni-2B vs Qwen3.5-9B
- LFM3-Omni-2B vs Qwen3.6-27B
- LFM3-Omni-2B vs Qwen3.6-35B-A3B
- LFM3-Omni-2B vs Qwen3.8-27B
- LFM3-Omni-2B vs Qwen3.8-Flash-Next
- LFM3-Omni-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-Coder-Next
- LFM3-Omni-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-2B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-32B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-4B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-8B-Instruct
- LFM3-Omni-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-Omni-2B vs Recursive Flint
- LFM3-Omni-2B vs Ripple-65B Preview
- LFM3-Omni-2B vs SmolLM3-3B
- LFM3-Omni-2B vs Spark-X2.6-4B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-Omni-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-Omni-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/hy3-vs-lfm3-omni-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy3.json·/api/v1/tools/lfm3-omni-2b.json - From a terminal
anchor compare hy3 lfm3-omni-2b(the CLI) - Over MCP
compare_tools {"a": "hy3", "b": "lfm3-omni-2b"}at/mcp, no key