LFM3-Audio-2B vs Swift 1.5 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.

Swift 1.5 Qwen3.8-27B 60

Chat template 20, the base's Jinja file. Tool-calling format 10 of 25, the format is only in the template and the parser only in serving commands. Trained tool calling 20, several calls a turn and agentic post-training. Structured output 0, not documented. Reasoning control 0, the card mentions reasoning_effort but not how to set it, turn thinking off or read the reasoning. Context 10, 262,144 tokens native.

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.

Swift 1.5 Qwen3.8-27B 50

File safety 25, safetensors only and nothing from the repository runs. Provenance 15, the files are in the account UkisAI's site 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 10, a revenue threshold. Security programme 0, no way to report a flaw was found.

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.

Swift 1.5 Qwen3.8-27B 43

Model card 8 of 20, intended use, parameters and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI's own ONNX builds of the model took a new card and licence on 8 October, 26 days ago (the main repository's last commit is the 3 October README update). Responsiveness 0, UkisAI answered none of 8 discussions. Version policy 5, Swift 1.0 stays in its own repository without a note. File health 5, reports of a broken model wait without a reply and the card's metadata claims a gate that doesn't exist.