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

Kimi K3 vs MiniCPM-V 4.7 1B

Kimi K3 scores 62.4 (B) on agent readiness against MiniCPM-V 4.7 1B's 61 (C), and leads in 1 of 4 scored categories. MiniCPM-V 4.7 1B leads on reach, 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

Kimi K3 B

Best for Teams with a multi-node GPU cluster who want an open 1M-context agent model for long coding and research work

Ahead on

  • Risk, 65 against 55

Watch for

1,561 GB of files at its smallest publisher build, far beyond any single machine

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 50
  • Agent interface, 70 against 65
  • Documentation and upkeep, 48 against 41

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.

Reach MiniCPM-V 4.7 1B +45

Kimi K3 50

Memory earns nothing, because the only build of 4-bit precision or better from Moonshot or a runtime's own library is Moonshot's MXFP4 release of 1,561 GB, about 1,873 GB with the fifth added, far above 256 GB. Ollama and LM Studio list it only as a cloud model. Runtimes earn 15, for model code in released vLLM, SGLang and llama.cpp; Transformers has no kimi_k3 code of its own and loads Moonshot's remote code, so it doesn't count. Builds earn 10 for one publisher precision, the MXFP4 files the model was trained for. Terms earn 10, a custom MIT-based licence that is free for commercial use below a revenue threshold. Download earns 10, with no gate and no account. Hosted earns 5, since Moonshot's API serves it and five inference providers are live for it on Hugging Face.

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.

Risk Kimi K3 +10

Kimi K3 65

File safety earns 15, safetensors only with no pickle files, less 10 because the documented loading path runs Moonshot's Python with trust_remote_code and builds prompts with encoding_k3.py. Provenance earns the full 15, files in the organisation Moonshot links to with a SHA-256 for every shard. Safety evaluation earns 20 for the cyber assessment the UK AI Security Institute and CAISI ran and published, which found its safeguards didn't stop exploit development. Agent guidance earns 5 for the blog's general cautions about proactiveness and passing back thinking. Licence risk earns 10, losing 5 for the model-as-a-service revenue threshold and nothing else. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or public advisories found.

MiniCPM-V 4.7 1B 55

File safety 25, safetensors in the main repository and the AWQ, GPTQ and int4 builds, GGUF in the GGUF build, with no .bin, .pt, .pth or .py files in the main repository. Provenance 15, files in the openbmb organisation that OpenBMB's GitHub README links to (10), with a SHA-256 for both large files in the main repository (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or disclaimer section, and no prompt-injection guidance, instruction hierarchy or statement of trained refusals. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the LICENSE in OpenBMB's GitHub repository resolved on 10 November 2026. Security programme 0, no SECURITY.md in OpenBMB/MiniCPM-V and no security.txt on openbmb.cn (both 404 on 10 November 2026), and no advisories found. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Documentation and upkeep MiniCPM-V 4.7 1B +7

Kimi K3 41

The model card earns 11, covering intended use, architecture, parameters and context, but not limitations, languages or a knowledge cut-off. Training data earns 5 for a general description with no cut-off. The last change earns 15, an encoding_k3.py update on 20 August, 74 days before 2 November and within 90; the GitHub repository's last commit is 6 August. Responsiveness earns nothing, with no Moonshot reply in the 40 most recent discussions. Version policy earns 5 for a first release. File health earns 5, because a report that the tokeniser goes past the declared vocabulary waits without a reply.

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.

Agent interface MiniCPM-V 4.7 1B +5

Kimi K3 65

The chat template earns 10, because there is no Jinja template and the prompt format exists only as encoding_k3.py, code you run. The tool-calling format earns 10, since Moonshot documents the tools channel but the parser name comes only from vLLM's and SGLang's own recipes. Trained tool calling earns 20 for indexed parallel calls in one turn. Structured output earns 5, as the card names it among its linked guides without saying how to ask the weights for it, and the how sits in hosted-API docs. Reasoning control earns 10, with per-request effort documented on the card and reasoning returned as reasoning_content. Context earns 10 for 1,048,576 tokens trained in.

MiniCPM-V 4.7 1B 70

Chat template 20, chat_template.jinja in the repository, 7,249 characters. Tool-calling format 10, the card shows tools declared in the OpenAI tools array in a request to Transformers' server, but not how a call comes back, and names no parser for vLLM or SGLang. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one assistant turn, and the card gives a tool-calling request as a supported use. Structured output 0, Neither JSON nor JSON Schema output is documented or claimed for the model on the card. Reasoning control 10, the card passes enable_thinking per request in its examples, the template has been off by default since 19 October 2026, and the GGUF repository keeps thinking builds in their own folder. Context 10, 262,144 tokens, max_position_embeddings in the text config. 20 + 10 + 20 + 0 + 10 + 10 = 70.

Score by category

CategoryWeight this runKimi K3MiniCPM-V 4.7 1BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255095MiniCPM-V 4.7 1B +45
Risk20%206555Kimi K3 +10
Agent interface10%106570MiniCPM-V 4.7 1B +5
Documentation and upkeep10%104148MiniCPM-V 4.7 1B +7
Negative events≤1500
TotalB 62.4/100C 61/100

Facts side by side

FactKimi K3MiniCPM-V 4.7 1B
KindOpen-weight modelOpen-weight model
VendorMoonshot AIOpenBMB
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceKimi K3 License (modified MIT)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-09-022026-10-30
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.3/5 (4)none

Verdicts

Kimi K3

Kimi K3 is a 2.8T multimodal agent model with a 1M-token context, parallel tool calls and per-request effort, for long coding and research sessions. Its 1,561 GB of files need a multi-node GPU cluster, so most agents will call a hosted copy. The main risks are Moonshot's Python running at load and prompt time, and no answers in its repository.

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.

Before you call either

Kimi K3

  1. Start it with SGLang on a node of 8 B300s, sglang serve --trust-remote-code --model-path moonshotai/Kimi-K3 --tp-size 8 --context-length 65536 --mem-fraction-static 0.82 --reasoning-parser kimi_k3 --tool-call-parser kimi_k3 --port 30000
  2. Use the kimi_k3 tool-call and reasoning parsers in vLLM or SGLang, and validate tool-call arguments against the schema, since vLLM's recipe says K3 sometimes emits a format its parser doesn't expect
  3. Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
  4. Thinking is always on; set reasoning_effort to low or high when max is too slow
  5. Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
  6. Don't hand an ongoing session from another model to K3, and state boundaries in the system prompt, since Moonshot warns it can act on its own when intent is unclear
  7. Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page

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

Questions

Which is better for AI agents, Kimi K3 or MiniCPM-V 4.7 1B?

Kimi K3 scores 62.4 (B) on agent readiness against MiniCPM-V 4.7 1B's 61 (C), and leads in 1 of 4 scored categories. MiniCPM-V 4.7 1B leads on reach, agent interface and documentation and upkeep.

Other comparisons with Kimi K3 or MiniCPM-V 4.7 1B

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.