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

MiniCPM-o 4.5 vs Step 3.7 Flash

MiniCPM-o 4.5 scores 61 (C) on agent readiness against Step 3.7 Flash's 59.8 (C), and leads in 2 of 4 scored categories. Step 3.7 Flash leads on risk and agent interface. 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

Best conversational voice-agent APIs · All 581 voice agents comparisons

Which one, for what

MiniCPM-o 4.5 C

Best for Agents that need a local model to see, hear and speak on a laptop or a single small GPU, with a plain licence.

Ahead on

  • Reach, 90 against 70
  • Documentation and upkeep, 66 against 39

Watch for

Speech output and full duplex need trust_remote_code with Transformers 4.51.0 or OpenBMB's llama.cpp-omni

Step 3.7 Flash C

Best for Teams with a GPU server or a provider account that want an open, long-context agent model with vision

Ahead on

  • Risk, 45 against 40
  • Agent interface, 85 against 35

Watch for

About 131 GB to run at 4 bits with images, over a 128 GB machine's share

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 Step 3.7 Flash +50

MiniCPM-o 4.5 35

Chat template 20, a Jinja template in the tokenizer config. Tool-calling format 10 of 25, only the inherited Qwen3 template says how tools work. Trained tool calling 0, OpenBMB never mentions tool use. Structured output 0, not documented. Reasoning control 0, thinking turns on and off per request but nobody says where the reasoning comes back. Context 5, 40,960 tokens. Read as an omni model, it takes images, video and audio and returns text and streaming speech, which the card documents with code.

Step 3.7 Flash 85

Chat template 20, chat_template.jinja in the repository (5,723 characters). Tool-calling format 25, the card names the parser to use in two runtimes, step3p5 in vLLM (with auto tool choice) and in SGLang, and both ship Step parsers in a release. Trained tool calling 20, the card presents tool orchestration as a main use, with multi-turn results, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output for the weights. Reasoning control 10, the template has a reasoning_effort setting and keeps reasoning_content, and the card names the step3p5 reasoning parser for vLLM and SGLang, which returns the reasoning apart from the answer. Context 10, 256K tokens per the card, and 262,144 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Documentation and upkeep MiniCPM-o 4.5 +27

MiniCPM-o 4.5 66

Model card 11 of 20, limitations, context length and a knowledge cut-off are missing. Training data 5, described by kind without sources, sizes or a cut-off. Last change 20, the card changed on 24 October 2026. Responsiveness 10, OpenBMB answered half of the 12 questions. Version policy 10, earlier models stay in their own repositories and releases are dated. File health 10, the files agree and the two bug reports have replies.

Step 3.7 Flash 39

Model card 14, Intended use, the architecture, the parameters, the context and the language (in the metadata) are on the card. Training data 0, Nothing on the card about the training data. Last change 10, the last commit, on 3 June 2026, fixed the modelling code, 160 days before this check and within 180. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (29 May to 24 June 2026) has a reply from a stepfun-ai member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, Step-3.5-Flash stays in its own repositories and 3.7 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the context, and June commits fixed the modelling code. 14 + 0 + 10 + 0 + 5 + 10 = 39.

Reach MiniCPM-o 4.5 +20

MiniCPM-o 4.5 90

Memory 30, OpenBMB's 4-bit GGUF with its vision file is 5.9 GB, about 7 GB with a fifth added. Runtimes 15 of 25, released vLLM, llama.cpp and Ollama run it, while Transformers 5.22.1 still needs OpenBMB's remote code and SGLang 0.5.23 supports only the older 2.6. Builds 15, GGUF at several precisions plus AWQ and GPTQ. Terms 15, plain Apache 2.0. Download 10, nothing gated. Hosted 5, OpenBMB's own API serves it.

Step 3.7 Flash 70

Memory 5, the smallest build at 4 bits is StepFun's IQ4_XS GGUF, 104.99 GB with the 3.97 GB projector, and 108.96 GB × 1.2 = 130.8 GB, over what the reference machine can give a model and within 256 GB. The IQ3 and Q3 builds are below 4 bits and aren't read. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the step3p7 model, and llama.cpp b12242 has the architecture, with StepFun's own GGUF. Four at 5 each, and the card documents all four. Builds 15, StepFun publishes GGUF at five quantised precisions, an FP8 build and an NVFP4 build. Terms 15, Apache 2.0 in the card's metadata and its licence section, an OSI licence with nothing added. Download 10, the Hub API reports gated false for all four repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, StepFun's own API serves it, per the card and our StepFun API listing, and Featherless and DeepInfra are live for it on Hugging Face. 5 + 20 + 15 + 15 + 10 + 5 = 70.

