Terminus-2 – Kimi K2.7 Code (always on) vs. Codex – GPT-6.1 Sol (high): geospatial agent comparison
Comparison between Terminus-2 – Kimi K2.7 Code (always on) and Codex – GPT-6.1 Sol (high) 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 – Kimi K2.7 Code (always on) | Codex – GPT-6.1 Sol (high) |
|---|---|---|
| Geospatial Agent Index | 74 | 80* (partial: 2.8 of 3 attempts) |
| GeoAgentBench score | 91 | 100 |
| GeoBenchX score | 54 | 66 |
| Earth-Bench score | 62 | 53 |
| GeoAnalystBench score | 88 | 100 |
| Raster and remote sensing score | 74 | 72 |
| Vector and overlay score | 78 | 78 |
| Networks and routing score | 87 | 100 |
| Climate and time series score | 78 | 76 |
| Spatial statistics and interpolation score | 60 | 61 |
| Mapping and cartography score | 72 | 76 |
| Recognising infeasible requests score | 41 | 68 |
| Cost per task | $0.119 | $0.080 |
| Time per task | 6.5 min | 1.8 min |
| Tokens per attempt | 290k | 143k |
| Turns per attempt | 14.1 | 7.8 |
| Attempts decided | 870 | 753 |
| Input price per 1M tokens | $0.95 | $2.00 |
| Output price per 1M tokens | $4.00 | $10.00 |
| Context window | 262,144 | No data |
| Image input | Yes | No data |
| Developer | Moonshot AI | OpenAI |
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) |
|---|---|---|---|---|---|
| Codex – GPT-6.1 Sol (high) | OpenAI | 80* (partial: 2.8 of 3 attempts) | 72 to 80 | 4 of 4 | 753 of 870 planned attempts |
| Terminus-2 – Kimi K2.7 Code (always on) | Moonshot AI | 74 | No pending judgements | 4 of 4 | 870 of 870 planned attempts |
Codex – GPT-6.1 Sol (high)
Terminus-2 – Kimi K2.7 Code (always on)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 – Kimi K2.7 Code (always on) | Moonshot AI | $0.119 | 870 of 870 planned attempts |
| Codex – GPT-6.1 Sol (high) | OpenAI | $0.080 | 813 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 – Kimi K2.7 Code (always on) | Moonshot AI | 6.5 min | 870 of 870 planned attempts |
| Codex – GPT-6.1 Sol (high) | OpenAI | 1.8 min | 813 of 870 planned attempts |
Frequently asked questions
- Which scores higher on the Geospatial Agent Index, Terminus-2 – Kimi K2.7 Code (always on) or Codex – GPT-6.1 Sol (high)?
- Codex – GPT-6.1 Sol (high), at 80 against 74 for Terminus-2 – Kimi K2.7 Code (always on). Terminus-2 – Kimi K2.7 Code (always on): 870 of 870 planned attempts. Codex – GPT-6.1 Sol (high): 753 of 870 planned attempts. Coverage is partial; scores can change as more attempts are decided.
- Which is cheaper per task, Terminus-2 – Kimi K2.7 Code (always on) or Codex – GPT-6.1 Sol (high)?
- Codex – GPT-6.1 Sol (high), at $0.080 against $0.119 for Terminus-2 – Kimi K2.7 Code (always on).
- Which is faster per task, Terminus-2 – Kimi K2.7 Code (always on) or Codex – GPT-6.1 Sol (high)?
- Codex – GPT-6.1 Sol (high), at 1.8 min against 6.5 min for Terminus-2 – Kimi K2.7 Code (always on).
- Which has the larger context window, Terminus-2 – Kimi K2.7 Code (always on) or Codex – GPT-6.1 Sol (high)?
- Not known yet: Codex – GPT-6.1 Sol (high) has no context window data.
More: Terminus-2 – Kimi K2.7 Code (always on) · Codex – GPT-6.1 Sol (high) · all comparisons