$2
Input $/M
$6
Output $/M
1M
Context
47
Speed tok/s

Agent scores

Terminal-Bench 2.x

shell agent loops

Can the model finish real terminal / shell-agent tasks end to end — install tools, run commands, recover from errors.

0–100, higher is better. 70+ means a usable coding agent in a terminal; 80+ is frontier agent quality.

Editorial scores, not auto-scraped. Versions (2.0 vs 2.1) are not always comparable.

86.6 ★ (v)

SWE-bench Pro

software engineering

Can the model solve real software-engineering problems — patches, reviews, and repo-level fixes — in a single pass.

0–100, higher is better. A high score means stronger code-review and patch quality, not just snippet completion.

This is SWE-bench Pro, not SWE-bench Verified. Vendor harness notes are marked (v).

67.7 (v)

MCP-Atlas

multi-tool use

Can the model use many Model Context Protocol tools together — pick the right tool, pass arguments, and chain calls.

0–100, higher is better. High scores matter if your agent talks to GitHub, browsers, databases, or other MCP servers.

—

SWE-Marathon & Long-Horizon

sustained multi-hour work

Whether the model stays useful over long agent sessions instead of collapsing after a few dozen steps.

Mixed — not one number. Use this as supporting evidence for long-running agents, not as a ranking against TB or SWE-Pro.

Entries mix DeepSWE percentages, Marathon raw scores, and tool-call counts. Bars are editorial, not a shared scale.

56.6% DeepSWE (v)

Vendor launch scores

Qwen 3.8 Max vendor · 2026-08. Vendor harness — not independent evals.

BenchmarkScoreNote
Coding
QwenReactBench1724(v)
Agentic
Toolathlon72.5(v)

(v) = vendor harness.

Extended scores

BFCL

function calling

Berkeley Function Calling Leaderboard (V4): can the model call APIs with the right names, types, and arguments.

0–100, higher is better. Useful when the job is structured tool calls rather than a full agent loop.

Coverage is thin on newest models. Sourced manually from the Berkeley leaderboard.

—

tau-bench

multi-turn agent tasks

Can the model hold a multi-turn tool-using conversation and finish a policy-constrained task.

0–100, higher is better. High scores help for customer-support-style agents that must follow rules across turns.

—

AIME

math reasoning

American Invitational Mathematics Examination problems — contest math, not coding.

0–100, higher is better. A proxy for careful multi-step reasoning. Weak signal for terminal or repo agents.

—

MMLU-Pro

knowledge breadth

Harder multiple-choice knowledge questions across academic subjects.

0–100, higher is better. Shows general knowledge. Does not measure tool use or coding agents.

—

LiveCodeBench

live coding

Can the model solve fresh programming problems (contamination-resistant coding).

0–100, higher is better. Complements SWE-Pro: LiveCode is contest-style code, SWE-Pro is repo engineering.

—

Where to buy

ProviderTheir priceNoteLink
OpenRouter$6TB 86.6 (v) · $2/$6—
Nous Portal (via OpenRouter)SubsubLatest Qwen · TB 86.6 (v)—

Editorial routing

Task matrix
TaskRoleNote
Long-horizon multi-tool agentAlternativeToolathlon 72.5 (v)
Terminal-agent loopsAlternative86.6 (v) · $6/M
Frontend / web devAlternativeReactBench 1724 (v)
Long-horizon autonomousAlternativeDeepSWE 56.6% (v)
Budget and pairs