Hy-Memory-30B-A3B vs MiniCPM-o 4.5

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

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.

Hy-Memory-30B-A3B 60

File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

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.

Hy-Memory-30B-A3B 85

Memory 25, Tencent's own Q4_K_M GGUF is 18.24 GB, and 18.24 GB × 1.2 = 21.9 GB, which fits 24 GB but not 16 GB. Its Q3_K_M file and the two files with experts at 1 or 2 bits are below 4-bit precision and don't count. Runtimes 20, hy_v3 model code in released vLLM (HYV3ForCausalLM in the v0.33.0 registry), SGLang v0.5.23 (hunyuan_v3.py), Transformers v5.22.2 and llama.cpp b12242, 5 each. Builds 15, Tencent publishes an FP8 repository and a GGUF repository with Q4_K_M, Q6_K and Q8_0 files in its own organisation, so quantised builds at two precisions or more. Terms 15, Apache 2.0, with only a preamble naming Tencent as copyright holder above the licence text. Download 10, gated is false for the main, FP8 and GGUF repositories on 10 November 2026, so the files download with no account or terms to accept. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and the card names no API. 25 + 20 + 15 + 15 + 10 + 0 = 85.

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.