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

MiniCPM-V 4.7 35B-A3B vs occamy-1.0

MiniCPM-V 4.7 35B-A3B and occamy-1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). occamy-1.0 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 6359 open weights comparisons

Which one, for what

MiniCPM-V 4.7 35B-A3B C

Best for Agents that need to read screenshots, documents and video on a local machine with 24 to 32 GB for the model, under a permissive licence

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

Watch for

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

occamy-1.0 C

Best for Agents that want an Apache 2.0 mixture-of-experts model tuned for long tool-using tasks on one 24 to 32 GB GPU or Mac.

Ahead on

  • Documentation and upkeep, 74 against 68

Watch for

No safety results, prompt-injection guidance or security contact

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.

Documentation and upkeep occamy-1.0 +6

MiniCPM-V 4.7 35B-A3B 68

Model card 8, it covers intended use, architecture and parameters but not limitations, context length, languages or a knowledge cut-off. Training data 0, none described. Last change 20, a commit on 3 November 2026. Responsiveness 20, OpenBMB answered 8 of 12 discussions. Version policy 10, earlier versions keep their repositories and the changes are dated and described. File health 10, the files agree. 8 + 0 + 20 + 20 + 10 + 10 = 68.

occamy-1.0 74

Model card 14 of 20, languages and a knowledge cut-off are missing. Training data 15, the mix by type with token counts, the method and a published subset, without a cut-off. Last change 20, Accio's GGUF build card changed on 19 October 2026 and the main card on 2 October. Responsiveness 10, Accio answered 4 of 9 questions. Version policy 5, a first release with no files replaced. File health 10, the files agree with the card. 14 + 15 + 20 + 10 + 5 + 10 = 74.

Score by category

CategoryWeight this runMiniCPM-V 4.7 35B-A3Boccamy-1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259090even
Risk20%205555even
Agent interface10%107070even
Documentation and upkeep10%106874occamy-1.0 +6
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactMiniCPM-V 4.7 35B-A3Boccamy-1.0
KindOpen-weight modelOpen-weight model
VendorOpenBMBAccio (Accio-Lab)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-032026-10-02
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 35B-A3B

A vision-language cousin for images and video that fits a 24 to 32 GB machine from OpenBMB's own GGUF, under plain Apache 2.0, with a publisher that answers. The card says little about limits, training data or how tool calls come back, so test the tool format in your runtime before relying on it.

occamy-1.0

A Qwen3.6-35B-A3B fine-tuned for long agent work with tools, files and code, under plain Apache 2.0, and Accio's 4-bit builds run in about 23 GB. The main gaps are no safety results, agent guidance or security contact, and every benchmark figure is Accio's own.

Before you call either

MiniCPM-V 4.7 35B-A3B

  1. Start it with llama-server -hf openbmb/MiniCPM-V-4.7-35B-A3B-gguf:Q4_K_M --jinja, or ollama run openbmb/minicpm-v4.7:35b-a3b
  2. For image input in llama.cpp add mmproj-model-f16.gguf, or the 4x projector for more visual detail at a higher cost
  3. The GGUF files at the repository root have thinking off. Use the files in thinking/ when you want the trace
  4. With Transformers pass enable_thinking to apply_chat_template, and pass downsample_mode to both apply_chat_template and generate
  5. Use temperature 0.7, top_p 0.95 and top_k 100 in instruct mode, as the card recommends
  6. Check tool calls in your runtime first, since the card names no parser. The template uses the Qwen3.5 function-block format
  7. Validate JSON output yourself, since structured output isn't documented

occamy-1.0

  1. Serve with --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on vLLM 0.19.0 or SGLang 0.5.10 and later
  2. BF16 is 70.2 GB, so on a 128 GB machine run it without the card's 8-way tensor parallelism
  3. Keep the whole assistant message, reasoning and tool calls included, in later turns, as the card says
  4. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 1.5
  5. With the GGUFs, NFC-normalise input text and read TOKENIZER.md, since the files store qwen2 pre-tokenizer metadata
  6. The base's MTP layer isn't in this checkpoint, Accio-Lab/occamy-1.0-MTP is an experimental separate head
  7. Ollama has no Occamy library entry, so load Accio's GGUF in Ollama 0.40.14 or later, which builds a llama.cpp with the qwen35moe architecture

Questions

Which is better for AI agents, MiniCPM-V 4.7 35B-A3B or occamy-1.0?

MiniCPM-V 4.7 35B-A3B and occamy-1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). occamy-1.0 leads on documentation and upkeep.

Other comparisons with MiniCPM-V 4.7 35B-A3B or occamy-1.0

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.