Online course
Building AI Agents
Design, build and evaluate agents that do real work: when an agent beats a plain workflow, how the loop actually runs, how to design tools a model can use well, how to keep it safe and affordable, and how to know whether it works.
Not yet reviewed
This content has been authored but not yet reviewed by a qualified subject-matter expert.
What you’ll build
Each lab asks you to produce something real and gives you the checklist to judge it against. Write your answer in the lab, and ask for feedback on it.
- Redesign a tool
Rewrite a poorly designed tool declaration so a model can use it correctly first time.
- Write the standing brief
Write a system prompt that still governs an agent on its twelfth turn.
- Choose the pattern
Select an orchestration pattern for a set of real problems and defend each choice in a sentence.
- Find the hole
Threat-model an agent design: sort its actions by reversibility and find the path an attacker would take.
- Write the eval set
Turn real production failures into evaluation cases that would catch them again.
What you’ll be able to do
- Language model fundamentalsfoundational
- Prompt designfoundational
- Choosing between a workflow and an agentworking
- The agent loopworking
- Tool designworking
- Context engineeringworking
- Retrieval and groundingworking
- Agent memoryworking
- Orchestration patternsworking
- Multi-agent systemsfoundational
- Agent evaluationworking
- Agent observabilityworking
- Failure and recoveryworking
- Agent safety and permissionsworking
- Prompt injection defenceworking
- Cost and latency engineeringworking
Credential
Once an expert has reviewed this course, passing its final exam earns a verified credential that appears on your profile where employers can see it. It has not been reviewed yet, so for now the exam is practice: passing it cannot issue a credential, and each attempt still counts toward your limit. 12 questions, 45 minutes, 75% to pass, up to 3 attempts.
Learning is free, and nothing anywhere on the site is charged today. Certification is where a fee is planned, because that is what makes a credential mean something to an employer.
Course content
1 What an Agent Actually Is
Three different things get called an agent. Telling them apart is the first real decision you make.
- Models, workflows and agents
Distinguish a single model call, a workflow, and an agent, and say which one a given problem needs.
- The loop, in one page
Describe the agent loop end to end and name what terminates it.
- When not to build an agent
Apply a test for whether a problem justifies an agent, and pick the simpler option when it does not.
- What autonomy costs
Name the three costs autonomy adds and estimate them for a proposed agent before building it.
- Models, workflows and agents
2 The Loop in Practice
The mechanics: how tool calls travel, how errors teach, and how the loop ends.
- Tool use, mechanically
Trace one tool call from declaration through the model’s request to the result you send back.
- Errors are part of the conversation
Return failures to the model in a form it can recover from, and recognise which failures it must not see.
- Stopping: budgets, limits and done-ness
Choose stop conditions for an agent and explain what each one protects against.
- State between turns
Decide what belongs in the conversation, what belongs in your own storage, and why.
- Tool use, mechanically
3 Designing Tools
The interface between your systems and a model deserves as much care as the one you design for people.
- A tool is an interface for a model
Explain why tool design is interface design, and evaluate a tool from the model’s point of view.
- Names, descriptions and schemas
Write a tool description and schema that a model can use correctly first time.
- Making the wrong call hard
Redesign a tool so that a plausible mistake becomes impossible rather than merely discouraged.
- How many tools is too many
Judge when a tool set has grown too large and apply a strategy for keeping it usable.
- Lab: redesign a tool
Rewrite a poorly designed tool declaration so a model can use it correctly first time.
- A tool is an interface for a model
4 Context Engineering
The model knows only what is in front of it. Deciding what that is, on every turn, is most of the craft.
- The context window is a budget
Account for what fills a context window during an agent run and explain why quality falls before the limit does.
- What belongs in a system prompt
Write a system prompt for an agent that states role, boundaries and process without bloat.
- Grounding: retrieval and citations
Design an agent so its factual claims are traceable to something a tool returned.
- Long tasks: compaction and handoff
Keep an agent working on a task longer than its context window without losing what matters.
- Lab: write the standing brief
Write a system prompt that still governs an agent on its twelfth turn.
- The context window is a budget
5 Orchestration Patterns
Five arrangements that cover most of what people build, and the honest test for when to reach past one agent.
- Chaining and routing
Apply prompt chaining and routing, and say which problems each fits.
- Doing things at once
Use sectioning and voting appropriately, and recognise when parallelism is false economy.
- Orchestrator and workers
Describe the orchestrator–workers pattern and identify the problems it fits.
- Evaluator, optimiser, and how many agents
Apply the evaluator–optimiser loop, and apply an honest test before adding a second agent.
- Lab: choose the pattern
Select an orchestration pattern for a set of real problems and defend each choice in a sentence.
- Chaining and routing
6 Making It Trustworthy
An agent that acts on the world needs permission, defences against text that lies to it, and a record of what it did.
- Permission, and the person in the loop
Classify an agent’s actions by reversibility and decide which require a person to approve.
- Untrusted content and prompt injection
Explain indirect prompt injection and apply the boundary that contains it.
- Blast radius
Bound what an agent can affect, so that a bad run is contained by design.
- Recording what the agent did
Specify the record an agent run must leave, and explain who each field is for.
- Lab: find the hole
Threat-model an agent design: sort its actions by reversibility and find the path an attacker would take.
- Permission, and the person in the loop
7 Knowing It Works
Impressions do not survive contact with production. This is how you find out whether your agent is any good.
- What to measure
Choose an end-to-end success measure for an agent and avoid measuring the wrong thing.
- Building an eval set from real failures
Assemble a small evaluation set that catches regressions, from cases that actually occurred.
- Using a model as a judge
Use model-graded evaluation where appropriate and name the failure modes it brings.
- Cost, latency and shipping
Plan a first release of an agent that is affordable, observable and reversible.
- Lab: write the eval set
Turn real production failures into evaluation cases that would catch them again.
- What to measure
8 Case Study: Meridian Tools
One team, one agent, six weeks. What they built first, what it cost them, and what actually shipped.
- The brief, and the first mistake
Identify, from a realistic brief, the point at which a team over-reached for autonomy.
- Rebuilding around what is actually known
Restructure an over-autonomous system into a router with one genuinely agentic branch.
- The week it went wrong
Trace three production incidents to the design decisions that permitted them.
- What shipped, and what the numbers said
Read an agent programme’s results honestly, including what it did not achieve.
- The brief, and the first mistake

