Chat model
GPT-6.1 Terra
high reasoning · 16 questions per request
94.3% of the 2,198 questions right (93.2% to 95.2%, 95% interval). Back to the leaderboard.
Which decision model can go first in front of it? See the Routing tab.
How we called it
- Kind
- Chat model
- Access
- Codex CLI, ChatGPT subscription
- Paid as
- Subscription
- Model ID
gpt-6.1-terra- Confidence from
- Written estimate
- Run
- 275, 28 October 2026
Settings
- Reasoning
- high
- Request format
- 16 questions per request
- Requests at once
- 1
- Temperature
- not recorded
- Harness seed
- 0
- Harness commit
0fbd97b0899d- Prompt version
254597b8be16
Reasoning effort levels (OpenAI's model page, read 28 October 2026): none, low, medium (default), high, xhigh, max. Top level: max. This run: high.
Results
| Questions | Accuracy | 95% interval | Right |
|---|---|---|---|
| All questions | 94.3% | 93.2% to 95.2% | 2,072 of 2,198 |
| Reading | 96.2% | 94.4% to 97.4% | 631 of 656 |
| Grammar | 93.5% | 92.1% to 94.6% | 1,441 of 1,542 |
Comparison group: fg. Compare with another setup.
Accuracy by topic
Confidence
- Answers kept at 99% or more
- 1,363, of which 19 wrong (share right: 97.8% to 99.1%, 95% interval); 835 skipped, the model less than 99% sure
- Calibration gap
- 2.8 points
- AUROC, all questions
- 0.81 0.77 to 0.85
- AUROC, reading
- 0.93 0.87 to 0.97
- AUROC, grammar
- 0.78 0.73 to 0.82
- Brier score
- 0.049
- Accuracy of its surest answers
- most confident fifth: 98.8% right; most confident half: 98.6% right; most confident four fifths: 97.5% right
- Typical score of a right answer
- 99.0%
- Typical score of a wrong answer
- 94.0%
Repeats
Run 5 times on a sample of 200 questions.
- Answers changed in 5 runs
- 11 of 200
- Same wrong answer in all 5
- 5 of 200
- Wrong in at least one run
- 16 of 200
- Accuracy in each run
- 96.5%, 97.0%, 95.0%, 96.5%, 95.5%
Latency
- Latency, median request
- 7.10 s (this run)
- Latency, 90th percentile
- 12.6 s
- Requests at once
- 1
- Throughput
- 113.3 questions per minute of request time
- Request time
- 19.4 minutes, over the requests whose answers were kept
Latency: the time from sending one request to receiving its answer, measured from our computer, network and any retries within the request included. Request time: the time at least one request was in flight, over the requests whose answers were kept. It is not the run's elapsed time: it leaves out requests that failed and any pause before a run was resumed.
Cost
- $ per 1,000 questions
- $0.51
- Whole run
- $1.13
- Basis
- Subscription run priced as if we had used the API
- Price
- $1 input, $0.05 cached input, $1.25 cache writes, $5 output per 1M tokens (source, 2026-10-28)
- Input tokens per question
- 529
- Output tokens per question
- 30