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

Apodex-1.1-mini vs Qwopus3.8-27B-Flash-V2

Apodex-1.1-mini and Qwopus3.8-27B-Flash-V2 score within a point of each other on agent readiness, 61 (C) and 61 (C). Qwopus3.8-27B-Flash-V2 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 2870 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

  • Risk, 65 against 50
  • Agent interface, 85 against 60

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.5 out of 5

Watch for

No safety results, and agent guidance only from the harness

Qwopus3.8-27B-Flash-V2 C

Best for Hobbyist and research agents that want a faster-finishing Qwen3.8-27B for local coding loops on a 24 GB GPU.

Ahead on

  • Documentation and upkeep, 56 against 38

Watch for

Published from a personal account, with no organisation, security contact or safety evaluation

Score by category

CategoryWeight this runApodex-1.1-miniQwopus3.8-27B-Flash-V2Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258585even
Risk20%206550Apodex-1.1-mini +15
Agent interface10%108560Apodex-1.1-mini +25
Documentation and upkeep10%103856Qwopus3.8-27B-Flash-V2 +18
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApodex-1.1-miniQwopus3.8-27B-Flash-V2
KindOpen-weight modelOpen-weight model
VendorApodex AIJackrong
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0 (metadata only, no LICENSE file); built on Qwen3.8-27B under Apache 2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-252026-09-21
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.3/5 (4)2.5/5 (4)

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.

Qwopus3.8-27B-Flash-V2

A Qwen3.8-27B cousin tuned to think less per turn in long agent loops, with an MTP head for speculative decoding in llama.cpp. It fits 24 GB with Jackrong's 4-bit GGUF. The risks are one person's experimental release with no safety work, training traces taken from Claude and GPT, and a tool format that differs from Qwen's.

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

Qwopus3.8-27B-Flash-V2

  1. Quickest start is llama-server -hf Jackrong/Qwopus3.8-27B-Flash-V2-GGUF:Q4_K_M --jinja, about 17 GB, and add mmproj-F32.gguf for images
  2. The card's tests used Q5_K_M with the bundled MTP head and --spec-type draft-mtp in llama.cpp
  3. The template asks for tool calls as JSON inside tool_call tags, so use a Hermes-style parser (vLLM's hermes), not Qwen3.8's qwen3_coder
  4. For coding the card recommends enable_thinking true, reasoning_effort xhigh and temperature 0.3, which you must pass yourself, since generation_config.json says 1.0
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Earlier reasoning stays in the context unless preserve_thinking is false
  7. Cap max_tokens, since a report says it loops more than V1

Questions

Which is better for AI agents, Apodex-1.1-mini or Qwopus3.8-27B-Flash-V2?

Apodex-1.1-mini and Qwopus3.8-27B-Flash-V2 score within a point of each other on agent readiness, 61 (C) and 61 (C). Qwopus3.8-27B-Flash-V2 leads on documentation and upkeep.

Other comparisons with Apodex-1.1-mini or Qwopus3.8-27B-Flash-V2

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.