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

MiniCPM-V 4.7 1B vs Qwen3.5-122B-A10B

Qwen3.5-122B-A10B scores 63.1 (B) on agent readiness against MiniCPM-V 4.7 1B's 61 (C), and leads in 0 of 4 scored categories. MiniCPM-V 4.7 1B leads on reach 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 6359 open weights comparisons

Which one, for what

MiniCPM-V 4.7 1B C

Best for Agents that need a cheap local model to read screenshots, photos and short video on a phone, a laptop or beside a bigger model

Ahead on

  • Reach, 95 against 80
  • Documentation and upkeep, 48 against 34

Watch for

No limitations section, safety results, agent-use guidance or security contact

Qwen3.5-122B-A10B B

Best for Agents with a 128 GB unified-memory machine or two large GPUs that want a capable vision-language model with a plain licence.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Too big for a single 64 GB machine even at 4 bits

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.

Reach MiniCPM-V 4.7 1B +15

MiniCPM-V 4.7 1B 95

Memory 30, OpenBMB's own IQ4_XS GGUF is 0.64 GB, 1.54 GB with the 0.90 GB vision projector, and 1.54 GB × 1.2 = 1.9 GB, which fits 16 GB with room to spare. Runtimes 25, MiniCPMV4_7ForConditionalGeneration in vLLM's registry at v0.33.0, the minicpmv4_7 model type in SGLang's minicpmv.py at v0.5.23, the minicpmv4_7 model in Transformers at v5.22.2, a MiniCPM-V 4.7 guide and conversion code in llama.cpp at b12242, and an openbmb/minicpm-v4.7:1b tag in OpenBMB's namespace on Ollama, read as the 35B-A3B listing's is. Builds 15, OpenBMB publishes AWQ, GPTQ and int4 safetensors builds and a GGUF repository from IQ3_XS to F16, so quantised builds at two precisions or more. Terms 15, Apache 2.0 in the card's metadata and as the LICENSE of OpenBMB's MiniCPM-V repository, an OSI licence. Download 10, gated is false on the main repository and on the GGUF, AWQ, GPTQ and int4 repositories, so the files download with no account or terms. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and no provider's own list was read. 30 + 25 + 15 + 15 + 10 + 0 = 95.

Qwen3.5-122B-A10B 80

Memory earns 10 of 30, since Alibaba's GPTQ 4-bit build is 78.9 GB, about 95 GB with a fifth added, which fits our reference machine but no smaller band. Runtimes reach the 25 cap on released llama.cpp, Ollama, vLLM, SGLang and Transformers. Alibaba's FP8 and GPTQ-Int4 builds give builds the full 15. Apache 2.0 with nothing added gives terms 15, the ungated repositories give download 10, and Alibaba's own Model Studio plus Novita and DeepInfra give hosted too its 5.

Documentation and upkeep MiniCPM-V 4.7 1B +14

MiniCPM-V 4.7 1B 48

Model card 8, Intended use (image, multi-image and video understanding on device), architecture (early visual-token compression inside the vision encoder) and parameters (1B) are there. Training data 0, no description of the training data on the card. Last change 20, the last commit, on 30 October 2026, updated the card and removed an unused asset folder, eleven days before this check. Responsiveness 0, the repository has no discussions that aren't pull requests (two pull requests in all), so nobody has asked anything yet and the line reads as none answered, as settled in calibration. Version policy 10, MiniCPM-V 4.5 and 4.6 stay in their own repositories and the GitHub README dates each release. File health 10, Config, template and card agree on the architecture and the thinking switch, and no report waits without a reply, since there are no discussions. 8 + 0 + 20 + 0 + 10 + 10 = 48.

Qwen3.5-122B-A10B 34

The card covers five of the seven items and misses limitations and a cut-off (14). Training data is a general description without a cut-off (5). The files last changed on 24 April 2026, 192 days before this check, past the 180-day band and within a year (5), and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. No Qwen member has answered any of the 21 discussions that aren't pull requests, recounted on 2 November (0), and GitHub issues couldn't be counted. It's a first release at this size (5), and a template fix and a run report still wait unanswered (5). 14 + 5 + 5 + 0 + 5 + 5 = 34.

Score by category

CategoryWeight this runMiniCPM-V 4.7 1BQwen3.5-122B-A10BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259580MiniCPM-V 4.7 1B +15
Risk20%205555even
Agent interface10%107070even
Documentation and upkeep10%104834MiniCPM-V 4.7 1B +14
Negative events≤1500
TotalC 61/100B 63.1/100

Facts side by side

FactMiniCPM-V 4.7 1BQwen3.5-122B-A10B
KindOpen-weight modelOpen-weight model
VendorOpenBMBAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-302026-02-24
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

MiniCPM-V 4.7 1B

A vision-language cousin small enough for a phone, under plain Apache 2.0, that every runtime we count can load. The projector is bigger than the language model, so plan for about 2 GB. The card says nothing about limits or training data and doesn't show how a tool call comes back.

Qwen3.5-122B-A10B

A strong mid-size cousin for coding, agent steps and reading images or video, with thinking you can switch off per request. Alibaba's 4-bit build needs about 95 GB, which fits one 128 GB unified-memory machine, and several providers host it. The main risk is silence, with no safety results, agent guidance or answers from Alibaba.

Before you call either

MiniCPM-V 4.7 1B

  1. Start it with llama-server -hf openbmb/MiniCPM-V-4.7-1B-gguf:Q4_K_M --jinja, or ollama run openbmb/minicpm-v4.7:1b
  2. For image input in llama.cpp add mmproj-model-f16.gguf, or the smaller 4x projector
  3. The GGUF files at the repository root have thinking off. Use the files in thinking/ when you want the trace
  4. Use temperature 0.7, top_p 0.95 and top_k 100 in instruct mode, as the card recommends
  5. Check tool calls in your runtime first, since the card names no parser
  6. Validate JSON output yourself, since structured output isn't documented

Qwen3.5-122B-A10B

  1. Quickest start on a 128 GB machine is ollama run qwen3.5:122b (Q4_K_M, 81 GB of files, about 97 GB with context)
  2. Alibaba's 4-bit build serves with vllm serve Qwen/Qwen3.5-122B-A10B-GPTQ-Int4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --quantization moe_wna16, though that kernel isn't documented for AMD gfx1151
  3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as the card's commands do
  4. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
  5. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
  6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  7. Add --language-model-only in vLLM to skip the vision encoder and free memory for the KV cache when you only need text
  8. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, MiniCPM-V 4.7 1B or Qwen3.5-122B-A10B?

Qwen3.5-122B-A10B scores 63.1 (B) on agent readiness against MiniCPM-V 4.7 1B's 61 (C), and leads in 0 of 4 scored categories. MiniCPM-V 4.7 1B leads on reach and documentation and upkeep.

Other comparisons with MiniCPM-V 4.7 1B or Qwen3.5-122B-A10B

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.