GLM 4.7 Flash
Budget GLM lane for fast coding help, routing, and everyday automation
- Context
- 200K
- Released
- 8mo ago
- Parameters
- —
- Input / 1M tokens
- $0.06
- Output / 1M tokens
- $0.40
Sources:models.devOpenRouter
Benchmarks
DeepSWE is the primary coding benchmark where an exact model evaluation exists. Other sourced evaluations appear below; missing scores are not zero.
Not evaluated in DeepSWE 1.1 as of 2026-09-22. Results are only shown for exact model versions in the official dataset. Official leaderboard.
Other published benchmarks
| Evaluation | Reported score and source |
|---|---|
| GPQA diamond | |
| GPQA diamond | |
| OTIS Mock AIME 2024-2025 | |
| OTIS Mock AIME 2024-2025 |
Benchmark compilation: Epoch AI, Capabilities & benchmarking (CC BY attribution). Scores are converted to percentages and model names matched to the Vertical Tabs catalog. Individual evaluations are credited to their original sources. External results may carry separate licences and evaluation configurations; do not interpret scores from different harnesses as directly comparable.
Specifications
- Developer
- Z.ai
- Model family
- GLM
- Type
- Language model
- Predecessor
- —
- Successor
- —
- Released
- January 19, 2026
- Model ID
z-ai/glm-4.7-flash- Openness
- Open weights
- License
- —
- Parameters
- —
- Input modalities
- text
- Output modalities
- text
- Modality
- text->text
- Native context
- 198K
- Tokenizer
- Other
- Max output tokens
- 118K
- Knowledge cutoff
- 2025-04
- Hugging Face
- zai-org/GLM-4.7-Flash
- Source freshness
- Metadata synced Oct 8, 2026, 10:17 PM UTC
Open-weight builds
Ollama variants
Every published Ollama tag matched to this model, including parameter editions, instruction/base variants, and quantized builds.
| Variant | Parameters | Type | Quantization | Size | Context | Input |
|---|---|---|---|---|---|---|
| glm-4.7-flash:bf16 | — | — | BF16 | 60 GB | 198K | text |
| glm-4.7-flash:latest | — | — | Q4_K_M | 19 GB | 198K | text |
| glm-4.7-flash:q8_0 | — | — | Q8_0 | 32 GB | 198K | text |
Additional source evidence
- Source model
- zhipuai/glm-4.7-flash
- Source family
- glm-flash
- Last updated
- 2026-01-19
- Knowledge cutoff
- 2025-04
- Model context
- 200K
- Model output limit
- 131K
- Open weights
- Yes
- File attachments
- No
- Reasoning
- Yes
- Tool calling
- Yes
- Temperature control
- Yes
Downloadable weights
Published benchmarks
| Benchmark | Score | Evaluation details | Evidence |
|---|---|---|---|
| SWE-Bench Verified | 59.2 · resolved | — | Source |
Complete source record (JSON)
{
"id": "zhipuai/glm-4.7-flash",
"name": "GLM-4.7-Flash",
"description": "Budget GLM lane for fast coding help, routing, and everyday automation",
"family": "glm-flash",
"last_updated": "2026-01-19",
"knowledge": "2025-04",
"attachment": false,
"reasoning": true,
"tool_call": true,
"temperature": true,
"modalities": {
"input": [
"text"
],
"output": [
"text"
]
},
"limit": {
"context": 200000,
"output": 131072
},
"benchmarks": [
{
"name": "SWE-Bench Verified",
"score": 59.2,
"source": "https://huggingface.co/zai-org/GLM-4.7-Flash",
"metric": "resolved"
}
],
"release_date": "2026-01-19",
"open_weights": true,
"weights": [
{
"label": "Hugging Face",
"url": "https://huggingface.co/zai-org/GLM-4.7-Flash"
}
]
}Infrastructure
Provider availability
| Provider | Endpoint | Context | Input /M tokens | Output /M tokens | Cached input /M tokens | Cache write /M tokens | Uptime 1d | Data handling |
|---|---|---|---|---|---|---|---|---|
| venice/fp8 | 128K | $0.06 | $0.40 | $0.01 | — | 100.00% | ZDR: YesTraining: Unknown Prompt logging: Unknown Retention: Unknown Checked 2026-10-15 | |
| cloudflare | 131K | $0.06 | $0.40 | — | — | 99.38% | ZDR: NoTraining: Unknown Prompt logging: Unknown Retention: Unknown Checked 2026-10-15 | |
| novita/bf16 | 200K | $0.07 | $0.40 | $0.01 | — | 7.06% | ZDR: YesTraining: Unknown Prompt logging: Unknown Retention: Unknown Checked 2026-10-15 |
Provider data:OpenRouter
Deployment graph
Can I run this?
Vertical Tabs only shows compatibility when it has structured evidence tying this exact model to hardware, runtime, quantization, memory use, and observed performance.