GLM-5-Turbo
zai/glm-5-turboPor Z.AI / Zhipu · familia: glm · lanzado 2026-03-16 · fecha de conocimiento: 2025-01-01
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
Capacidades
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding86
- Tool calling40/40
- Structured output20/20
- Reasoning10/10
- Context window (100K → 1M)6/20
- Provider availability10/10
Agents100
- Tool calling35/35
- Structured output25/25
- Reasoning15/15
- Output token limit15/15
- Provider availability10/10
JSON / structured output90
- Structured output / JSON mode50/50
- Tool calling20/20
- Temperature control10/10
- Price-friendly for high-volume10/20
Cost efficiency50
- Headline price (log-scaled)45/95
- Has prompt-cache pricing5/5
Long context55
- Context window (100K → 2M)45/90
- Has published price for full window10/10
Production-readiness98
- Number of independent providers40/40
- Has published per-token price20/20
- Context window ≥ 8K15/15
- No data inconsistencies across providers8/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $8.00 < $0.01 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $16.00 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $4.40 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $13.60 $0.01 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $16.80 $0.02 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
Detalle de precios
Precio recomendado de zai · glm-5-turbo
Proveedor más barato: zai-coding-plan · Unknown entrada + Unknown salida
Disponible en 10 proveedores
| Proveedor | ID de modelo del proveedor | Entrada / 1M | Salida / 1M | Contexto | Lanzado |
|---|---|---|---|---|---|
| Z.AI zai | glm-5-turbo | $1.20 | $4.00 | 200K | 2026-03-16 |
| Z.AI Coding Plan zai-coding-plan | glm-5-turbo | Unknown | Unknown | 200K | 2026-03-16 |
| Zhipu AI Coding Plan zhipuai-coding-plan | glm-5-turbo | Unknown | Unknown | 200K | 2026-03-16 |
| OpenRouter openrouter | z-ai/glm-5-turbo | $0.960 | $3.20 | 203K | 2026-03-16 |
| Vercel AI Gateway vercel | zai/glm-5-turbo | $1.20 | $4.00 | 203K | 2026-03-15 |
| 302.AI 302ai | glm-5-turbo | $0.720 | $3.20 | 200K | 2026-03-16 |
| ZenMux zenmux | z-ai/glm-5-turbo | $0.880 | $3.48 | 200K | 2026-03-20 |
| Chutes chutes | zai-org/GLM-5-Turbo | $0.489 | $1.96 | 203K | 2026-03-11 |
| Kilo Gateway kilo | z-ai/glm-5-turbo | $1.20 | $4.00 | 203K | 2026-03-15 |
| Venice AI venice | z-ai-glm-5-turbo | $1.20 | $4.00 | 200K | 2026-03-15 |
Inconsistencias de datos entre proveedores
- context_window varies: 200000, 202752, 202800
Los proveedores reportan valores distintos para este modelo. Los datos clave de arriba usan un proveedor representativo; consulta la tabla para detalles por proveedor.
Frequently asked questions
How much does GLM-5-Turbo cost?
GLM-5-Turbo costs $1.20 per 1M input tokens and $4.00 per 1M output tokens, sourced from zai. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of GLM-5-Turbo?
GLM-5-Turbo has a context window of 200K tokens, with a max output of 131K tokens per reply. This is the total combined size of prompt + completion.
Does GLM-5-Turbo support tool calling?
Yes. GLM-5-Turbo supports tool calling (function calling). This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.
Does GLM-5-Turbo support structured output / JSON mode?
Yes. GLM-5-Turbo supports structured output / JSON-schema-constrained decoding. This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.
Can GLM-5-Turbo accept image input?
No. GLM-5-Turbo only accepts text as input. If you need image input, see our /capabilities/vision list for current vision-capable models.
Is GLM-5-Turbo open-weight?
No. GLM-5-Turbo is a proprietary model — only Z.AI / Zhipu (and any approved hosting partners) can serve it. The pricing above reflects the cheapest API access.
What are the best alternatives to GLM-5-Turbo?
If GLM-5-Turbo doesn't fit, consider GLM-5, GLM-4.7, GLM-5.1. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers come from the public models.dev API and are normalised into a single canonical model record. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More Z.AI / Zhipu models
- GLM-5$1.00 in / $3.20 out
- GLM-4.7$0.60 in / $2.20 out
- GLM-5.1$1.40 in / $4.40 out
- GLM-4.6$0.60 in / $2.20 out
- GLM-4.7-Flash$0.06 in / $0.40 out
Capability lists this model is in
Última actualización:
Data is sourced from models.dev and normalized for comparison. Prices and capabilities may change. Always verify critical production decisions with the provider's official documentation.