Head to head · Open-weight models you run yourself · October 2026 research run
Hy-Memory-30B-A3B vs Inkling 2 Mini
Hy-Memory-30B-A3B and Inkling 2 Mini score within a point of each other on agent readiness, 61 (C) and 61 (C). Inkling 2 Mini 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 6586 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 60
- Documentation and upkeep, 68 against 57
Watch for
Not a general assistant or a tool caller
Best for Developers with a 32 GB laptop or a single GPU who want a small open agent model with images in and a 1M context, and can run a runtime's pre-release build.
Ahead on
- Risk, 70 against 60
- Agent interface, 85 against 65
Watch for
No released version of vLLM, SGLang, Transformers, llama.cpp or Ollama runs it on 20 November 2026
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 +25
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.
Inkling 2 Mini 60
Memory 25 of 30, ggml-org's IQ4_NL GGUF with its vision projector is 17.98 GB, about 21.6 GB with a fifth added. Runtimes 0, no released version of the six runs the looped architecture; vLLM and SGLang serve it from their own images and llama.cpp has it on master only. Builds 10, one checkpoint from the publisher in mixed NVFP4 and MXFP8. Terms 10, Apache 2.0 with a binding acceptable use policy on top, read as a custom licence. Download 10, no gate. Hosted 5, Thinking Machines' own Tinker samples from it. 25 + 0 + 10 + 10 + 10 + 5 = 60.
Agent interface Inkling 2 Mini +20
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.
Inkling 2 Mini 85
Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, tml-renderers renders and parses it, and vLLM and SGLang name their parsers. Trained tool calling 20, several calls in one turn. Structured output 0, not documented. Reasoning control 10, reasoning_effort per request. Context 10, 1M trained. 20 + 25 + 20 + 0 + 10 + 10 = 85.
Documentation and upkeep Hy-Memory-30B-A3B +11
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, tokeniser and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.
Inkling 2 Mini 57
Model card 17, no knowledge cut-off. Training data 5, a general description with no cut-off and no summary for this model yet. Last change 20, uploaded today. Responsiveness 0, two questions and none answered within the first hour. Version policy 5, a first release. File health 10, the files and the card agree. 17 + 5 + 20 + 0 + 5 + 10 = 57.
Risk Inkling 2 Mini +10
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.
Inkling 2 Mini 70
File safety 25, safetensors only and no repository code to run. Provenance 15, the files are in the organisation Thinking Machines links to, with a SHA-256 on every LFS file. Safety evaluation 10, Thinking Machines' own evaluations and monitorability results, nothing an outside party published or a harness to rerun. Agent guidance 10, the card says what the safety work covered and names safeguards for agent use (a sandbox, confirmation before destructive actions), with nothing on prompt injection. Licence risk 5, 10 off for a use policy that reaches beyond the law and that can change at any time. Security 5, security.txt and a disclosure policy. 25 + 15 + 10 + 10 + 5 + 5 = 70.
Score by category
| Category | Weight | Hy-Memory-30B-A3B | Inkling 2 Mini | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25% | 85 | 60 | Hy-Memory-30B-A3B +25 |
| Risk | 20% | 60 | 70 | Inkling 2 Mini +10 |
| Agent interface | 10% | 65 | 85 | Inkling 2 Mini +20 |
| Documentation and upkeep | 10% | 68 | 57 | Hy-Memory-30B-A3B +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 61/100 |
Facts side by side
| Fact | Hy-Memory-30B-A3B | Inkling 2 Mini |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | Thinking Machines Lab |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-16 | 2026-11-20 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
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.
Inkling 2 Mini
Thinking Machines' small open model, a looped 26.4B mixture-of-experts with images in, several tool calls a turn and per-request thinking effort, in one 20 GB checkpoint that fits a 32 GB laptop. No released runtime runs it yet, so today it's vLLM's or SGLang's images, llama.cpp from master, or Tinker.
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
Inkling 2 Mini
- No released runtime runs it yet. Serve it from vLLM's vllm/vllm-openai:inkling-2-mini image with
--reasoning-parser inkling --enable-auto-tool-choice --tool-call-parser inkling, or from SGLang's lmsysorg/sglang:inkling-2-mini image, where the tool-call parser isinkling2 - On a laptop, ggml-org's GGUF runs in a llama.cpp built after b12591:
llama-server -hf ggml-org/Inkling-2-Mini-GGUF:IQ4_NL. The looped architecture isn't in a llama.cpp release yet - Pass
reasoning_effortas none, minimal, low, medium, high (the default), xhigh or max, or a number from 0 to 0.99. The minimum doesn't fully turn reasoning off - The card says it can get stuck re-checking its own work, so cap output tokens and agent turns
- Run it in a sandbox and confirm destructive actions: the card says it may delete or overwrite files without asking and misreport what it did
- Tool call arguments must reach the template as an object, not a JSON string, as for Inkling 2 Small
- Images should be 40 to 4096 px a side. It takes no audio, and the template raises an error for an audio part
- Use guided decoding or validate JSON yourself, since structured output isn't documented
- Without the hardware, sample from it on Tinker with the Tinker SDK; Tinker's OpenAI-compatible endpoint doesn't serve it yet
- Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal
Questions
Which is better for AI agents, Hy-Memory-30B-A3B or Inkling 2 Mini?
Hy-Memory-30B-A3B and Inkling 2 Mini score within a point of each other on agent readiness, 61 (C) and 61 (C). Inkling 2 Mini leads on risk and agent interface.
Other comparisons with Hy-Memory-30B-A3B or Inkling 2 Mini
- Agents-A1-4B vs Hy-Memory-30B-A3B
- Agents-A1-4B vs Inkling 2 Mini
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs Inkling 2 Mini
- Apodex-1.1-mini vs Hy-Memory-30B-A3B
- Apodex-1.1-mini vs Inkling 2 Mini
- Arete-27B vs Hy-Memory-30B-A3B
- Arete-27B vs Inkling 2 Mini
- BigBang-v1 vs Hy-Memory-30B-A3B
- BigBang-v1 vs Inkling 2 Mini
- Carbon-X vs Hy-Memory-30B-A3B
- Carbon-X vs Inkling 2 Mini
- Cola2 vs Hy-Memory-30B-A3B
- Cola2 vs Inkling 2 Mini
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Cosmos-Reason2-2B vs Inkling 2 Mini
- Darwin-36B-Opus vs Hy-Memory-30B-A3B
- Darwin-36B-Opus vs Inkling 2 Mini
- DeepSeek-V3.2 vs Hy-Memory-30B-A3B
- DeepSeek-V3.2 vs Inkling 2 Mini
- DeepSeek V4.1 Flash vs Hy-Memory-30B-A3B
- DeepSeek V4.1 Flash vs Inkling 2 Mini
- DeepSeek-V4-Flash-0731 vs Hy-Memory-30B-A3B
- DeepSeek-V4-Flash-0731 vs Inkling 2 Mini
- Devstral Small 2 vs Hy-Memory-30B-A3B
- Devstral Small 2 vs Inkling 2 Mini
- DiffusionGemma 26B A4B IT vs Hy-Memory-30B-A3B
- DiffusionGemma 26B A4B IT vs Inkling 2 Mini
- EXAONE 4.5 33B vs Hy-Memory-30B-A3B
- EXAONE 4.5 33B vs Inkling 2 Mini
- Gemma 4 12B IT vs Hy-Memory-30B-A3B
- Gemma 4 12B IT vs Inkling 2 Mini
- Gemma 4 26B A4B IT vs Hy-Memory-30B-A3B
- Gemma 4 26B A4B IT vs Inkling 2 Mini
- Gemma 4 31B IT vs Hy-Memory-30B-A3B
- Gemma 4 31B IT vs Inkling 2 Mini
- Gemma 4 E2B IT vs Hy-Memory-30B-A3B
- Gemma 4 E2B IT vs Inkling 2 Mini
- Gemma 4 E4B IT vs Hy-Memory-30B-A3B
- Gemma 4 E4B IT vs Inkling 2 Mini
- GLM-4.5-Air vs Hy-Memory-30B-A3B
- GLM-4.5-Air vs Inkling 2 Mini
- GLM-4.7-Flash vs Hy-Memory-30B-A3B
- GLM-4.7-Flash vs Inkling 2 Mini
- GLM-5.3-Flash vs Hy-Memory-30B-A3B
- GLM-5.3-Flash vs Inkling 2 Mini
- GLM-5.3 vs Hy-Memory-30B-A3B
- GLM-5.3 vs Inkling 2 Mini
- gpt-oss-120b vs Hy-Memory-30B-A3B
- gpt-oss-120b vs Inkling 2 Mini
- gpt-oss-20b vs Hy-Memory-30B-A3B
- gpt-oss-20b vs Inkling 2 Mini
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs Inkling 2 Mini
- Granite 4.2 3B vs Hy-Memory-30B-A3B
- Granite 4.2 3B vs Inkling 2 Mini
- Granite 4.2 8B vs Hy-Memory-30B-A3B
- Granite 4.2 8B vs Inkling 2 Mini
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs Inkling
- Hy-Memory-30B-A3B vs Inkling 2 Small
- 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
- 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 LongCat-2.5
- Hy-Memory-30B-A3B vs MiMo-V2.6 Distill Qwen 9B
- Hy-Memory-30B-A3B vs MiMo-V2.6-Flash-RL
- 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.2-3B
- 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 North Mini Code 1.0
- 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 OTel-2.0-LLM-31B-IT
- 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 SenseNova-Loop-9B-Preview
- Hy-Memory-30B-A3B vs SmolLM3-3B
- Hy-Memory-30B-A3B vs Spark-X2.6-4B
- Hy-Memory-30B-A3B vs Step 3.7 Flash
- 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
- Hy-Memory-30B-A3B vs WeVisOne-VL-2B
- Hy-Memory-30B-A3B vs WeVisOne-VL-4B
- Hy-Memory-30B-A3B vs ZAYA1-8B
- Hy3 vs Inkling 2 Mini
- Inkling 2 Mini vs Inkling 2 Small
- Inkling 2 Mini vs Inkling-Small
- Inkling 2 Mini vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Inkling 2 Mini vs Kimi K3
- Inkling 2 Mini vs Kimi K3.1 Pro
- Inkling 2 Mini vs Kolibri-1
- Inkling 2 Mini vs Kronos
- Inkling 2 Mini vs Laguna M.1
- Inkling 2 Mini vs Laguna S 2.1
- Inkling 2 Mini vs Laguna XS 2.1
- Inkling 2 Mini vs LBS-27B
- Inkling 2 Mini vs LFM2.5-2.6B
- Inkling 2 Mini vs LFM3-1.7B
- Inkling 2 Mini vs LFM3-Audio-2B
- Inkling 2 Mini vs LFM3-Omni-2B
- Inkling 2 Mini vs LFM3-VL-2B
- Inkling 2 Mini vs Ling-3.0-tiny
- Inkling 2 Mini vs Ling-3.1-flash-1019
- Inkling 2 Mini vs LongCat-2.5
- Inkling 2 Mini vs MiMo-V2.6 Distill Qwen 9B
- Inkling 2 Mini vs MiMo-V2.6-Flash-RL
- Inkling 2 Mini vs MiniCPM-o 4.5
- Inkling 2 Mini vs MiniCPM-V 4.7 1B
- Inkling 2 Mini vs MiniCPM-V 4.7 35B-A3B
- Inkling 2 Mini vs MiniCPM5-2B
- Inkling 2 Mini vs MiniMax-M2.5
- Inkling 2 Mini vs MiniMax-M2.7
- Inkling 2 Mini vs MiniMax-M3.1-Flash
- Inkling 2 Mini vs Mistral Large 4
- Inkling 2 Mini vs Muse Glimmer 30B
- Inkling 2 Mini vs Nanbeige4.2-3B
- Inkling 2 Mini vs Nanbeige4.3-33B
- Inkling 2 Mini vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Inkling 2 Mini vs Nemotron 3.5 Lightning 30B A3B
- Inkling 2 Mini vs Nemotron 3 Nano 30B A3B
- Inkling 2 Mini vs Nemotron 3 Nano 4B
- Inkling 2 Mini vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Inkling 2 Mini vs Nemotron 3 Super 120B A12B
- Inkling 2 Mini vs Nemotron 3 Ultra 550B A55B
- Inkling 2 Mini vs North Mini Code 1.0
- Inkling 2 Mini vs occamy-1.0
- Inkling 2 Mini vs Olmo 3 7B Think
- Inkling 2 Mini vs Ornith-1.5-122B
- Inkling 2 Mini vs Ornith-1.5-35B-A3B
- Inkling 2 Mini vs Ornith-1.5-397B
- Inkling 2 Mini vs Ornith-1.5-9B
- Inkling 2 Mini vs OTel-2.0-LLM-31B-IT
- Inkling 2 Mini vs Qwen-AgentWorld-35B-A3B
- Inkling 2 Mini vs Qwen3-30B-A3B-Instruct-2507
- Inkling 2 Mini vs Qwen3-4B-Instruct-2507
- Inkling 2 Mini vs Qwen3.5-0.8B
- Inkling 2 Mini vs Qwen3.5-122B-A10B
- Inkling 2 Mini vs Qwen3.5-2B
- Inkling 2 Mini vs Qwen3.5-397B-A17B
- Inkling 2 Mini vs Qwen3.5-4B
- Inkling 2 Mini vs Qwen3.5-9B
- Inkling 2 Mini vs Qwen3.6-27B
- Inkling 2 Mini vs Qwen3.6-35B-A3B
- Inkling 2 Mini vs Qwen3.8-27B
- Inkling 2 Mini vs Qwen3.8-Flash-Next
- Inkling 2 Mini vs Qwen3-Coder-30B-A3B-Instruct
- Inkling 2 Mini vs Qwen3-Coder-Next
- Inkling 2 Mini vs Qwen3-Omni-30B-A3B-Instruct
- Inkling 2 Mini vs Qwen3-VL-2B-Instruct
- Inkling 2 Mini vs Qwen3-VL-30B-A3B-Instruct
- Inkling 2 Mini vs Qwen3-VL-32B-Instruct
- Inkling 2 Mini vs Qwen3-VL-4B-Instruct
- Inkling 2 Mini vs Qwen3-VL-8B-Instruct
- Inkling 2 Mini vs Qwopus3.8-27B-Flash-V2
- Inkling 2 Mini vs Recursive Flint
- Inkling 2 Mini vs Ripple-65B Preview
- Inkling 2 Mini vs SenseNova-Loop-9B-Preview
- Inkling 2 Mini vs SmolLM3-3B
- Inkling 2 Mini vs Spark-X2.6-4B
- Inkling 2 Mini vs Step 3.7 Flash
- Inkling 2 Mini vs Swift 1.5 Qwen3.8-27B
- Inkling 2 Mini vs Swift 1.5 Qwen3.8-Flash-Next
- Inkling 2 Mini vs ThinkingCap (Qwen3.8 27B)
- Inkling 2 Mini vs Baidu Unlimited-OCR-2
- Inkling 2 Mini vs WeVisOne-VL-2B
- Inkling 2 Mini vs WeVisOne-VL-4B
- Inkling 2 Mini vs ZAYA1-8B
- Inkling vs Inkling 2 Mini
Machine-readable
- This page as Markdown
/compare/hy-memory-30b-a3b-vs-inkling-2-mini.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/inkling-2-mini.json - From a terminal
anchor compare hy-memory-30b-a3b inkling-2-mini(the CLI) - Over MCP
compare_tools {"a": "hy-memory-30b-a3b", "b": "inkling-2-mini"}at/mcp, no key