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

Hy3 vs MiniCPM-o 4.5

Hy3 scores 62.6 (B) on agent readiness against MiniCPM-o 4.5's 61 (C), and leads in 2 of 4 scored categories. MiniCPM-o 4.5 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 2870 open weights comparisons

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

Which one, for what

Hy3 B

Best for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0

Ahead on

  • Risk, 60 against 40
  • Agent interface, 75 against 35

Watch for

597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build

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 56

Watch for

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

Score by category

CategoryWeight this runHy3MiniCPM-o 4.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257090MiniCPM-o 4.5 +20
Risk20%206040Hy3 +20
Agent interface10%107535Hy3 +40
Documentation and upkeep10%105666MiniCPM-o 4.5 +10
Negative events≤1500
TotalB 62.6/100C 61/100

Facts side by side

FactHy3MiniCPM-o 4.5
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)OpenBMB
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0; built from Qwen3-8B, SigLIP2, Whisper-medium and CosyVoice2, all Apache 2.0 on their Hub cards
Read-only variant documentednono
llms.txtnono
Last release2026-07-202026-10-16
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.8/5 (4)2.8/5 (4)

Verdicts

Hy3

Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.

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.

Before you call either

Hy3

  1. Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
  2. In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
  3. Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
  4. With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
  5. Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
  6. Use temperature 0.9 and top_p 1.0, the card's recommended sampling
  7. On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
  8. Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers

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

Questions

Which is better for AI agents, Hy3 or MiniCPM-o 4.5?

Hy3 scores 62.6 (B) on agent readiness against MiniCPM-o 4.5's 61 (C), and leads in 2 of 4 scored categories. MiniCPM-o 4.5 leads on reach and documentation and upkeep.

Other comparisons with Hy3 or MiniCPM-o 4.5

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.