Tier 3 · Guard & build3.512 min

Which model tier runs your agent

A fiery orange-and-pink sunset over a harbour ringed by dark hillsAgents at Work — CC BY 4.0

The last lesson asked one question about your model — whose computer is it running on? (custody). This one asks the other half: which tier of model should run this agent? When you’re running one agent it barely matters. When you’re running several, or one of them daily, it becomes a real decision — about cost and about quality — and it’s Anchor 2, continuous improvement, in a very concrete form: put the capability where it earns its keep, and not a dollar more.

The two instincts that both fail

“Always use the best.” Comfortable, expensive, and it teaches you nothing about where the money is doing work. “Vibes” — this agent feels important, so it gets the top model. But how important an agent feels correlates badly with the specific kind of difficulty a stronger model actually addresses. Most agents aren’t limited by the model’s capability; they’re limited by a vague job or messy inputs, and a bigger model fixes neither.

The disciplined answer is the same triage the whole course has taught, pointed at your gallery: score each agent on the characteristics that genuinely reward a stronger model, and pay the top tier only where they’re present.

And the two things a bigger model will not fix — which the earlier tiers already taught you:

Then two plain checks: readiness — a capability-hungry agent handed a vague job produces expensive confusion, not brilliance — and volume — tier pricing barely matters for a once-a-week agent and compounds for one that runs all day.

The move that keeps it model-agnostic

Here’s what makes this sit cleanly beside the last lesson rather than fighting it: the framework doesn’t care whose model it is. It tells you where capability earns its keep — and that’s just as true of the sovereign, New-Zealand- or EU-hosted models from Lesson 3.4 as of any public frontier tier. So the two questions compose into one grid:

A sensitive-data agent belongs on sovereign infrastructure whatever its tier; a capability-hungry agent on non-sensitive work can reach for the strongest tier available. You allocate on both axes, deliberately, rather than defaulting the whole fleet to the most expensive box.

Naming the tier — carefully

At the time of writing, the most capable widely-released model is Claude Fable 5, above the Opus, Sonnet, and Haiku tiers — but that is exactly the kind of fact that dates: names, capabilities, and prices change often, and the sovereign options move too. The durable claim is simply that a higher tier is more capable than the ones below it. For current specifics, check the source (anthropic.com/news, docs.claude.com) rather than trusting a course page from memory — the same evidence discipline you’d demand of the agent itself. (This course’s legislative-watch keeps an eye on when these facts shift.)

The build move

Take the agents in your gallery. Which one would you actually pay the top tier for — and can you name which of reasoning, synthesis, or strategic depth justifies it? If the honest answer is “it just feels important,” that’s the instinct this lesson exists to check.

Next

That’s the guard-and-build tier done: scope, criteria, guardrails, testing, the two builds, and the two questions about your model — whose computer, and which tier. Tier 4 puts the agent to work and keeps you answerable for it.

Marking this lesson complete saves your progress on this device — no account, no tracking.

Shared freely, in good faith. If it's been of value, a koha toward development and running costs is warmly welcomed.

Leave a koha →

Useful? Share this lesson with a colleague.