Head to head · Open-weight models you run yourself · October 2026 research run
Hy-Memory-30B-A3B vs WeVisOne-VL-4B
Hy-Memory-30B-A3B and WeVisOne-VL-4B score within a point of each other on agent readiness, 61 (C) and 61 (C). WeVisOne-VL-4B 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 6359 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 70
- Risk, 60 against 55
- Documentation and upkeep, 68 against 48
Watch for
Not a general assistant or a tool caller
Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence
Ahead on
- Agent interface, 70 against 65
Watch for
The pixel decoder ships as a pickle file
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.
Documentation and upkeep Hy-Memory-30B-A3B +20
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.
WeVisOne-VL-4B 48
Model card 8, Intended use, limitations and the architecture are on the card. Training data 5, A general description in the README of a data engine and over 100 million annotated images, with no sources named and no cut-off. Last change 20, the last commit, on 27 October 2026, added links to the paper and project page, 14 days before this check. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (23 and 26 October 2026) has a reply from a tencent member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, 14 days old. File health 10, Config, template and card agree on the Qwen3-VL classes, and the card names mask_decoder.pt as required and it's there. 8 + 5 + 20 + 0 + 5 + 10 = 48.
Reach Hy-Memory-30B-A3B +15
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.
WeVisOne-VL-4B 70
Memory 30, the only build from Tencent is the BF16 safetensors file with its decoder, 9.7 GB, and 9.7 GB × 1.2 = 11.6 GB, within 16 GB. No runtime library has a build. Runtimes 15, the architecture is Qwen3VLForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors file, three at 5 each. Builds 0, Tencent publishes the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata with the LICENSE file in the repository, and nothing added. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 30 + 15 + 0 + 15 + 10 + 0 = 70.
Risk Hy-Memory-30B-A3B +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.
WeVisOne-VL-4B 55
File safety 15, the backbone is safetensors, but mask_decoder.pt, a PyTorch pickle the card calls a required component, sits beside it. Provenance 15, the files sit in the tencent organisation, which Tencent's GitHub repository for the model links to (10), and the Hub gives a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the README. Agent guidance 5, General cautions: the card says the release is for research, isn't for autonomous high-impact decisions or identifying individuals, and lists where masks go wrong. Licence risk 15, Apache 2.0 with no use policy, no threshold and no right to change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide, as the Hy3 listing records (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.
Agent interface WeVisOne-VL-4B +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.
WeVisOne-VL-4B 70
Chat template 20, chat_template.jinja in the repository (5,292 characters), Qwen3-VL's template. Tool-calling format 25, Read for a perception model as what it takes and returns. Trained tool calling 10, Read for a perception model as the inputs it was trained to use. Structured output 15, Read for a perception model as typed outputs. Reasoning control 0, the card says it writes structured output directly with no chain-of-thought reasoning. Context 0, Tencent states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.
Score by category
| Category | Weight this run | Hy-Memory-30B-A3B | WeVisOne-VL-4B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 70 | Hy-Memory-30B-A3B +15 |
| Risk | 20%20 | 60 | 55 | Hy-Memory-30B-A3B +5 |
| Agent interface | 10%10 | 65 | 70 | WeVisOne-VL-4B +5 |
| Documentation and upkeep | 10%10 | 68 | 48 | Hy-Memory-30B-A3B +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 61/100 |
Facts side by side
| Fact | Hy-Memory-30B-A3B | WeVisOne-VL-4B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | Tencent (WeChat Vision) |
| 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-10-27 |
| Terms last updated | no document linked | not read yet |
| 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.
WeVisOne-VL-4B
A small Apache 2.0 perception model that finds, counts, reads and cuts out what you name in an image, and says None when it isn't there. Boxes and points run in vLLM, SGLang or Transformers. Masks and mattes need Tencent's package and a pickle file. Two weeks old, with no questions answered yet and no safety results.
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
WeVisOne-VL-4B
- Use Tencent's package:
WeVisOneVL("tencent/WeVisOne-VL-4B", backend="vllm")thenmodel.predict(image, task=..., query=...) - Tasks are detection, referring, point, count_box, count_point, ocr, ocr_grounding, segmentation and matting
- A None answer means the target isn't in the image. Treat it as a result, not an error
- mask_decoder.pt is a pickle. Load it only from the tencent repository, and check its SHA-256 against the Hub's
- Send one image a turn. Video grids are rejected by the decoder
- The card says it isn't for identifying individuals or for high-impact decisions on its own
Questions
Which is better for AI agents, Hy-Memory-30B-A3B or WeVisOne-VL-4B?
Hy-Memory-30B-A3B and WeVisOne-VL-4B score within a point of each other on agent readiness, 61 (C) and 61 (C). WeVisOne-VL-4B leads on agent interface.
Other comparisons with Hy-Memory-30B-A3B or WeVisOne-VL-4B
- Agents-A1-4B vs Hy-Memory-30B-A3B
- Agents-A1-4B vs WeVisOne-VL-4B
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs WeVisOne-VL-4B
- Apodex-1.1-mini vs Hy-Memory-30B-A3B
- Apodex-1.1-mini vs WeVisOne-VL-4B
- Arete-27B vs Hy-Memory-30B-A3B
- Arete-27B vs WeVisOne-VL-4B
- BigBang-v1 vs Hy-Memory-30B-A3B
- BigBang-v1 vs WeVisOne-VL-4B
- Carbon-X vs Hy-Memory-30B-A3B
- Carbon-X vs WeVisOne-VL-4B
- Cola2 vs Hy-Memory-30B-A3B
- Cola2 vs WeVisOne-VL-4B
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Cosmos-Reason2-2B vs WeVisOne-VL-4B
- Darwin-36B-Opus vs Hy-Memory-30B-A3B
- Darwin-36B-Opus vs WeVisOne-VL-4B
- DeepSeek-V3.2 vs Hy-Memory-30B-A3B
- DeepSeek-V3.2 vs WeVisOne-VL-4B
- DeepSeek V4.1 Flash vs Hy-Memory-30B-A3B
- DeepSeek V4.1 Flash vs WeVisOne-VL-4B
- DeepSeek-V4-Flash-0731 vs Hy-Memory-30B-A3B
- DeepSeek-V4-Flash-0731 vs WeVisOne-VL-4B
- Devstral Small 2 vs Hy-Memory-30B-A3B
- Devstral Small 2 vs WeVisOne-VL-4B
- DiffusionGemma 26B A4B IT vs Hy-Memory-30B-A3B
- DiffusionGemma 26B A4B IT vs WeVisOne-VL-4B
- EXAONE 4.5 33B vs Hy-Memory-30B-A3B
- EXAONE 4.5 33B vs WeVisOne-VL-4B
- Gemma 4 12B IT vs Hy-Memory-30B-A3B
- Gemma 4 12B IT vs WeVisOne-VL-4B
- Gemma 4 26B A4B IT vs Hy-Memory-30B-A3B
- Gemma 4 26B A4B IT vs WeVisOne-VL-4B
- Gemma 4 31B IT vs Hy-Memory-30B-A3B
- Gemma 4 31B IT vs WeVisOne-VL-4B
- Gemma 4 E2B IT vs Hy-Memory-30B-A3B
- Gemma 4 E2B IT vs WeVisOne-VL-4B
- Gemma 4 E4B IT vs Hy-Memory-30B-A3B
- Gemma 4 E4B IT vs WeVisOne-VL-4B
- GLM-4.5-Air vs Hy-Memory-30B-A3B
- GLM-4.5-Air vs WeVisOne-VL-4B
- GLM-4.7-Flash vs Hy-Memory-30B-A3B
- GLM-4.7-Flash vs WeVisOne-VL-4B
- GLM-5.3-Flash vs Hy-Memory-30B-A3B
- GLM-5.3-Flash vs WeVisOne-VL-4B
- GLM-5.3 vs Hy-Memory-30B-A3B
- GLM-5.3 vs WeVisOne-VL-4B
- gpt-oss-120b vs Hy-Memory-30B-A3B
- gpt-oss-120b vs WeVisOne-VL-4B
- gpt-oss-20b vs Hy-Memory-30B-A3B
- gpt-oss-20b vs WeVisOne-VL-4B
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs WeVisOne-VL-4B
- Granite 4.2 3B vs Hy-Memory-30B-A3B
- Granite 4.2 3B vs WeVisOne-VL-4B
- Granite 4.2 8B vs Hy-Memory-30B-A3B
- Granite 4.2 8B vs WeVisOne-VL-4B
- 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
- 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 ZAYA1-8B
- Hy3 vs WeVisOne-VL-4B
- Inkling-Small vs WeVisOne-VL-4B
- Inkling vs WeVisOne-VL-4B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs WeVisOne-VL-4B
- Kimi K3.1 Pro vs WeVisOne-VL-4B
- Kimi K3 vs WeVisOne-VL-4B
- Kolibri-1 vs WeVisOne-VL-4B
- Kronos vs WeVisOne-VL-4B
- Laguna M.1 vs WeVisOne-VL-4B
- Laguna S 2.1 vs WeVisOne-VL-4B
- Laguna XS 2.1 vs WeVisOne-VL-4B
- LBS-27B vs WeVisOne-VL-4B
- LFM2.5-2.6B vs WeVisOne-VL-4B
- LFM3-1.7B vs WeVisOne-VL-4B
- LFM3-Audio-2B vs WeVisOne-VL-4B
- LFM3-Omni-2B vs WeVisOne-VL-4B
- LFM3-VL-2B vs WeVisOne-VL-4B
- Ling-3.0-tiny vs WeVisOne-VL-4B
- Ling-3.1-flash-1019 vs WeVisOne-VL-4B
- LongCat-2.5 vs WeVisOne-VL-4B
- MiMo-V2.6 Distill Qwen 9B vs WeVisOne-VL-4B
- MiMo-V2.6-Flash-RL vs WeVisOne-VL-4B
- MiniCPM-o 4.5 vs WeVisOne-VL-4B
- MiniCPM-V 4.7 1B vs WeVisOne-VL-4B
- MiniCPM-V 4.7 35B-A3B vs WeVisOne-VL-4B
- MiniCPM5-2B vs WeVisOne-VL-4B
- MiniMax-M2.5 vs WeVisOne-VL-4B
- MiniMax-M2.7 vs WeVisOne-VL-4B
- MiniMax-M3.1-Flash vs WeVisOne-VL-4B
- Mistral Large 4 vs WeVisOne-VL-4B
- Muse Glimmer 30B vs WeVisOne-VL-4B
- Nanbeige4.2-3B vs WeVisOne-VL-4B
- Nanbeige4.3-33B vs WeVisOne-VL-4B
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs WeVisOne-VL-4B
- Nemotron 3.5 Lightning 30B A3B vs WeVisOne-VL-4B
- Nemotron 3 Nano 30B A3B vs WeVisOne-VL-4B
- Nemotron 3 Nano 4B vs WeVisOne-VL-4B
- Nemotron 3 Nano Omni 30B A3B Reasoning vs WeVisOne-VL-4B
- Nemotron 3 Super 120B A12B vs WeVisOne-VL-4B
- Nemotron 3 Ultra 550B A55B vs WeVisOne-VL-4B
- North Mini Code 1.0 vs WeVisOne-VL-4B
- occamy-1.0 vs WeVisOne-VL-4B
- Olmo 3 7B Think vs WeVisOne-VL-4B
- Ornith-1.5-122B vs WeVisOne-VL-4B
- Ornith-1.5-35B-A3B vs WeVisOne-VL-4B
- Ornith-1.5-397B vs WeVisOne-VL-4B
- Ornith-1.5-9B vs WeVisOne-VL-4B
- OTel-2.0-LLM-31B-IT vs WeVisOne-VL-4B
- Qwen-AgentWorld-35B-A3B vs WeVisOne-VL-4B
- Qwen3-30B-A3B-Instruct-2507 vs WeVisOne-VL-4B
- Qwen3-4B-Instruct-2507 vs WeVisOne-VL-4B
- Qwen3.5-0.8B vs WeVisOne-VL-4B
- Qwen3.5-122B-A10B vs WeVisOne-VL-4B
- Qwen3.5-2B vs WeVisOne-VL-4B
- Qwen3.5-397B-A17B vs WeVisOne-VL-4B
- Qwen3.5-4B vs WeVisOne-VL-4B
- Qwen3.5-9B vs WeVisOne-VL-4B
- Qwen3.6-27B vs WeVisOne-VL-4B
- Qwen3.6-35B-A3B vs WeVisOne-VL-4B
- Qwen3.8-27B vs WeVisOne-VL-4B
- Qwen3.8-Flash-Next vs WeVisOne-VL-4B
- Qwen3-Coder-30B-A3B-Instruct vs WeVisOne-VL-4B
- Qwen3-Coder-Next vs WeVisOne-VL-4B
- Qwen3-Omni-30B-A3B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-2B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-30B-A3B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-32B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-4B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-8B-Instruct vs WeVisOne-VL-4B
- Qwopus3.8-27B-Flash-V2 vs WeVisOne-VL-4B
- Recursive Flint vs WeVisOne-VL-4B
- Ripple-65B Preview vs WeVisOne-VL-4B
- SenseNova-Loop-9B-Preview vs WeVisOne-VL-4B
- SmolLM3-3B vs WeVisOne-VL-4B
- Spark-X2.6-4B vs WeVisOne-VL-4B
- Step 3.7 Flash vs WeVisOne-VL-4B
- Swift 1.5 Qwen3.8-27B vs WeVisOne-VL-4B
- Swift 1.5 Qwen3.8-Flash-Next vs WeVisOne-VL-4B
- ThinkingCap (Qwen3.8 27B) vs WeVisOne-VL-4B
- WeVisOne-VL-2B vs WeVisOne-VL-4B
- WeVisOne-VL-4B vs ZAYA1-8B
- Baidu Unlimited-OCR-2 vs WeVisOne-VL-4B
Machine-readable
- This page as Markdown
/compare/hy-memory-30b-a3b-vs-wevisone-vl-4b.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/wevisone-vl-4b.json - From a terminal
anchor compare hy-memory-30b-a3b wevisone-vl-4b(the CLI) - Over MCP
compare_tools {"a": "hy-memory-30b-a3b", "b": "wevisone-vl-4b"}at/mcp, no key