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

Apodex-1.1-mini vs GLM-4.7-Flash

GLM-4.7-Flash scores 63 (B) on agent readiness against Apodex-1.1-mini's 61 (C), and leads in 0 of 4 scored categories. Apodex-1.1-mini leads on reach, risk and 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

  • Reach, 85 against 80
  • Risk, 65 against 55
  • Documentation and upkeep, 38 against 28

Also in its favour

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

Watch for

No safety results, and agent guidance only from the harness

GLM-4.7-Flash B

Best for Agents and developers who want a small, permissively licensed tool-calling model on one 24 to 32 GB GPU or Mac, in almost any runtime

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No change to the files since 29 January 2026 and no zai-org reply on discussions since 31 January

Score by category

CategoryWeight this runApodex-1.1-miniGLM-4.7-FlashEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258580Apodex-1.1-mini +5
Risk20%206555Apodex-1.1-mini +10
Agent interface10%108585even
Documentation and upkeep10%103828Apodex-1.1-mini +10
Negative events≤1500
TotalC 61/100B 63/100

Facts side by side

FactApodex-1.1-miniGLM-4.7-Flash
KindOpen-weight modelOpen-weight model
VendorApodex AIZ.ai (Zhipu AI)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtnono
Last release2026-08-252026-01-29
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.8/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.

GLM-4.7-Flash

A small MIT-licensed mixture-of-experts model with about 3B active parameters, for local agent and coding work with several tool calls per turn and optional thinking. It runs in Ollama at about 23 GB and in nearly every common runtime. The main risk is neglect, with no changes or replies since early February 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

GLM-4.7-Flash

  1. On our reference machine start it with vllm serve zai-org/GLM-4.7-Flash --max-model-len 65536 --tool-call-parser glm47 --reasoning-parser glm45 --enable-auto-tool-choice --served-model-name glm-4.7-flash
  2. Or run ollama run glm-4.7-flash for the 19 GB q4_K_M build
  3. Without the glm47 and glm45 parsers, tool calls and reasoning come back as plain text
  4. Use a released vLLM (0.32.0 or later) or SGLang (0.5.22 or later); the card's nightly and pull-request builds date from January 2026
  5. Pass chat_template_kwargs: {"enable_thinking": false} for short tasks, since thinking is on by default
  6. Set clear_thinking: false to keep earlier reasoning in multi-turn agent work, as Z.ai does for τ²-Bench and Terminal Bench
  7. Set the context length yourself, since config.json allows 202,752 tokens and tokenizer_config.json says 128,000

Questions

Which is better for AI agents, Apodex-1.1-mini or GLM-4.7-Flash?

GLM-4.7-Flash scores 63 (B) on agent readiness against Apodex-1.1-mini's 61 (C), and leads in 0 of 4 scored categories. Apodex-1.1-mini leads on reach, risk and documentation and upkeep.

Other comparisons with Apodex-1.1-mini or GLM-4.7-Flash

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.