Risk Step 3.7 Flash +5

MiniCPM-o 4.5 40

File safety 5 of 25, two pickle files sit in the speech stage and the documented load runs repository code. Provenance 15, the files are in the openbmb organisation OpenBMB's GitHub links, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 5, general cautions only, nothing about voice cloning misuse, prompt injection or refusals. Licence risk 15, plain Apache 2.0. Security programme 0, no security.txt, policy or advisories.

Step 3.7 Flash 45

File safety 15, safetensors and GGUF only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the stepfun-ai organisation, which the card's StepFun platform and model page belong to (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations section and gives no guidance on prompt injection, instruction priority, refusals or safeguards. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 0, no way to report a flaw on the card, and our StepFun API listing found no security.txt, bug bounty or disclosure policy. 15 + 15 + 0 + 0 + 15 + 0 = 45.

Score by category

CategoryWeight this runMiniCPM-o 4.5Step 3.7 FlashEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259070MiniCPM-o 4.5 +20
Risk20%204045Step 3.7 Flash +5
Agent interface10%103585Step 3.7 Flash +50
Documentation and upkeep10%106639MiniCPM-o 4.5 +27
Negative events≤1500
TotalC 61/100C 59.8/100

Facts side by side

FactMiniCPM-o 4.5Step 3.7 Flash
KindOpen-weight modelOpen-weight model
VendorOpenBMBStepFun
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0; built from Qwen3-8B, SigLIP2, Whisper-medium and CosyVoice2, all Apache 2.0 on their Hub cardsApache-2.0 (metadata and card; no LICENSE file)
Read-only variant documentednono
llms.txtnono
Last release2026-10-242026-06-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

Verdicts

MiniCPM-o 4.5

A small omni cousin that sees, listens and talks back, with full-duplex speech and voice cloning, in about 7 GB at 4-bit through llama.cpp or Ollama for text and images. Speech output needs OpenBMB's remote code or llama.cpp-omni, and 28 GB of GPU for the full demo. The main risks are repository code and pickle files and no safety results.

Step 3.7 Flash

A capable open agent model with a clean licence, every kind of build and four released runtimes. Two things hold it back: it's a little too big for a 128 GB machine at 4 bits, whatever the card says, and StepFun has gone quiet on the repository since June. No safety results, limitations or data description.

Before you call either

MiniCPM-o 4.5

  1. Quickest start for text and images is ollama run openbmb/minicpm-o4.5, about 6 GB
  2. With vLLM 0.16.0 or later pass --trust-remote-code, and send stop_token_ids [151643, 151645] as OpenBMB's guide does
  3. vLLM, llama.cpp and Ollama return text only; for speech out use the card's Transformers 4.51.0 code or OpenBMB's llama.cpp-omni
  4. In llama.cpp pass both the language GGUF and MiniCPM-o-4_5-vision-F16.gguf with --mmproj, and use --jinja --reasoning-budget 0 to turn thinking off
  5. Keep prompts within 40,960 tokens
  6. Don't rely on tool calls or JSON output, neither is documented; validate any you get

Step 3.7 Flash

  1. On a 128 GB machine the 4-bit GGUF won't fit with a working context. Use StepFun's API or a provider, or a server
  2. On vLLM or SGLang pass --tool-call-parser step3p5 --reasoning-parser step3p5
  3. The card's commands pass trust-remote-code. Released Transformers 5.22.2 has the model built in if you'd rather not run the repository's code
  4. For llama.cpp load the mmproj file from StepFun's GGUF repository for image input
  5. StepFun's API has two hosts. Use the one where your key was issued, api.stepfun.ai or api.stepfun.com
  6. The same model is on our StepFun API listing, with prices and terms

Questions

Which is better for AI agents, MiniCPM-o 4.5 or Step 3.7 Flash?

MiniCPM-o 4.5 scores 61 (C) on agent readiness against Step 3.7 Flash's 59.8 (C), and leads in 2 of 4 scored categories. Step 3.7 Flash leads on risk and agent interface.

Other comparisons with MiniCPM-o 4.5 or Step 3.7 Flash

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.