Head to head · Open-weight models you run yourself · October 2026 research run
Hy-Memory-30B-A3B vs Kimi K3
Kimi K3 scores 62.4 (B) on agent readiness against Hy-Memory-30B-A3B's 61 (C), and leads in 1 of 4 scored categories. Hy-Memory-30B-A3B 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 4969 open weights comparisons
Which one, for what
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 50
- Documentation and upkeep, 68 against 41
Watch for
Not a general assistant or a tool caller
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 60
Watch for
1,561 GB of files at its smallest publisher build, far beyond any single machine
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 +35
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.
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.
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.
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.
Risk Kimi K3 +5
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.
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.
Score by category
| Category | Weight this run | Hy-Memory-30B-A3B | Kimi K3 | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 50 | Hy-Memory-30B-A3B +35 |
| Risk | 20%20 | 60 | 65 | Kimi K3 +5 |
| Agent interface | 10%10 | 65 | 65 | even |
| Documentation and upkeep | 10%10 | 68 | 41 | Hy-Memory-30B-A3B +27 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | B 62.4/100 |
Facts side by side
| Fact | Hy-Memory-30B-A3B | Kimi K3 |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | Moonshot AI |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Kimi K3 License (modified MIT) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-16 | 2026-09-02 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 2.3/5 (4) |
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.
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.
Before you call either
Hy-Memory-30B-A3B
- Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
- 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 - Pass
reasoning_effortas no_think inchat_template_kwargsand temperature 0, as the card's example does - Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
- Treat what it stores as unverified. It keeps what a conversation says, true or not
Kimi K3
- 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
- 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
- Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
- Thinking is always on; set reasoning_effort to low or high when max is too slow
- Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
- 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
- Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page
Questions
Which is better for AI agents, Hy-Memory-30B-A3B or Kimi K3?
Kimi K3 scores 62.4 (B) on agent readiness against Hy-Memory-30B-A3B's 61 (C), and leads in 1 of 4 scored categories. Hy-Memory-30B-A3B leads on reach and documentation and upkeep.
Other comparisons with Hy-Memory-30B-A3B or Kimi K3
- Agents-A1-4B vs Hy-Memory-30B-A3B
- Agents-A1-4B vs Kimi K3
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs Kimi K3
- Apodex-1.1-mini vs Hy-Memory-30B-A3B
- Apodex-1.1-mini vs Kimi K3
- Arete-27B vs Hy-Memory-30B-A3B
- Arete-27B vs Kimi K3
- BigBang-v1 vs Hy-Memory-30B-A3B
- BigBang-v1 vs Kimi K3
- Carbon-X vs Hy-Memory-30B-A3B
- Carbon-X vs Kimi K3
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Cosmos-Reason2-2B vs Kimi K3
- Darwin-36B-Opus vs Hy-Memory-30B-A3B
- Darwin-36B-Opus vs Kimi K3
- DeepSeek-V3.2 vs Hy-Memory-30B-A3B
- DeepSeek-V3.2 vs Kimi K3
- DeepSeek V4.1 Flash vs Hy-Memory-30B-A3B
- DeepSeek V4.1 Flash vs Kimi K3
- DeepSeek-V4-Flash-0731 vs Hy-Memory-30B-A3B
- DeepSeek-V4-Flash-0731 vs Kimi K3
- DiffusionGemma 26B A4B IT vs Hy-Memory-30B-A3B
- DiffusionGemma 26B A4B IT vs Kimi K3
- Gemma 4 12B IT vs Hy-Memory-30B-A3B
- Gemma 4 12B IT vs Kimi K3
- Gemma 4 26B A4B IT vs Hy-Memory-30B-A3B
- Gemma 4 26B A4B IT vs Kimi K3
- Gemma 4 31B IT vs Hy-Memory-30B-A3B
- Gemma 4 31B IT vs Kimi K3
- Gemma 4 E2B IT vs Hy-Memory-30B-A3B
- Gemma 4 E2B IT vs Kimi K3
- Gemma 4 E4B IT vs Hy-Memory-30B-A3B
- Gemma 4 E4B IT vs Kimi K3
- GLM-4.5-Air vs Hy-Memory-30B-A3B
- GLM-4.5-Air vs Kimi K3
- GLM-4.7-Flash vs Hy-Memory-30B-A3B
- GLM-4.7-Flash vs Kimi K3
- GLM-5.3-Flash vs Hy-Memory-30B-A3B
- GLM-5.3-Flash vs Kimi K3
- GLM-5.3 vs Hy-Memory-30B-A3B
- GLM-5.3 vs Kimi K3
- gpt-oss-120b vs Hy-Memory-30B-A3B
- gpt-oss-120b vs Kimi K3
- gpt-oss-20b vs Hy-Memory-30B-A3B
- gpt-oss-20b vs Kimi K3
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs Kimi K3
- Granite 4.2 3B vs Hy-Memory-30B-A3B
- Granite 4.2 3B vs Kimi K3
- Granite 4.2 8B vs Hy-Memory-30B-A3B
- Granite 4.2 8B vs Kimi K3
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs Inkling
- Hy-Memory-30B-A3B vs Inkling-Small
- Hy-Memory-30B-A3B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy-Memory-30B-A3B vs Kimi K3.1 Pro
- Hy-Memory-30B-A3B vs Kolibri-1
- Hy-Memory-30B-A3B vs Kronos
- Hy-Memory-30B-A3B vs Laguna M.1
- Hy-Memory-30B-A3B vs Laguna S 2.1
- Hy-Memory-30B-A3B vs Laguna XS 2.1
- Hy-Memory-30B-A3B vs LBS-27B
- Hy-Memory-30B-A3B vs LFM2.5-2.6B
- Hy-Memory-30B-A3B vs LFM3-1.7B
- Hy-Memory-30B-A3B vs LFM3-Audio-2B
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs Ling-3.0-tiny
- Hy-Memory-30B-A3B vs Ling-3.1-flash-1019
- Hy-Memory-30B-A3B vs MiMo-V2.6 Distill Qwen 9B
- Hy-Memory-30B-A3B vs MiniCPM-o 4.5
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 1B
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 35B-A3B
- Hy-Memory-30B-A3B vs MiniCPM5-2B
- Hy-Memory-30B-A3B vs MiniMax-M2.5
- Hy-Memory-30B-A3B vs MiniMax-M2.7
- Hy-Memory-30B-A3B vs MiniMax-M3.1-Flash
- Hy-Memory-30B-A3B vs Mistral Large 4
- Hy-Memory-30B-A3B vs Muse Glimmer 30B
- Hy-Memory-30B-A3B vs Nanbeige4.3-33B
- Hy-Memory-30B-A3B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Hy-Memory-30B-A3B vs Nemotron 3.5 Lightning 30B A3B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano 30B A3B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano 4B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy-Memory-30B-A3B vs Nemotron 3 Super 120B A12B
- Hy-Memory-30B-A3B vs Nemotron 3 Ultra 550B A55B
- Hy-Memory-30B-A3B vs occamy-1.0
- Hy-Memory-30B-A3B vs Olmo 3 7B Think
- Hy-Memory-30B-A3B vs Ornith-1.5-122B
- Hy-Memory-30B-A3B vs Ornith-1.5-35B-A3B
- Hy-Memory-30B-A3B vs Ornith-1.5-397B
- Hy-Memory-30B-A3B vs Ornith-1.5-9B
- Hy-Memory-30B-A3B vs Qwen-AgentWorld-35B-A3B
- Hy-Memory-30B-A3B vs Qwen3-30B-A3B-Instruct-2507
- Hy-Memory-30B-A3B vs Qwen3-4B-Instruct-2507
- Hy-Memory-30B-A3B vs Qwen3.5-0.8B
- Hy-Memory-30B-A3B vs Qwen3.5-122B-A10B
- Hy-Memory-30B-A3B vs Qwen3.5-2B
- Hy-Memory-30B-A3B vs Qwen3.5-397B-A17B
- Hy-Memory-30B-A3B vs Qwen3.5-4B
- Hy-Memory-30B-A3B vs Qwen3.5-9B
- Hy-Memory-30B-A3B vs Qwen3.6-27B
- Hy-Memory-30B-A3B vs Qwen3.6-35B-A3B
- Hy-Memory-30B-A3B vs Qwen3.8-27B
- Hy-Memory-30B-A3B vs Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs Qwen3-Coder-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-Coder-Next
- Hy-Memory-30B-A3B vs Qwen3-Omni-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-2B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-32B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-4B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-8B-Instruct
- Hy-Memory-30B-A3B vs Qwopus3.8-27B-Flash-V2
- Hy-Memory-30B-A3B vs Recursive Flint
- Hy-Memory-30B-A3B vs Ripple-65B Preview
- Hy-Memory-30B-A3B vs SmolLM3-3B
- Hy-Memory-30B-A3B vs Spark-X2.6-4B
- Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-27B
- Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs ThinkingCap (Qwen3.8 27B)
- Hy-Memory-30B-A3B vs Baidu Unlimited-OCR-2
- Hy3 vs Kimi K3
- Inkling-Small vs Kimi K3
- Inkling vs Kimi K3
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kimi K3
- Kimi K3 vs Kimi K3.1 Pro
- Kimi K3 vs Kolibri-1
- Kimi K3 vs Kronos
- Kimi K3 vs Laguna M.1
- Kimi K3 vs Laguna S 2.1
- Kimi K3 vs Laguna XS 2.1
- Kimi K3 vs LBS-27B
- Kimi K3 vs LFM2.5-2.6B
- Kimi K3 vs LFM3-1.7B
- Kimi K3 vs LFM3-Audio-2B
- Kimi K3 vs LFM3-Omni-2B
- Kimi K3 vs LFM3-VL-2B
- Kimi K3 vs Ling-3.0-tiny
- Kimi K3 vs Ling-3.1-flash-1019
- Kimi K3 vs MiMo-V2.6 Distill Qwen 9B
- Kimi K3 vs MiniCPM-o 4.5
- Kimi K3 vs MiniCPM-V 4.7 1B
- Kimi K3 vs MiniCPM-V 4.7 35B-A3B
- Kimi K3 vs MiniCPM5-2B
- Kimi K3 vs MiniMax-M2.5
- Kimi K3 vs MiniMax-M2.7
- Kimi K3 vs MiniMax-M3.1-Flash
- Kimi K3 vs Mistral Large 4
- Kimi K3 vs Muse Glimmer 30B
- Kimi K3 vs Nanbeige4.3-33B
- Kimi K3 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kimi K3 vs Nemotron 3.5 Lightning 30B A3B
- Kimi K3 vs Nemotron 3 Nano 30B A3B
- Kimi K3 vs Nemotron 3 Nano 4B
- Kimi K3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kimi K3 vs Nemotron 3 Super 120B A12B
- Kimi K3 vs Nemotron 3 Ultra 550B A55B
- Kimi K3 vs occamy-1.0
- Kimi K3 vs Olmo 3 7B Think
- Kimi K3 vs Ornith-1.5-122B
- Kimi K3 vs Ornith-1.5-35B-A3B
- Kimi K3 vs Ornith-1.5-397B
- Kimi K3 vs Ornith-1.5-9B
- Kimi K3 vs Qwen-AgentWorld-35B-A3B
- Kimi K3 vs Qwen3-30B-A3B-Instruct-2507
- Kimi K3 vs Qwen3-4B-Instruct-2507
- Kimi K3 vs Qwen3.5-0.8B
- Kimi K3 vs Qwen3.5-122B-A10B
- Kimi K3 vs Qwen3.5-2B
- Kimi K3 vs Qwen3.5-397B-A17B
- Kimi K3 vs Qwen3.5-4B
- Kimi K3 vs Qwen3.5-9B
- Kimi K3 vs Qwen3.6-27B
- Kimi K3 vs Qwen3.6-35B-A3B
- Kimi K3 vs Qwen3.8-27B
- Kimi K3 vs Qwen3.8-Flash-Next
- Kimi K3 vs Qwen3-Coder-30B-A3B-Instruct
- Kimi K3 vs Qwen3-Coder-Next
- Kimi K3 vs Qwen3-Omni-30B-A3B-Instruct
- Kimi K3 vs Qwen3-VL-2B-Instruct
- Kimi K3 vs Qwen3-VL-30B-A3B-Instruct
- Kimi K3 vs Qwen3-VL-32B-Instruct
- Kimi K3 vs Qwen3-VL-4B-Instruct
- Kimi K3 vs Qwen3-VL-8B-Instruct
- Kimi K3 vs Qwopus3.8-27B-Flash-V2
- Kimi K3 vs Recursive Flint
- Kimi K3 vs Ripple-65B Preview
- Kimi K3 vs SmolLM3-3B
- Kimi K3 vs Spark-X2.6-4B
- Kimi K3 vs Swift 1.5 Qwen3.8-27B
- Kimi K3 vs Swift 1.5 Qwen3.8-Flash-Next
- Kimi K3 vs ThinkingCap (Qwen3.8 27B)
- Kimi K3 vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/hy-memory-30b-a3b-vs-kimi-k3.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy-memory-30b-a3b.json·/api/v1/tools/kimi-k3.json - From a terminal
anchor compare hy-memory-30b-a3b kimi-k3(the CLI) - Over MCP
compare_tools {"a": "hy-memory-30b-a3b", "b": "kimi-k3"}at/mcp, no key