LLM Reference

GLM-5.2 vs Qwen3-105B

GLM-5.2 (2026) and Qwen3-105B (2025) are frontier reasoning models from Zhipu AI and Alibaba. GLM-5.2 ships a 1m-token context window, while Qwen3-105B ships a 128k-token context window. This comparison covers specs, pricing, API access, capabilities, benchmarks, input and output token costs, and production fit for coding and agent workloads. It focuses on practical selection signals rather than broad model-family marketing.

GLM-5.2 fits 8x more tokens; pick it for long-context work and Qwen3-105B for tighter calls.

Decision scorecard

Local evidence first
SignalGLM-5.2Qwen3-105B
Best forreasoning-heavy apps, tool-calling agents, and long-context analysistool-calling agents
Decision fitCoding, RAG, and AgentsRAG, Agents, and Long context
Context window1m128k
Cheapest output$4.40/1M tokens-
Provider routes1 tracked0 tracked
Shared benchmarks0 shared0 shared

Decision tradeoffs

Choose GLM-5.2 when...
  • GLM-5.2 has the larger context window for long prompts, retrieval packs, or transcript analysis.
  • GLM-5.2 has broader tracked provider coverage for fallback and procurement flexibility.
  • GLM-5.2 uniquely exposes Reasoning, Structured outputs, and Code execution in local model data.
  • Local decision data tags GLM-5.2 for Coding, RAG, and Agents.
Choose Qwen3-105B when...
  • Local decision data tags Qwen3-105B for RAG, Agents, and Long context.

Monthly cost at traffic

Estimate token spend from the cheapest tracked input and output route or tier on this page.

GLM-5.2

$2,220

Cheapest tracked route/tier: OpenRouter

Qwen3-105B

Unavailable

No complete token price in local provider data

Cost delta unavailable until both models have sourced input and output token prices.

Switch friction

GLM-5.2 -> Qwen3-105B
  • No overlapping tracked provider route is sourced for GLM-5.2 and Qwen3-105B; plan for SDK, billing, or endpoint changes.
  • Check replacement coverage for Reasoning, Structured outputs, and Code execution before moving production traffic.
Qwen3-105B -> GLM-5.2
  • No overlapping tracked provider route is sourced for Qwen3-105B and GLM-5.2; plan for SDK, billing, or endpoint changes.
  • GLM-5.2 adds Reasoning, Structured outputs, and Code execution in local capability data.

Specs

Specification
Released2026-06-132025-12-15
Context window1m128k
Parameters753B total, 40B active105B
ArchitectureMixture of Experts-
LicenseMITOSI-approvedApache 2.0OSI-approved
OpennessOpen sourceOpen source
Commercial useCommercial use: permittedCommercial use: permitted
Knowledge cutoff-2025-02

Pricing and availability

Pricing attributeGLM-5.2Qwen3-105B
Input price$1.40/1M tokens-
Output price$4.40/1M tokens-
Providers-

Capabilities

CapabilityGLM-5.2Qwen3-105B
VisionNoNo
MultimodalNoNo
ReasoningYesNo
Function callingYesYes
Tool useYesYes
Structured outputsYesNo
Code executionYesNo
IDE integrationNoNo
Computer useNoNo
Parallel agentsNoNo

Benchmarks

No shared benchmark scores are currently available for this pair.

Deep dive

The capability footprint differs most on reasoning mode: GLM-5.2, structured outputs: GLM-5.2, and code execution: GLM-5.2. Both models share function calling and tool use, so the practical split is not just feature count. Use those differences to decide whether the page is about raw model quality, agentic coding support, multimodal ingestion, or predictable structured API behavior.

Pricing coverage is uneven: GLM-5.2 has $1.40/1M input tokens and Qwen3-105B has no token price sourced yet. Provider availability is 1 tracked routes versus 0. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.

Choose GLM-5.2 when coding workflow support, larger context windows, and broader provider choice are central to the workload. Choose Qwen3-105B when provider fit are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.

FAQ

Which has a larger context window, GLM-5.2 or Qwen3-105B?

GLM-5.2 supports 1m tokens, while Qwen3-105B supports 128k tokens. That gap matters most for long documents, large codebases, retrieval-heavy agents, and conversations where earlier context must remain visible. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.

Is GLM-5.2 or Qwen3-105B open source?

GLM-5.2 is listed under MIT. Qwen3-105B is listed under Apache 2.0. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.

Which is better for reasoning mode, GLM-5.2 or Qwen3-105B?

GLM-5.2 has the clearer documented reasoning mode signal in this comparison. If reasoning mode is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for function calling, GLM-5.2 or Qwen3-105B?

Both GLM-5.2 and Qwen3-105B expose function calling. The better choice depends on benchmark fit, context budget, pricing, and whether your provider route exposes the same capability surface. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.

Which is better for tool use, GLM-5.2 or Qwen3-105B?

Both GLM-5.2 and Qwen3-105B expose tool use. The better choice depends on benchmark fit, context budget, pricing, and whether your provider route exposes the same capability surface. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.

Where can I run GLM-5.2 and Qwen3-105B?

GLM-5.2 is available on OpenRouter. Qwen3-105B is available on the tracked providers still being sourced. Provider coverage can affect latency, region availability, compliance posture, and fallback options. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.

Continue comparing

Last reviewed: 2026-06-24. Data sourced from public model cards and provider documentation.