LLM Comparison

Gemini 3.1 Pro vs Composer 2.5: benchmark scores, pricing & comparison.

Side-by-side Gemini 3.1 Pro vs Composer 2.5 comparison across SWE-bench, GPQA, HLE, Terminal-Bench, coding agent scores, token pricing, context window, and AskClash RWT. Green marks the winner on each benchmark.

Rank #23 vs #32AskClash overall scores 52.0 vs 44.4.
Pricing $2.00/$12.0 vs $0.50/$2.50Input and output token prices per 1M tokens when published.
Proprietary vs ProprietaryGoogle vs Cursor.

Gemini 3.1 Pro vs Composer 2.5 benchmark comparison

Green cells highlight the winning model for each metric. Scores are cached from the AskClash LLM leaderboard snapshot.

MetricGemini 3.1 ProComposer 2.5
Overall Score52.044.4
Leaderboard Rank#23#32
RWT8.5
Coding Agent Index30.362.9
HLE51.4
GPQA94.3
SWE-bench80.6
SWE-Pro54.249.2
SWE-Atlas72.5
Terminal-Bench68.569.3
DeepSWE11.8
MCP Atlas69.2
Finance Agent43.0
CharXiv80.2
MMMU-Pro83.9
ARC-AGI 277.1
Tau299.3
MRCR84.9
Input Price (per 1M tokens)$2.00$0.50
Output Price (per 1M tokens)$12.0$2.50
Context Window1M200K
Benchmarks Published165

Gemini 3.1 Pro vs Composer 2.5 head-to-head charts

Gemini 3.1 Pro leads 2 and Composer 2.5 leads 2 of 4 shared benchmarks. Composer 2.5 is cheaper on a defined 1M-input / 200K-output workload. Charts show only benchmarks both models publish.

Gemini 3.1 ProComposer 2.5
Overall
52.0Gemini 3.1 Pro
44.4Composer 2.5
Coding Agent Index
30.3Gemini 3.1 Pro
62.9Composer 2.5
SWE-Pro
54.2Gemini 3.1 Pro
49.2Composer 2.5
Terminal-Bench
68.5Gemini 3.1 Pro
69.3Composer 2.5
Gemini 3.1 Pro
Input$2.00
Output$12.0
Workload$4.40
Context1M
Composer 2.5
Input$0.50
Output$2.50
Workload$1.00
Context200K

Workload = published cost of 1M input + 200K output tokens. Open the live leaderboard for interactive compare charts.

More Gemini 3.1 Pro and Composer 2.5 comparisons

Explore how Gemini 3.1 Pro and Composer 2.5 stack up against other top-ranked LLMs.

How to read this comparison

Benchmark scores

Higher is better for all benchmark scores (SWE-bench, GPQA, HLE, Terminal-Bench, etc.). Green marks the model with the higher score.

Token pricing

Lower is better for input and output prices. Green marks the cheaper model per 1M tokens.

Coverage matters

Models with fewer disclosed benchmark cells may have inflated percentile scores. Check the benchmark cell count for context.

This comparison page is generated from the AskClash LLM leaderboard cache. Open the live leaderboard for real-time scores and interactive filtering.