Sign in

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

Apodex-1.1-mini vs MiniCPM-V 4.7 35B-A3B

Apodex-1.1-mini and MiniCPM-V 4.7 35B-A3B score within a point of each other on agent readiness, 61 (C) and 61 (C). MiniCPM-V 4.7 35B-A3B 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

Apodex-1.1-miniApodex AI · Open-weight model C61/100#41 of 160 open-weight models MiniCPM-V 4.7 35B-A3BOpenBMB · Open-weight model C61/100#77 of 160 open-weight models

Which one, for what

Apodex-1.1-mini C

Best for Long-running agent tasks with tools on a 32 GB GPU or Mac, or through Apodex's API, under a plain licence

Ahead on

  • Risk, 65 against 55
  • Agent interface, 85 against 70

Watch for

No safety results, and agent guidance only from the harness

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

Ahead on

  • Reach, 90 against 85
  • Documentation and upkeep, 68 against 38

Watch for

No limitations section, safety results, agent-use 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 MiniCPM-V 4.7 35B-A3B +30

Apodex-1.1-mini 38

Model card 8, it covers intended use, context and languages but not the architecture, parameters, limitations or a knowledge cut-off. Training data 5, a general description with no cut-off. Last change 15, the GGUF build went up on 10 September 2026, 54 days before 3 November. Responsiveness 0, Apodex answered none of the four discussions, unchanged on 3 November 2026. Version policy 5, 1.0-mini stays in its own repository without a note. File health 5, the files agree, but the card's agent example is broken and reports wait without a reply.

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.

Agent interface Apodex-1.1-mini +15

Apodex-1.1-mini 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card says how tools go in and come back and names the parser for SGLang and vLLM, with a full example. Trained tool calling 20, trained for native function calling with parallel calls. Structured output 0. Reasoning control 10, the template turns thinking off per request and the card says the reasoning comes back in reasoning_content. Context 10, 262,144 tokens.

MiniCPM-V 4.7 35B-A3B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10, the card shows the tools array going in but not the call coming back, and names no parser. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented or claimed. Reasoning control 10, enable_thinking per request, off by default, with the trace between markers. Context 10, 262,144 tokens native.

Risk Apodex-1.1-mini +10

Apodex-1.1-mini 65

File safety 25, safetensors and GGUF only and nothing from the repositories runs. Provenance 15, the files are in the apodex organisation its site links to, with a SHA-256 for every weight file and a SHA256SUMS file for the GGUF. Safety evaluation 0, none published. Agent guidance 5, the recommended harness documents approval gates and a sandbox boundary, but nothing on prompt injection or refusals for the model. Licence risk 15, Apache 2.0 from Qwen3.5-35B-A3B through to this model with no conditions added. Security programme 5, the harness has a disclosure policy with a private address, with no route shown for the weights.

MiniCPM-V 4.7 35B-A3B 55

File safety 25, safetensors and GGUF only, no Python in the main repository and no remote code needed. Provenance 15, the files come from the openbmb organisation OpenBMB's GitHub README links to, with a SHA-256 for every weight file. Safety evaluation 0 and agent guidance 0, nothing published on either, and the card has no limitations section. Licence risk 15, plain Apache 2.0. Security programme 0, no security.txt or SECURITY.md.

Reach MiniCPM-V 4.7 35B-A3B +5

Apodex-1.1-mini 85

Memory 20, Apodex's Q4_K_M GGUF with its vision projector is 22.6 GB and needs about 27.1 GB with the fifth added, so 32 GB, as do its NVFP4 and GPTQ-Int4 builds. Runtimes 20, the Qwen3.5 MoE architecture runs in released vLLM, SGLang, Transformers and llama.cpp, while Ollama's and LM Studio's entries are the base's, not this model's. Builds 15, Apodex publishes FP8, NVFP4, GPTQ-Int4 and GGUF. Terms 15, Apache 2.0 with nothing added. Download 10, nothing is gated. Hosted 5, Apodex's own API serves it.

MiniCPM-V 4.7 35B-A3B 90

Memory 25, since OpenBMB's IQ4_XS GGUF with its vision projector is 19.6 GB and needs about 23.6 GB with the fifth added, which fits 24 GB, while its Q4_K_M GGUF, 4-bit safetensors builds and Ollama entry need 32 GB. Runtimes 25, from vLLM 0.33.0, SGLang 0.5.23, Transformers 5.18.0 and later, llama.cpp's own MiniCPM-V 4.7 support and OpenBMB's entry on Ollama. Builds 15, OpenBMB publishes FP8, three 4-bit safetensors builds and GGUF. Terms 15, Apache 2.0 with nothing added. Download 10, nothing is gated. Hosted 0, no inference provider is mapped. 25 + 25 + 15 + 15 + 10 + 0 = 90.

Score by category

CategoryWeight this runApodex-1.1-miniMiniCPM-V 4.7 35B-A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258590MiniCPM-V 4.7 35B-A3B +5
Risk20%206555Apodex-1.1-mini +10
Agent interface10%108570Apodex-1.1-mini +15
Documentation and upkeep10%103868MiniCPM-V 4.7 35B-A3B +30
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApodex-1.1-miniMiniCPM-V 4.7 35B-A3B
KindOpen-weight modelOpen-weight model
VendorApodex AIOpenBMB
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-252026-11-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3.3/5 (4)none

Verdicts

Apodex-1.1-mini

An agent cousin fine-tuned from Qwen3.5-35B-A3B for long tasks with files, code and tools, with parallel tool calling and about 3B active parameters. It needs 32 GB for Apodex's GGUF, NVFP4 or GPTQ-Int4 builds or about 86 GB in BF16, and Apodex's API serves it too. The main risks are no safety results and no replies from the publisher.

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.

Before you call either

Apodex-1.1-mini

  1. Serve it with vllm serve apodex/Apodex-1.1-mini --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser qwen3, or the same parsers in SGLang, so tool calls and reasoning come back parsed
  2. For llama.cpp, llama-server -hf apodex/Apodex-1.1-mini-GGUF:Q4_K_M --jinja --reasoning-format deepseek, and the card passes the repository's chat_template.jinja with --chat-template-file
  3. Pass tools through the API's tools parameter rather than in the system prompt, as the card asks
  4. The card recommends temperature 1.0, top_p 0.95, repetition_penalty 1.05 and max_tokens up to 32,768
  5. Send your own system prompt, or set identity_mode, since the template otherwise adds an Apodex identity block
  6. The template keeps all earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  7. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  8. The card's Python example has a broken line where it runs the tool (available_toolsname), so fix it to available_tools[name](**args) before running
  9. Validate JSON output yourself, since structured output isn't documented

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

Questions

Which is better for AI agents, Apodex-1.1-mini or MiniCPM-V 4.7 35B-A3B?

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

Other comparisons with Apodex-1.1-mini or MiniCPM-V 4.7 35B-A3B

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.

Get an auditSee a sample report