Understanding models · Chapter 8 of 8
Choosing a model for an agent
Choosing a model means removing the ones that fail a hard limit, then weighing capability, speed, price per task, context and reliability with tools for one agent's job.
Goals
- Pick an agent to choose a model for.To do
- Apply its hard limits and see which models drop out.To do
- Weigh what is left, rank it and price a month of work.To do
- Pass the check.To do
Step 1 of 4: The read
A fit, not a best
There is no best model, only the best fit for one agent's job. Choosing takes two passes. First come the hard limits: needs the agent cannot do without. A model that fails one is out, however strong or cheap it is. Then you weigh what is left: you decide how much each quality matters for this job, and rank the models by it.
Hard limits
Modality: the kinds of input and output a model handles, such as text, images or sound. Context window: how many tokens it reads at once, as in chapter 2. Data policy: whether the provider may train its models on what you send, and retention, how long it keeps it. Region: where your data is processed; some rules, such as the EU's, care where. Licence and access: what you may do with a model, and who may use it at all. Open weights can also run on your own machine, even with no internet.
What you weigh
Capability: how well it does the job. Benchmarks, as in chapter 7, help when their tasks are close to yours, but your own eval says more: a few dozen real tasks from the job, scored by you. Latency: how long you wait for an answer; more thinking usually means better answers and longer waits.
Price per task: what one finished task costs. An agent calls its model several times per task, and each call is a turn, billed for its tokens in and out. A cheap price per token can still mean an expensive task. Tool-call reliability: how often the model calls tools correctly, with the right inputs. Rate limits: how many requests and tokens a provider accepts per minute.
In the visual
You pick one of four agents. Its hard limits remove models, your weights rank the rest, and a calculator turns real list prices into a monthly bill. A worked answer then shows what its choice gives up. The agents and their task sizes are made up. The models, prices, context windows, inputs, licences and scores are real, from a snapshot dated 2026-11-03. The snapshot has no regions and only some data terms, so some limits say Check; it has no speeds or rate limits, so you test those yourself.
Step 2 of 4: Try it: Choose a model for this agent
Choose a model for this agent
Pick an agent, apply its hard limits one at a time, weigh what is left and price a month of work, then compare with a worked answer.
Mode:RealSimulatedReal: the models and their list prices, context windows, inputs, sizes, tool use, licences, Google's and Meta's data terms by plan and Artificial Analysis scores, in a snapshot dated 2026-11-03; prices per task and the ranking are worked out from them in this page. Simulated: the four agents, their limits and task sizes, and the worked answers are made up for this chapter, and no model runs in this page.
Step 3 of 4: Check
Check
Next: Question 2 of 3
Step 4 of 4: What you can do now
What you can do now
- Separate the hard limits that remove a model from the qualities you weigh.
- Work out a price per task and per month from tokens, turns and list prices.
- Rank a shortlist by what matters for one agent, and say what the choice gives up.
- Name what a model's page cannot tell you, and test it in your own eval.