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

Hy-Memory-30B-A3B vs MiniMax-M3.1-Flash

Hy-Memory-30B-A3B scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 54.3 (C), and leads in 3 of 4 scored categories. MiniMax-M3.1-Flash leads on agent interface. 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

Hy-Memory-30B-A3B C

Best for Agents with an external memory framework that want a local model for the write path on a 24 GB card

Ahead on

  • Reach, 85 against 55
  • Risk, 60 against 35
  • Documentation and upkeep, 68 against 41

Watch for

Not a general assistant or a tool caller

MiniMax-M3.1-Flash C

Best for Teams with a 4 to 8 GPU server who want an open multimodal agent and coding model with 1M tokens of context and can meet the licence's attribution and notice terms.

Ahead on

  • Agent interface, 70 against 65

Watch for

SGLang's cookbook still points to a pull request or a dev image on 4 November 2026, and vLLM's recipe still names a nightly image, though both runtimes' releases carry the model code

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 Hy-Memory-30B-A3B +30

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.

MiniMax-M3.1-Flash 55

Memory earns nothing. MiniMax's only build is its 250 GB NVFP4 and MXFP8 release, about 300 GB with the fifth added, above 256 GB, and no runtime library has a local build. Runtimes earn 20. llama.cpp from b11861 runs it, Ollama v0.40.14 pins llama.cpp b11963 with the minimax-m3 architecture, vLLM v0.33.0 (tagged 1 November 2026) registers the architecture and meets its recipe's minimum version, and SGLang v0.5.23 (tagged 29 October) registers it with M3.1 processor code and tests, though its cookbook still points to a pull request. Transformers support is in progress per the card and LM Studio has no entry. Builds earn 10 for one publisher precision. Terms earn 10, since commercial use is free with attribution and a notice below $20M of yearly revenue. Download earns 10, with no gate. Hosted earns 5, since MiniMax's API and Novita serve it. 0 + 20 + 10 + 10 + 10 + 5 = 55.

Documentation and upkeep Hy-Memory-30B-A3B +27

Hy-Memory-30B-A3B 68

Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.

MiniMax-M3.1-Flash 41

The model card earns 11, missing limitations, languages and a knowledge cut-off. Training data earns nothing, as it isn't described. The last change earns 20, an evaluation-results commit of 30 October 2026 after the release commit of 23 October. Responsiveness earns nothing, with no MiniMax reply in nine discussions opened from 23 to 31 October. Version policy earns 5 for a first release in its own repository. File health earns 5, for the tokenizer's 40,960,000-token model_max_length against the 1M context, the Transformers library tag against the card, and an unanswered vLLM streaming report. 11 + 0 + 20 + 0 + 5 + 5 = 41.

Risk Hy-Memory-30B-A3B +25

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.

MiniMax-M3.1-Flash 35

File safety earns 15, safetensors only, less 10 because the SGLang route the card links passes trust_remote_code for the repository's configuration and processor code. Provenance earns the full 15, files in the organisation MiniMax links to with a SHA-256 for each shard. Safety evaluation and agent guidance earn nothing; the launch post's security testing measured offensive capability, and the template's root role isn't documented as a trained hierarchy. Licence risk earns 5, after the military-use ban and the $20M threshold. The security programme earns nothing, with no security.txt, disclosure policy or advisories.

Agent interface MiniMax-M3.1-Flash +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.

MiniMax-M3.1-Flash 70

The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 10, since only the template shows the format and the parsers come from vLLM's and SGLang's own docs. Trained tool calling earns 20, with several invoke blocks in one call. Structured output earns nothing, as it isn't documented. Reasoning control earns 10, with reasoning_effort per request on the card and the reasoning in mm:think tags. Context earns 10 for 1,048,576 tokens with no position scaling.

Score by category

CategoryWeight this runHy-Memory-30B-A3BMiniMax-M3.1-FlashEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258555Hy-Memory-30B-A3B +30
Risk20%206035Hy-Memory-30B-A3B +25
Agent interface10%106570MiniMax-M3.1-Flash +5
Documentation and upkeep10%106841Hy-Memory-30B-A3B +27
Negative events≤1500
TotalC 61/100C 54.3/100

Facts side by side

FactHy-Memory-30B-A3BMiniMax-M3.1-Flash
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MiniMax Community License (custom; commercial use needs a "Built with MiniMax M3.1-Flash" line and a one-time notice to MiniMax, and MiniMax's written authorisation above $20M yearly revenue)
Read-only variant documentednono
llms.txtnono
Last release2026-10-162026-10-23
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.3/5 (4)

How the scores have moved

Verdicts

Hy-Memory-30B-A3B

A specialist that writes an agent's long-term memory, built to slot into Mem0, MemOS or Tencent's own framework in place of a general model. It fits a 24 GB card from Tencent's own GGUF, under plain Apache 2.0, and Tencent answers on the repository. Its results are Tencent's own and nobody has rerun them.

MiniMax-M3.1-Flash

A 428B mixture-of-experts model, 23B active, for agent work, coding and computer use, with image and video input, about 1M tokens of context and parallel tool calls. It needs a 4 to 8 GPU server for 250 GB of NVFP4 and MXFP8 weights. vLLM 0.33.0 and SGLang 0.5.23 carry its code. Commercial use needs attribution and notice.

Before you call either

Hy-Memory-30B-A3B

  1. Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
  2. Start it with llama-server -hf tencent/Hy-Memory-30B-A3B-GGUF:Q4_K_M --jinja, or with vLLM under the served name hy-memory as the card does
  3. Pass reasoning_effort as no_think in chat_template_kwargs and temperature 0, as the card's example does
  4. Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
  5. Treat what it stores as unverified. It keeps what a conversation says, true or not

MiniMax-M3.1-Flash

  1. Check the use case first; commercial products must show "Built with MiniMax M3.1-Flash" and notify MiniMax once, or get written authorisation above $20M yearly revenue
  2. On 8 H100 or H200 GPUs use vLLM 0.33.0 or later, or the recipe's image vllm/vllm-openai:minimax-m31-flash, with --tensor-parallel-size 8 --block-size 128 --kv-cache-dtype fp8 --moe-backend marlin --max-model-len 262144
  3. Pass --reasoning-parser minimax_m3 --tool-call-parser minimax_m3 --enable-auto-tool-choice in vLLM, or minimax-m3 for both in SGLang with --trust-remote-code
  4. --block-size 128 is mandatory in vLLM, since MSA's sparse block size is 128
  5. Set effort per request with chat_template_kwargs reasoning_effort (low, medium, high, xhigh, max); sample at temperature 1.0 and top_p 0.95
  6. On Blackwell or MI355X, 4 GPUs serve it with the DSpark draft from dspark/; vLLM's Hopper command leaves DSpark off and turns video input off
  7. For GGUF builds by others, use llama.cpp b11861 or later; earlier builds mis-scale the NVFP4 experts and produce garbage
  8. Without the hardware, call MiniMax-M3.1-Flash on MiniMax's API (minimax-api), whose thinking defaults to max effort

Questions

Which is better for AI agents, Hy-Memory-30B-A3B or MiniMax-M3.1-Flash?

Hy-Memory-30B-A3B scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 54.3 (C), and leads in 3 of 4 scored categories. MiniMax-M3.1-Flash leads on agent interface.

Other comparisons with Hy-Memory-30B-A3B or MiniMax-M3.1-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.