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

Apodex-1.1-mini vs WeVisOne-VL-4B

Apodex-1.1-mini and WeVisOne-VL-4B score within a point of each other on agent readiness, 61 (C) and 61 (C). WeVisOne-VL-4B leads on documentation and upkeep. 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

Apodex-1.1-mini C

Best for Long-running agent tasks with tools on a 32 GB GPU or Mac, or through Apodex's API, under a plain licence

Ahead on

  • Reach, 85 against 70
  • Risk, 65 against 55
  • Agent interface, 85 against 70

Watch for

No safety results, and agent guidance only from the harness

WeVisOne-VL-4B C

Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence

Ahead on

  • Documentation and upkeep, 48 against 38

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.

Reach Apodex-1.1-mini +15

Apodex-1.1-mini 85

Memory 20, Apodex's Q4_K_M GGUF with its vision projector is 22.6 GB and needs about 27.1 GB with the fifth added, so 32 GB, as do its NVFP4 and GPTQ-Int4 builds. Runtimes 20, the Qwen3.5 MoE architecture runs in released vLLM, SGLang, Transformers and llama.cpp, while Ollama's and LM Studio's entries are the base's, not this model's. Builds 15, Apodex publishes FP8, NVFP4, GPTQ-Int4 and GGUF. Terms 15, Apache 2.0 with nothing added. Download 10, nothing is gated. Hosted 5, Apodex's own API serves it.

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.

Agent interface Apodex-1.1-mini +15

Apodex-1.1-mini 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card says how tools go in and come back and names the parser for SGLang and vLLM, with a full example. Trained tool calling 20, trained for native function calling with parallel calls. Structured output 0. Reasoning control 10, the template turns thinking off per request and the card says the reasoning comes back in reasoning_content. Context 10, 262,144 tokens.

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.

Risk Apodex-1.1-mini +10

Apodex-1.1-mini 65

File safety 25, safetensors and GGUF only and nothing from the repositories runs. Provenance 15, the files are in the apodex organisation its site links to, with a SHA-256 for every weight file and a SHA256SUMS file for the GGUF. Safety evaluation 0, none published. Agent guidance 5, the recommended harness documents approval gates and a sandbox boundary, but nothing on prompt injection or refusals for the model. Licence risk 15, Apache 2.0 from Qwen3.5-35B-A3B through to this model with no conditions added. Security programme 5, the harness has a disclosure policy with a private address, with no route shown for the weights.

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.

Documentation and upkeep WeVisOne-VL-4B +10

Apodex-1.1-mini 38

Model card 8, it covers intended use, context and languages but not the architecture, parameters, limitations or a knowledge cut-off. Training data 5, a general description with no cut-off. Last change 15, the GGUF build went up on 10 September 2026, 54 days before 3 November. Responsiveness 0, Apodex answered none of the four discussions, unchanged on 3 November 2026. Version policy 5, 1.0-mini stays in its own repository without a note. File health 5, the files agree, but the card's agent example is broken and reports wait without a reply.

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.

Score by category

CategoryWeight this runApodex-1.1-miniWeVisOne-VL-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258570Apodex-1.1-mini +15
Risk20%206555Apodex-1.1-mini +10
Agent interface10%108570Apodex-1.1-mini +15
Documentation and upkeep10%103848WeVisOne-VL-4B +10
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApodex-1.1-miniWeVisOne-VL-4B
KindOpen-weight modelOpen-weight model
VendorApodex AITencent (WeChat Vision)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-252026-10-27
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews3.3/5 (4)none

Verdicts

Apodex-1.1-mini

An agent cousin fine-tuned from Qwen3.5-35B-A3B for long tasks with files, code and tools, with parallel tool calling and about 3B active parameters. It needs 32 GB for Apodex's GGUF, NVFP4 or GPTQ-Int4 builds or about 86 GB in BF16, and Apodex's API serves it too. The main risks are no safety results and no replies from the publisher.

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

Apodex-1.1-mini

  1. Serve it with vllm serve apodex/Apodex-1.1-mini --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser qwen3, or the same parsers in SGLang, so tool calls and reasoning come back parsed
  2. For llama.cpp, llama-server -hf apodex/Apodex-1.1-mini-GGUF:Q4_K_M --jinja --reasoning-format deepseek, and the card passes the repository's chat_template.jinja with --chat-template-file
  3. Pass tools through the API's tools parameter rather than in the system prompt, as the card asks
  4. The card recommends temperature 1.0, top_p 0.95, repetition_penalty 1.05 and max_tokens up to 32,768
  5. Send your own system prompt, or set identity_mode, since the template otherwise adds an Apodex identity block
  6. The template keeps all earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  7. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  8. The card's Python example has a broken line where it runs the tool (available_toolsname), so fix it to available_tools[name](**args) before running
  9. Validate JSON output yourself, since structured output isn't documented

WeVisOne-VL-4B

  1. Use Tencent's package: WeVisOneVL("tencent/WeVisOne-VL-4B", backend="vllm") then model.predict(image, task=..., query=...)
  2. Tasks are detection, referring, point, count_box, count_point, ocr, ocr_grounding, segmentation and matting
  3. A None answer means the target isn't in the image. Treat it as a result, not an error
  4. mask_decoder.pt is a pickle. Load it only from the tencent repository, and check its SHA-256 against the Hub's
  5. Send one image a turn. Video grids are rejected by the decoder
  6. The card says it isn't for identifying individuals or for high-impact decisions on its own

Questions

Which is better for AI agents, Apodex-1.1-mini or WeVisOne-VL-4B?

Apodex-1.1-mini and WeVisOne-VL-4B score within a point of each other on agent readiness, 61 (C) and 61 (C). WeVisOne-VL-4B leads on documentation and upkeep.

Other comparisons with Apodex-1.1-mini or WeVisOne-VL-4B

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.