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

Apodex-1.1-mini vs LFM3-Audio-2B

Apodex-1.1-mini and LFM3-Audio-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-Audio-2B leads on documentation and upkeep. 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

Apodex-1.1-mini C

Best for Long-running agent tasks with tools on a 32 GB GPU or Mac, or through Apodex's API, under a plain licence

Ahead on

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

Watch for

No safety results, and agent guidance only from the harness

LFM3-Audio-2B C

Best for Voice agents on a laptop or phone that need speech in, speech out and tool calls from one small model

Ahead on

  • Documentation and upkeep, 52 against 38

Watch for

Only llama.cpp and Ollama run it in a release, though the card lists vLLM and SGLang

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 Apodex-1.1-mini +25

Apodex-1.1-mini 65

File safety 25, safetensors and GGUF only and nothing from the repositories runs. Provenance 15, the files are in the apodex organisation its site links to, with a SHA-256 for every weight file and a SHA256SUMS file for the GGUF. Safety evaluation 0, none published. Agent guidance 5, the recommended harness documents approval gates and a sandbox boundary, but nothing on prompt injection or refusals for the model. Licence risk 15, Apache 2.0 from Qwen3.5-35B-A3B through to this model with no conditions added. Security programme 5, the harness has a disclosure policy with a private address, with no route shown for the weights.

LFM3-Audio-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.

Documentation and upkeep LFM3-Audio-2B +14

Apodex-1.1-mini 38

Model card 8, it covers intended use, context and languages but not the architecture, parameters, limitations or a knowledge cut-off. Training data 5, a general description with no cut-off. Last change 15, the GGUF build went up on 10 September 2026, 54 days before 3 November. Responsiveness 0, Apodex answered none of the four discussions, unchanged on 3 November 2026. Version policy 5, 1.0-mini stays in its own repository without a note. File health 5, the files agree, but the card's agent example is broken and reports wait without a reply.

LFM3-Audio-2B 52

Model card 17, Intended use (local agents, tool calling, structured outputs, fine-tuning), limitations (not recommended for agentic coding or complex multi-step reasoning, voice chat in English only), an architecture section, parameters (2B), context (32K) and 19 speech languages and locales. 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 31 October, edited the card. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (27 and 31 October 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. 17 + 5 + 20 + 0 + 5 + 5 = 52.

Reach Apodex-1.1-mini +5

Apodex-1.1-mini 85

Memory 20, Apodex's Q4_K_M GGUF with its vision projector is 22.6 GB and needs about 27.1 GB with the fifth added, so 32 GB, as do its NVFP4 and GPTQ-Int4 builds. Runtimes 20, the Qwen3.5 MoE architecture runs in released vLLM, SGLang, Transformers and llama.cpp, while Ollama's and LM Studio's entries are the base's, not this model's. Builds 15, Apodex publishes FP8, NVFP4, GPTQ-Int4 and GGUF. Terms 15, Apache 2.0 with nothing added. Download 10, nothing is gated. Hosted 5, Apodex's own API serves it.

LFM3-Audio-2B 80

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.17 GB projector file, and 1.27 GB × 1.2 = 1.5 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 audio projector and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example that starts this model), and Ollama's library has an lfm3-audio 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-audio-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.

Score by category

CategoryWeight this runApodex-1.1-miniLFM3-Audio-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258580Apodex-1.1-mini +5
Risk20%206540Apodex-1.1-mini +25
Agent interface10%108585even
Documentation and upkeep10%103852LFM3-Audio-2B +14
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApodex-1.1-miniLFM3-Audio-2B
KindOpen-weight modelOpen-weight model
VendorApodex AILiquid 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-08-252026-11-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3.3/5 (4)none

Verdicts

Apodex-1.1-mini

An agent cousin fine-tuned from Qwen3.5-35B-A3B for long tasks with files, code and tools, with parallel tool calling and about 3B active parameters. It needs 32 GB for Apodex's GGUF, NVFP4 or GPTQ-Int4 builds or about 86 GB in BF16, and Apodex's API serves it too. The main risks are no safety results and no replies from the publisher.

LFM3-Audio-2B

A 2B model that listens and speaks on an 8 GB machine, transcribes and translates 19 languages and turns spoken requests into tool calls. Only llama.cpp and Ollama run it in a release. The context is 32K, voice chat is English only, Liquid hasn't answered the repository's questions, and there are no safety results or data sources.

Before you call either

Apodex-1.1-mini

  1. Serve it with vllm serve apodex/Apodex-1.1-mini --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser qwen3, or the same parsers in SGLang, so tool calls and reasoning come back parsed
  2. For llama.cpp, llama-server -hf apodex/Apodex-1.1-mini-GGUF:Q4_K_M --jinja --reasoning-format deepseek, and the card passes the repository's chat_template.jinja with --chat-template-file
  3. Pass tools through the API's tools parameter rather than in the system prompt, as the card asks
  4. The card recommends temperature 1.0, top_p 0.95, repetition_penalty 1.05 and max_tokens up to 32,768
  5. Send your own system prompt, or set identity_mode, since the template otherwise adds an Apodex identity block
  6. The template keeps all earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  7. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  8. The card's Python example has a broken line where it runs the tool (available_toolsname), so fix it to available_tools[name](**args) before running
  9. Validate JSON output yourself, since structured output isn't documented

LFM3-Audio-2B

  1. Start it with llama-server -hf LiquidAI/LFM3-Audio-2B-GGUF:Q4_K_M --jinja or ollama run lfm3-audio
  2. llama.cpp ships examples/realtime_client.py for live speech with this model
  3. Prefill the assistant turn with an open think tag to let it reason before a text reply
  4. The context is 32K
  5. Voice chat is English only, while transcription, synthesis and translation cover 19 languages and locales
  6. Liquid doesn't recommend it for agentic coding or complex multi-step reasoning

Questions

Which is better for AI agents, Apodex-1.1-mini or LFM3-Audio-2B?

Apodex-1.1-mini and LFM3-Audio-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-Audio-2B leads on documentation and upkeep.

Other comparisons with Apodex-1.1-mini or LFM3-Audio-2B

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.