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

EXAONE 4.5 33B vs OTel-2.0-LLM-31B-IT

EXAONE 4.5 33B scores 61 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on 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 6359 open weights comparisons

Which one, for what

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

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

Watch for

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

OTel-2.0-LLM-31B-IT C

Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware

Ahead on

  • Risk, 55 against 50
  • Documentation and upkeep, 74 against 50

Watch for

BF16 only at 62.6 GB, with no GGUF or other quantised build from anyone we checked

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.

Agent interface EXAONE 4.5 33B +25

EXAONE 4.5 33B 85

Chat template 20, chat_template.jinja in the repository (5,930 characters). Tool-calling format 25, the card's vLLM command names the parser, hermes with auto tool choice, and its agentic example calls tools from MCP servers through the OpenAI-compatible API, so declaration and return follow that API. Trained tool calling 20, the card reports agentic tool use among its language results and shows an agent run with several tool servers, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, enable_thinking is on by default and the card says to set it false for the non-reasoning mode, with an example of each. Context 10, 262,144 tokens per the card's configuration table and config.json, and the card's serve commands run at that length. 20 + 25 + 20 + 0 + 10 + 10 = 85.

OTel-2.0-LLM-31B-IT 60

Chat template 20, chat_template.jinja in the repository, 19,300 characters, the publisher's own. Tool-calling format 10, only the template says how tools are declared and how calls come back. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one turn, and the card says the training mix included general-purpose agentic tool-calling examples, while none were specific to telecoms. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card says the model wasn't trained to produce or consume Gemma's thought channel and answers directly, so there is no thinking to switch or budget. Context 10, 262,144 positions in the text config, the base's native context. 20 + 10 + 20 + 0 + 0 + 10 = 60.

Documentation and upkeep OTel-2.0-LLM-31B-IT +24

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.

OTel-2.0-LLM-31B-IT 74

Model card 14, Intended use, a long limitations section, the architecture and training method, the parameters (31B) and the language (English) are on the card. Training data 15, the card names the sources (3GPP, ETSI, ITU, GSMA, CAMARA, O-RAN and TM Forum material provided by GSMA), the overall sizes (15 billion raw tokens, over 1 trillion processed, about 440 billion used), the mix of example types and the processing tool, and lists what was left out. Last change 20, the last commit, on 1 November 2026, updated the card's links, resources, citation and contacts, nine days before this check. Responsiveness 20, Of the 3 discussions that aren't pull requests (7 August to 28 October 2026), 2 have a reply from the repository's owner, which is most. Version policy 0, the weights were replaced in place: uploads on 27 July, 3 August and 1 September 2026 under one name, with a standing notice on the card that they may change and that users should pin a revision, and no dated note of what changed. File health 5, the card describes 15 shards of about 62.6 GB while the repository still holds an earlier 14-shard set beside them, 126.8 GB in all. 14 + 15 + 20 + 20 + 0 + 5 = 74.

Reach EXAONE 4.5 33B +15

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.

OTel-2.0-LLM-31B-IT 50

Memory 10, the publisher's only build is the BF16 safetensors, 62.55 GB for the 15 shards the index names, and 62.55 GB × 1.2 = 75.1 GB, above 64 GB and inside the reference machine's GPU share. Runtimes 15, the architecture is Gemma4ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors files, three at 5 each. Builds 0, the publisher ships the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with nothing added on the card. Download 10, gated is false on 10 November 2026, so the files download with no account or terms. Hosted 0, Hugging Face maps one inference provider, Featherless AI (live), short of the two the line needs. 10 + 15 + 0 + 15 + 10 + 0 = 50.

Risk OTel-2.0-LLM-31B-IT +5

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.

OTel-2.0-LLM-31B-IT 55

File safety 25, safetensors only, with no .bin, .pt or .pth files and no Python files. Provenance 5, the files sit in a personal account, farbodtavakkoli, not in an organisation AT&T's or GSMA's site links to: GSMA's article names AT&T as the releaser without linking the repository, and the GitHub repository that links it is the same person's (0). Safety evaluation 0, no safety results on the card. Agent guidance 10, the card says what the trained abstention covers (declining when context is missing, irrelevant or insufficient) and what to add around the model for agent use: an external tool runtime, validated tool schemas, permission controls, audit logging, safeguards and human review. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the licence link resolves (200 on 10 November 2026). Security programme 0, no way to report a flaw found. 25 + 5 + 0 + 10 + 15 + 0 = 55.

Score by category

CategoryWeight this runEXAONE 4.5 33BOTel-2.0-LLM-31B-ITEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256550EXAONE 4.5 33B +15
Risk20%205055OTel-2.0-LLM-31B-IT +5
Agent interface10%108560EXAONE 4.5 33B +25
Documentation and upkeep10%105074OTel-2.0-LLM-31B-IT +24
Negative events≤1500
TotalC 61/100C 56.8/100

Facts side by side

FactEXAONE 4.5 33BOTel-2.0-LLM-31B-IT
KindOpen-weight modelOpen-weight model
VendorLG AI ResearchAT&T (Open Telco AI)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceEXAONE AI Model License Agreement 1.2 - NC (research and education only)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-062026-11-01
Terms last updatednot read yetno document linked
Privacy policy last updatedno document linkedno document linked

Verdicts

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.

OTel-2.0-LLM-31B-IT

A real telecoms post-training of Gemma 4 31B IT with an unusually candid card on what was and wasn't trained. It fits a 128 GB machine in BF16 only, with no quantised build, sits in a personal account, and its weights have been replaced in place. Tool-call format, structured output and safety results aren't documented.

Before you call either

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

OTel-2.0-LLM-31B-IT

  1. Download the 15 shards the index names, not the whole repository, which is twice the size
  2. Pin a revision. The card says the weights may change under the same name
  3. Serve it with vLLM 0.19.0 or later and the repository's own chat template, not Gemma 4's
  4. Send no thinking flags. It answers directly and wasn't trained on Gemma's thought channel
  5. Use it as the generation stage of a RAG pipeline over telecom standards, with source attribution and human review
  6. Don't use it to run network tools unattended. The card says that hasn't been evaluated

Questions

Which is better for AI agents, EXAONE 4.5 33B or OTel-2.0-LLM-31B-IT?

EXAONE 4.5 33B scores 61 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on risk and documentation and upkeep.

Other comparisons with EXAONE 4.5 33B or OTel-2.0-LLM-31B-IT

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.