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

Apodex-1.1-mini vs Qwen3.8-27B

Qwen3.8-27B scores 68.6 (B) on agent readiness against Apodex-1.1-mini's 61 (C), and leads in 1 of 4 scored categories. Apodex-1.1-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 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 55
  • Agent interface, 85 against 70

Watch for

No safety results, and agent guidance only from the harness

Qwen3.8-27B B

Best for Agents that want a capable open model with vision on one 24 to 32 GB GPU or Mac, with the widest runtime support and a plain licence.

Ahead on

  • Reach, 90 against 85

Watch for

No safety results, prompt-injection guidance or security contact

Score by category

CategoryWeight this runApodex-1.1-miniQwen3.8-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258590Qwen3.8-27B +5
Risk20%206555Apodex-1.1-mini +10
Agent interface10%108570Apodex-1.1-mini +15
Documentation and upkeep10%103836Apodex-1.1-mini +2
Negative events≤1500
TotalC 61/100B 68.6/100

Facts side by side

FactApodex-1.1-miniQwen3.8-27B
KindOpen-weight modelOpen-weight model
VendorApodex AIAlibaba (Qwen team)
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-08-14
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)3/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.

Qwen3.8-27B

A dense cousin for coding and agent work with image and video input that runs almost anywhere. Ollama's 4-bit build needs about 22 GB, and five providers host it for agents without the hardware. The main risk is that nobody at Alibaba answers, there are no safety results or agent guidance, and the tool format is only in the template.

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

Qwen3.8-27B

  1. Quickest start is ollama run qwen3.8, about 18 GB of files
  2. On our reference machine use BF16 with vllm serve Qwen/Qwen3.8-27B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, since FP8 on gfx1151 isn't documented
  3. Use the qwen3_coder tool parser, SGLang's cookbook says the Hermes parser leaves its calls unparsed
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, and read the reasoning from reasoning_content
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
  7. Preserved thinking keeps earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  8. Turn on YaRN only beyond 262,144 tokens, the card warns static YaRN can cost quality on short texts
  9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Questions

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

Qwen3.8-27B scores 68.6 (B) on agent readiness against Apodex-1.1-mini's 61 (C), and leads in 1 of 4 scored categories. Apodex-1.1-mini leads on risk and agent interface.

Other comparisons with Apodex-1.1-mini or Qwen3.8-27B

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.