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

Apodex-1.1-mini vs EXAONE 4.5 33B

Apodex-1.1-mini and EXAONE 4.5 33B score within a point of each other on agent readiness, 61 (C) and 61 (C). EXAONE 4.5 33B 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 65
  • Risk, 65 against 50

Watch for

No safety results, and agent guidance only from the harness

EXAONE 4.5 33B C

Best for Researchers and students working on documents, Korean or multimodal agents who don't need commercial rights

Ahead on

  • Documentation and upkeep, 50 against 38

Watch for

Research and education only. No commercial use of the model or its output

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 +20

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.

EXAONE 4.5 33B 65

Memory 20, the smallest build at 4 bits is LG's IQ4_XS GGUF, 18.03 GB with the 2.57 GB projector, and 20.60 GB × 1.2 = 24.7 GB, within 32 GB. Without the projector, for text only, it would fit 24 GB. Runtimes 15, Released vLLM 0.33.0 has exaone4_5.py, Transformers 5.22.2 has the exaone4_5 model, and llama.cpp b12242 has the architecture, with LG's own GGUF. Three at 5 each. Builds 15, LG publishes GGUF at five quantised precisions, an AWQ build and an FP8 build. Terms 5, Research and educational use only. Download 10, the Hub API reports gated false for all four repositories on 10 November 2026, so the files download with no account and no click-through, though the licence says downloading is acceptance. Hosted 0, Hugging Face maps no inference provider to it, and the card names no API that serves it. 20 + 15 + 15 + 5 + 10 + 0 = 65.

Risk Apodex-1.1-mini +15

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.

EXAONE 4.5 33B 50

File safety 25, safetensors and GGUF only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the LGAI-EXAONE organisation (LG AI Research on the Hub), which the card's GitHub repository shares a name with and the licence in the repository is LG's (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions: the limitation section lists inappropriate, biased, incorrect and outdated answers and tells users not to try to induce harmful output. Licence risk 5, 15 less 5 for field-of-use limits beyond the law (no commercial use, no building competing models) and 5 for terms the licensor can change or revoke (LG may amend the agreement at any time, and the licence is revocable). Security programme 0, no way to report a flaw on the card beyond a support contact, and www.lgresearch.ai has no security.txt. 25 + 15 + 0 + 5 + 5 + 0 = 50.

Documentation and upkeep EXAONE 4.5 33B +12

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.

EXAONE 4.5 33B 50

Model card 20, Uses (the quickstart's question answering, document and agent examples), limitations, the architecture, the parameters, the context, the languages (in the metadata) and a knowledge cut-off of December 2024 are all on the card. Training data 5, A knowledge cut-off and one line on excluding personal, harmful and biased content, with no sources or sizes. Last change 10, the main repository last changed on 6 July 2026 (dependencies moved to official releases), 127 days before this check, and the FP8 repository on 9 August, 93 days. Responsiveness 0, none of the 5 most recent discussions that aren't pull requests (13 April to 4 May 2026) has a reply from an LGAI-EXAONE member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, EXAONE 4.0 and 4.0.1 stay in their own repositories and 4.5 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the 262,144 tokens, and a July commit moved the dependencies to released versions. 20 + 5 + 10 + 0 + 5 + 10 = 50.

Score by category

CategoryWeight this runApodex-1.1-miniEXAONE 4.5 33BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258565Apodex-1.1-mini +20
Risk20%206550Apodex-1.1-mini +15
Agent interface10%108585even
Documentation and upkeep10%103850EXAONE 4.5 33B +12
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApodex-1.1-miniEXAONE 4.5 33B
KindOpen-weight modelOpen-weight model
VendorApodex AILG AI Research
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0EXAONE AI Model License Agreement 1.2 - NC (research and education only)
Read-only variant documentednono
llms.txtnono
Last release2026-08-252026-07-06
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.

EXAONE 4.5 33B

A well-documented vision-language model with a full set of builds, tool calling, switchable reasoning, a 256K context and a stated knowledge cut-off. The licence decides whether you can use it: research and education only, output included, and LG can change the terms. Nothing answered on the repository 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

EXAONE 4.5 33B

  1. Don't use it, or anything it writes, commercially. The licence covers the output too
  2. Serve it with vLLM and --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser hermes
  3. Set enable_thinking false for a direct answer. Thinking is on by default
  4. Use temperature 1.0, top_p 0.95 and presence_penalty 1.5 in general, and temperature 0.6 with top_k 20 for documents and Korean
  5. For llama.cpp, load a projector file from LG's GGUF repository with the weights for image input
  6. Its knowledge stops at December 2024

Questions

Which is better for AI agents, Apodex-1.1-mini or EXAONE 4.5 33B?

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

Other comparisons with Apodex-1.1-mini or EXAONE 4.5 33B

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.