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

Carbon-X vs LFM3-VL-2B

Carbon-X and LFM3-VL-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-VL-2B leads on agent interface and 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

Carbon-X C

Best for Agents that need a second opinion on DNA variants and regulatory regions on a 16 to 24 GB machine, without sending sequences to a hosted model.

Ahead on

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

Watch for

Not clinically validated and no wet-lab validation reported

LFM3-VL-2B C

Best for Agents on a laptop, phone or robot that need to read screens, documents, images and video from a model under 2 GB at 4 bits

Ahead on

  • Agent interface, 90 against 35
  • Documentation and upkeep, 77 against 72

Watch for

vLLM and SGLang support is unreleased, which the card says itself

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-VL-2B +55

Carbon-X 35

Chat template 20, a Jinja file in the repository. Tool-calling format 10, only the inherited template shows the format and no parser is named. Trained tool calling 0, nothing says it was trained to call tools. Structured output 0, not documented. Reasoning control 0, thinking can be switched off but was never trained, and the card asks you to keep it off. Context 5, 40,960 tokens from the base, though Hugging Face trained at 8,192 and under 16K. Most of what the card documents for agents is Carbon-X as a tool another model calls, which this checklist doesn't read.

LFM3-VL-2B 90

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, images and video, 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 its fine-tuning mix included tool calling and agentic traces. Structured output 5, the card's vLLM and SGLang commands set a structured-output backend and its fine-tuning table has a JSON extraction notebook, but nothing says how to ask this model for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, Liquid's chat-template page documents enable_thinking=False in apply_chat_template for LFM3, with reasoning on by default inside think tags, and the card documents preserve_thinking and reports a no-thinking configuration in its benchmarks. Context 10, 128K tokens of input and output per the card, and max_position_embeddings 128000 for the language model in config.json. 20 + 25 + 20 + 5 + 10 + 10 = 90.

Risk Carbon-X +25

Carbon-X 65

File safety 15, safetensors and GGUF only, but the documented loading path runs the repository's tokenizer.py through trust_remote_code. Provenance 15, the files are in HuggingFaceBio, which Hugging Face's GitHub repository links, with a checksum on every file. Safety evaluation 10, Hugging Face reports its own dual-use check on sequence editing in the launch post, without numbers or a harness. Agent guidance 5, general cautions only. Licence risk 15, plain Apache 2.0. Security programme 5, Hugging Face's security.txt is a reporting route, and public advisories couldn't be checked.

LFM3-VL-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 Carbon-X +5

Carbon-X 90

Memory 30, the publisher's Q4_K_M GGUF is 9.6 GB, or 11.6 GB with a fifth added. Runtimes 20, released llama.cpp (from b11742, which added the DNA tokenizer), vLLM, SGLang and Transformers all run it, with no Ollama or LM Studio entry. Builds 15, Hugging Face publishes GGUFs at four precisions. Terms 15, Apache 2.0 on the model and on its Qwen3-14B base. Download 10, nothing is gated. Hosted 0, no inference provider or Hugging Face API serves it.

LFM3-VL-2B 85

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.20 GB projector file, and 1.30 GB × 1.2 = 1.6 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture and the LFM3-VL projector (src/models/lfm3.cpp and tools/mtmd at b12242), Ollama's library has an lfm3-vl entry, and LM Studio's catalogue lists liquid/lfm3-vl-2b. 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-vl-2b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.

Documentation and upkeep LFM3-VL-2B +5

Carbon-X 72

Model card 17, everything but a knowledge cut-off. Training data 15, the mid-training sources and shares are listed, the instruction and fine-tuning data aren't named, and there's no cut-off. Last change 20, 28 October 2026, when config.json, generation_config.json, tokenizer_config.json and tokenizer.py were fixed. Responsiveness 10, organisation members replied to 2 of the 4 questions so far. Version policy 5, a first release whose history was squashed without a note. File health 5, the card now sends llama.cpp users to the publisher's GGUF repository, but the tokenizer config's 131,072 still contradicts the card's 40,960. 17 + 15 + 20 + 10 + 5 + 5 = 72.

LFM3-VL-2B 77

Model card 17, Intended use (questions about video, documents, charts and app screens, finding objects, spatial reasoning), a limitation (not recommended for coding, multi-turn conversations or complex reasoning), architecture (language model, 14-layer vision encoder and projector), parameters (1.92B), context (128K) and 16 languages. Training data 5, A general description: the base's 22T tokens of pre-training with the kinds of data added since LFM2, then vision mid-training on image and video data, supervised fine-tuning, vision reinforcement learning and distillation. Last change 20, the last commit, on 9 November 2026, added the OpenVINO checkpoint to the card's inference table, a day before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (27 to 31 October 2026), 3 have a reply from a LiquidAI member, which is most. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 10, Config, template and card agree on the lfm3_vl architecture, the 128,000-token context and the vision settings in processor_config.json. 17 + 5 + 20 + 20 + 5 + 10 = 77.

Score by category

CategoryWeight this runCarbon-XLFM3-VL-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259085Carbon-X +5
Risk20%206540Carbon-X +25
Agent interface10%103590LFM3-VL-2B +55
Documentation and upkeep10%107277LFM3-VL-2B +5
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactCarbon-XLFM3-VL-2B
KindOpen-weight modelOpen-weight model
VendorHugging Face (HuggingFaceBio)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-282026-11-09
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Carbon-X

A DNA specialist cousin that another agent calls for variant-effect and sequence questions, with DNA kept on the machine. Hugging Face's Q4_K_M GGUF needs about 12 GB and Q8_0 about 19 GB, on llama.cpp b11742 or later. It isn't clinically validated, isn't trained for tool calls or reasoning, and its Python tokenizer runs repository code.

LFM3-VL-2B

A 1.92B vision model that reads images and video on an 8 GB machine, with a documented tool-call format and thinking. It runs today in llama.cpp, Ollama and LM Studio, while vLLM and SGLang support is still unreleased. Transformers needs repository code, and there are no safety results, security contact or data sources.

Before you call either

Carbon-X

  1. Quickest start is llama-server -hf HuggingFaceBio/Carbon-X-GGUF:Q8_0 -ngl 99 -c 40960 --jinja --chat-template-kwargs '{"enable_thinking": false}' --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0, on llama.cpp b11742 or later
  2. With vLLM or Transformers pass trust_remote_code, and expect the tokenizer to fetch Qwen/Qwen3-4B-Base at a pinned revision on first load
  3. Keep enable_thinking false and the card's sampling (temperature 0.6, top_p 0.95, top_k 20), the settings every reported result used
  4. Keep DNA in files and pass sequences by name, compute positions and base changes in code and send them as context, the card says the model miscounts long sequences
  5. Only A, C, G and T form 6-mers, so filter N and other IUPAC codes first or they become a single oov token
  6. Strip the dna tags from answers if you need bare sequence, llama.cpp keeps them in the text
  7. Cap max_tokens for next-base questions, long DNA generation is slow and degrades

LFM3-VL-2B

  1. Start it with llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinja or ollama run lfm3-vl, with llama.cpp b11960 or later
  2. Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
  3. Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
  4. Don't plan on vLLM or SGLang until a release carries LFM3-VL
  5. Validate JSON output yourself
  6. Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning

Questions

Which is better for AI agents, Carbon-X or LFM3-VL-2B?

Carbon-X and LFM3-VL-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-VL-2B leads on agent interface and documentation and upkeep.

Other comparisons with Carbon-X or LFM3-VL-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.