LFM3-Audio-2B vs ThinkingCap (Qwen3.8 27B)

LFM3-Audio-2B 85

Chat template 20, chat_template.jinja in the repository (9,328 characters), with roles, 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 names turning spoken requests into tool calls as one of its four uses. Structured output 5, the card says the model is designed for structured outputs without saying how to ask for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, the card documents reasoning per request for text replies: the caller prefills the assistant turn with an open think tag to let the model reason, or a closed one for a direct answer, with a use_thinking example. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 5 + 10 + 5 = 85.

ThinkingCap (Qwen3.8 27B) 70

Chat template 20, the same Jinja template as Qwen3.8-27B, in the repository. Tool-calling format 10 of 25, the card names the parsers but the format lives only in the template. Trained tool calling 20, several calls a turn, and BottleCap evaluated agent tasks. Structured output 0, not documented. Reasoning control 10, reasoning_effort budgets thinking per request and the card says where the reasoning comes back. Context 10, 262,144 tokens.

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.

ThinkingCap (Qwen3.8 27B) 75

Memory 25 of 30, BottleCap's IQ4_XS GGUF is 15.5 GB, 18.6 GB with a fifth added, which fits 24 GB. Runtimes 20, it keeps the base's qwen3_5 architecture, which llama.cpp, vLLM, SGLang and Transformers run in released versions, while Ollama's entry is the base's. Builds 15, FP8, NVFP4, MLX and GGUF from BottleCap. Terms 10, PolyForm Small Business is free commercially only below 100 people and 1,000,000 USD (2019) revenue. Download 5, the main repository is gated behind a click-through with an account and contact details, though the GGUF, NVFP4 and MLX builds aren't. Hosted 0, no API or inference provider serves it.

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.

ThinkingCap (Qwen3.8 27B) 45

File safety 25, safetensors only and no code in the repository. Provenance 10 of 15, the files are in BottleCap's verified organisation, but the Hub hides the gated files' SHA-256 from the public, so checksums couldn't be confirmed. Safety evaluation 0, none published. Agent guidance 0. Licence risk 10, 5 off for the size and revenue threshold. Security programme 0, no security.txt, disclosure policy or security contact.