Terminus-2 – GLM-5.3 (max, default) vs. Terminus-2 – Kimi K2.7 Code (always on): geospatial agent comparison
Comparison between Terminus-2 – GLM-5.3 (max, default) and Terminus-2 – Kimi K2.7 Code (always on) on the Geospatial Agent Index, each benchmark, cost, time and token use, from the same tasks, agent and limits. Methodology.
Side by side
| Metric | Terminus-2 – GLM-5.3 (max, default) | Terminus-2 – Kimi K2.7 Code (always on) |
|---|---|---|
| Geospatial Agent Index | 67* (partial: 1.1 of 3 attempts) | 74 |
| GeoAgentBench score | 95 | 91 |
| GeoBenchX score | 52 | 54 |
| Earth-Bench score | 39 | 62 |
| GeoAnalystBench score | 84 | 88 |
| Raster and remote sensing score | 65 | 74 |
| Vector and overlay score | 75 | 78 |
| Networks and routing score | 80 | 87 |
| Climate and time series score | 56 | 78 |
| Spatial statistics and interpolation score | 67 | 60 |
| Mapping and cartography score | 66 | 72 |
| Recognising infeasible requests score | 42 | 41 |
| Cost per task | $0.363 | $0.119 |
| Time per task | 10.1 min | 6.5 min |
| Tokens per attempt | 260k | 290k |
| Turns per attempt | 10.5 | 14.1 |
| Attempts decided | 310 | 870 |
| Input price per 1M tokens | $1.40 | $0.95 |
| Output price per 1M tokens | $4.40 | $4.00 |
| Context window | 1,048,576 | 262,144 |
| Image input | No | Yes |
| Developer | Z.ai | Moonshot AI |
Charts
Geospatial Agent Index
Equal-weight average of the evaluation scores, 0 to 100 · Higher is better
First eight selected entries in metric order. Full results in table view.
Data table: Geospatial Agent Index
| Model | Creator | Geospatial Agent Index | Range while attempts are pending | Benchmarks covered | Coverage (attempts) |
|---|---|---|---|---|---|
| Terminus-2 – Kimi K2.7 Code (always on) | Moonshot AI | 74 | No pending judgements | 4 of 4 | 870 of 870 planned attempts |
| Terminus-2 – GLM-5.3 (max, default) | Z.ai | 67* (partial: 1.1 of 3 attempts) | 66 to 68 | 4 of 4 | 310 of 870 planned attempts |
Cost per task
Average cost per task (USD) · Lower is better
First eight selected entries in metric order. Full results in table view.
Data table: Cost per task
| Model | Creator | Cost per task | Coverage (attempts) |
|---|---|---|---|
| Terminus-2 – GLM-5.3 (max, default) | Z.ai | $0.363 | 320 of 870 planned attempts |
| Terminus-2 – Kimi K2.7 Code (always on) | Moonshot AI | $0.119 | 870 of 870 planned attempts |
Time per task
Average agent wall time per task · Lower is better
First eight selected entries in metric order. Full results in table view.
Data table: Time per task
| Model | Creator | Time per task | Coverage (attempts) |
|---|---|---|---|
| Terminus-2 – GLM-5.3 (max, default) | Z.ai | 10.1 min | 320 of 870 planned attempts |
| Terminus-2 – Kimi K2.7 Code (always on) | Moonshot AI | 6.5 min | 870 of 870 planned attempts |
Frequently asked questions
- Which scores higher on the Geospatial Agent Index, Terminus-2 – GLM-5.3 (max, default) or Terminus-2 – Kimi K2.7 Code (always on)?
- Terminus-2 – Kimi K2.7 Code (always on), at 74 against 67 for Terminus-2 – GLM-5.3 (max, default). Terminus-2 – GLM-5.3 (max, default): 310 of 870 planned attempts. Terminus-2 – Kimi K2.7 Code (always on): 870 of 870 planned attempts. Coverage is partial; scores can change as more attempts are decided.
- Which is cheaper per task, Terminus-2 – GLM-5.3 (max, default) or Terminus-2 – Kimi K2.7 Code (always on)?
- Terminus-2 – Kimi K2.7 Code (always on), at $0.119 against $0.363 for Terminus-2 – GLM-5.3 (max, default).
- Which is faster per task, Terminus-2 – GLM-5.3 (max, default) or Terminus-2 – Kimi K2.7 Code (always on)?
- Terminus-2 – Kimi K2.7 Code (always on), at 6.5 min against 10.1 min for Terminus-2 – GLM-5.3 (max, default).
- Which has the larger context window, Terminus-2 – GLM-5.3 (max, default) or Terminus-2 – Kimi K2.7 Code (always on)?
- Terminus-2 – GLM-5.3 (max, default), at 1,048,576 tokens against 262,144 tokens for Terminus-2 – Kimi K2.7 Code (always on).
More: Terminus-2 – GLM-5.3 (max, default) · Terminus-2 – Kimi K2.7 Code (always on) · all comparisons
