An agent model needs to interpret a goal, obey constraints, use tools and recover from mistakes. Our General agent profile weights reasoning, instruction following, agentic coding and data work to build a practical first shortlist.
Use the General agent profile for mixed workflows. Switch to Coding assistant for repository work, Research & analysis for structured information, or Writing & support for language-heavy tasks. These editorial weights express priorities; they do not reproduce your production environment.
02 / WHAT TO CHECK
Tool support is only the entry ticket
A tool-calling API can return a correctly shaped function call while choosing the wrong action. Check the catalog support flag, read Berkeley’s separate tool-use results, and test the exact tools, schemas and permissions your own agent will use.
03 / WHAT TO CHECK
Measure the cost of a completed task
A cheap token rate can still produce an expensive agent if it needs repeated attempts or very long reasoning. Enter total billed output, including hidden reasoning where charged. Track success rate, retries and human review alongside the bill.
04 / WHAT TO CHECK
Run a small, representative evaluation
Take 20–50 real tasks, remove private data where appropriate, and define what a successful result looks like before running models. Keep the prompt, tool definitions, reasoning budget and retry policy fixed. Include ambiguous requests, missing inputs and failing tools.
Make the numbers yours Estimated text API bill: requests × (input tokens × input price + output tokens × output price) ÷ 1,000,000. Include billed reasoning in output tokens. Excludes caching, tools, retries, taxes, hosting and long-context premiums.
Standard text API estimate. Include reasoning tokens in output.
A scenario estimate, not a measured task bill. Excludes cache discounts, tool fees, retries and provider premiums. Workloads exceeding a catalog context limit receive no cost or Value rating. Advertised context is not a guarantee of retrieval quality.
THE MARKET MAP
Capability meets cost.
Efficient frontierOther modelsHigher + further left = more for less
Practical Value Our blend of Agent Fit and affordability: 70% capability + 30% cost percentile by default. Cost uses your token workload. A relative score within this 56-model snapshot, not a claim of dollars saved. · General agent
70% Agent Fit + 30% affordability. Rankings use your workload; filters do not change the reference cohort.
THE EVIDENCE, SIDE BY SIDE
AI model comparison table
56 of 56 models · select up to 4 to comparePrices in USD · scores explained with ?
AI model benchmarks, aggregate ratings, API pricing and context windows. Snapshot 2026-09-23.
Compare
Our task-weighted mix of LiveBench category scores. A useful shortlist signal, not a measured agent success rate. Change the task profile to change the weights.
Our blend of Agent Fit and affordability: 70% capability + 30% cost percentile by default. Cost uses your token workload. A relative score within this 56-model snapshot, not a claim of dollars saved.
Equal-weight average of LiveBench and Arena percentile ranks within the same nine matched configurations. Models without both results receive no score. This small cohort does not rank the whole market.
Automatically checked tasks in seven areas: reasoning, coding, agentic coding, mathematics, data analysis, language and instruction following. Overall is the equal-weight category mean. All rows use the 2026-06-25 question set.
People compare answers without knowing which model wrote them. A higher rating means more preferred answers, not a percent correct. Published ± ranges can overlap; small score gaps may not mean a real difference.
Estimated text API bill: requests × (input tokens × input price + output tokens × output price) ÷ 1,000,000. Include billed reasoning in output tokens. Excludes caching, tools, retries, taxes, hosting and long-context premiums.
The advertised token capacity for the prompt, conversation and response. This is a size limit, not proof the model can reliably use every detail. Catalog endpoints may have different limits.
— means missing comparable evidence, never zero. Consensus covers only nine matched configurations. Model IDs, reasoning settings, source links and pricing differences are available on every model page. Open weights does not imply unrestricted commercial use.
Agent FitOur task-weighted mix of LiveBench category scores. A useful shortlist signal, not a measured agent success rate. Change the task profile to change the weights.
79.4
74.7
78.9
Practical ValueOur blend of Agent Fit and affordability: 70% capability + 30% cost percentile by default. Cost uses your token workload. A relative score within this 56-model snapshot, not a claim of dollars saved.
61.0
62.7
83.5
Evidence ConsensusEqual-weight average of LiveBench and Arena percentile ranks within the same nine matched configurations. Models without both results receive no score. This small cohort does not rank the whole market.
Insufficient evidence
Insufficient evidence
Insufficient evidence
Workload costEstimated text API bill: requests × (input tokens × input price + output tokens × output price) ÷ 1,000,000. Include billed reasoning in output tokens. Excludes caching, tools, retries, taxes, hosting and long-context premiums.
$80
$40
$2.14
Context windowThe advertised token capacity for the prompt, conversation and response. This is a size limit, not proof the model can reliably use every detail. Catalog endpoints may have different limits.
1.00M
1.05M
1.05M
Tool callingThe catalog declares support for returning structured tool calls. Support does not measure whether the model picks the right tool or uses it correctly.
Supported
Supported
Supported
ReasoningCan it work through constraints and connect clues? LiveBench uses spatial, navigation, perspective-taking and logic-puzzle tasks. Useful for planning, but not a direct test of long-running agents.
92.2
88.7
86.7
CodingCan it write or complete code that passes tests? These are contained programming problems, not entire software projects.
89.3
81.8
80.0
Agentic codingCan it edit code in a tool-using workflow? LiveBench tests JavaScript, TypeScript and Python tasks. Results depend on the benchmark harness as well as the model.
71.7
52.9
77.3
MathematicsCan it solve difficult quantitative problems with checkable answers? Strong math is useful evidence of reasoning, but does not guarantee better writing or tool use.
97.1
96.4
93.3
Data analysisCan it join and reformat tables and reason about event sequences? Useful for agents that process structured business information.
80.3
81.2
79.3
LanguageCan it interpret word relationships, reconstruct plots and correct typos? This is a narrow language test, not a full measure of writing quality or multilingual coverage.
86.3
85.3
81.2
Instruction followingCan it follow requested constraints while rewriting, simplifying, summarizing and composing text? Relevant to agents that must return a specific format.