Building AI Agents with Claude
M00 Study
Guide

Mobile revision aid — the whole M00 orientation on one thumb-scrollable deck. The arc from rule-based AI to production agents, the 7 building blocks, the lifecycle, the litmus test, and flash cards to check yourself before Module 1.

Reference ⏱ ~15 min read Quick reference
§1 · Reference

The 7 Eras of AI

Each era added a capability without erasing the previous ones. Today's agents still use rules, ML, transformers, and RAG — all at once. You add a reasoning layer on top; you don't replace what works.

EraAdded capability
1 · Rule-Based
1948–2000s
Follow human-written rules. Brittle — every edge case needs a new rule.
2 · Machine Learning
2000s–15
Learn patterns from data. One model = one task; can't reason or explain.
3 · Transformers
2017–20
Understand context; process unstructured text.
4 · Generative
2020–23
Create content. But reactive — can't call APIs or search.
5 · LLMs Mature
2023–24
RAG solves hallucination; tiered models solve cost. Still respond, don't act.
6 · Agentic ★
2024–now
Take actions. LLM + tools + loop + memory = reasons AND acts.
7 · The Frontier
2026+
Coordinate. Multi-agent systems via MCP + A2A protocols.

MCP = agent↔tool (Anthropic, 2024). A2A = agent↔agent (Google → Linux Foundation, 2025).

§2 · Reference

Why Agents Are Possible NOW

The headline isn't a smarter model — it's the scaffolding around it. Five capabilities went from impossible to production-ready between 2022 and 2026.

Capability20222026
Tool Use APInonenative
Structured Outputflaky JSONschema-guaranteed
Context Window4–8K200K–1M+
Inference Speed10–30s1–3s / turn
Cost / Token$0.06/1K$0.00025/1K

"Five years ago you could build a chatbot. Today you can build an agent. The difference isn't a smarter model — it's the tools, context, speed, and cost around it." Cost alone dropped 240× since GPT-3.

§3 · Reference

Three Approaches

Same question — "Is Acme Corp likely to go delinquent?" — three ways to answer. The ML model never disappears; the agent just uses it.

InputOutput
1 · Script
15 lines · ~$0
6 numbers, by hand0.823, no context
2 · FastAPI
35 lines · ~$0
{"name":"Acme"}score; misses DBA names
3 · Agent ★
70 lines · ~$0.05
Plain EnglishNarrative report, 7 filings, cites evidence

In Approach 1 the model is the product. In Approach 3 the model is one tool the agent calls when it needs a probability — surrounded by reasoning, search, and narrative.

Every ML model your team shipped can become an agent tool tomorrow.

§4 · Reference

What IS / ISN'T an Agent

One question: who decides what happens next — your code, or Claude?

LevelLoop?Who decides
1 · LLM Call
1 call, no tools
noYOU
2 · Workflow
fixed sequence
noYOU + Claude
3 · True Agent ★
dynamic tools
yesCLAUDE every turn

The litmus test: replace the LLM with hardcoded responses. If the program still works the same — NOT an agent. If it breaks because Claude was deciding at runtime — it IS one.

Level 3 needs all three: Tools (act on the world) + Loop (act again) + Decisions (choose from findings).

§5 · Reference

The 7 Building Blocks

Like parts of a body — drop any one and your agent stops being trustworthy. Most tutorials teach only blocks 1–2.

BlockJobTrack
1 BrainLLM reasons & decidesM01–04
2 ToolsCall APIs, DBs, filesM05–07
3 MemoryHistory + RAG retrievalM08–11
4 PlanDecompose, order, retryM12–15
5 GuardrailsValidate I/O, escalateM16–18
6 EyesLog, trace, monitorM19–20
7 HomeDeploy, scale, costM21–22

Brain + Tools = 2 of 7. An agent that works on your laptop but can't be trusted in production is a prototype, not a product.

§6 · Reference

The Agent Lifecycle

Building an agent isn't "write code and ship." Five stages, each adding a critical layer.

1 Design 2 Build 3 Protect 4 Observe 5 Deploy
  1. DesignScope, tools, data access. (Tracks 1–2)
  2. BuildDefine tools, engineer prompts, wire the loop, add RAG. (Tracks 2–4)
  3. ProtectValidate I/O, cap loops, add human-in-the-loop. (Track 5)
  4. ObserveTrace every tool call, log decisions, score outputs. (Track 6)
  5. DeployFastAPI/Docker, Cloud Run/Lambda, cost + rate limits. (Track 7)

⚠ "I'll add guardrails later" costs 4× more. Build safety in from the start — even a simple max_turns=10 counts.

§7 · Reference

How Agents Actually Work

An agent is your code calling Claude's API in a loop. No magic runtime — you are always in control.

# THE UNIVERSAL AGENT PATTERN
user_asks_a_question()

while claude_wants_a_tool:
  reply = send_to_claude(question + history)

  if reply.stop_reason == "tool_use":
    result = run_tool(reply.name, reply.args)
    history.append(result)   # one iteration
  else:
    return reply.text        # final answer

The while loop is the entire agent. Claude replies with a tool_use block (run this) or end_turn (final answer).

Every call is stateless — you resend the full history each time. Between calls, nothing "thinks." Same loop runs on a laptop, behind FastAPI, or in a cron job.

§8 · Reference

Common Misconceptions

"Agents run autonomously 24/7."
An agent runs when YOUR code calls it and stops when the task is done. It doesn't act between calls.
"An agent is just a smarter chatbot."
A chatbot responds in one turn. An agent uses tools, decides, and loops until done — it acts on the world.
"Agents are hundreds of lines."
The core pattern is ~10–15 lines. You'll have a working agent by Module 5.
"It might go rogue."
It can only use tools YOU define. You control the loop, limits, and approval gates. Track 5 is all safety.
"Claude's built-in safety is enough."
It can't know your business rules or compliance needs. Your guardrails complement Claude's.
§9 · Reference

Market Stats to Memorize

When a peer asks "is agentic AI real or hype?" — keep these in your back pocket.

$500M+raised by agentic-AI startups in early 2024
20–30%operational cost cut reported by enterprises deploying agents
35%faster decision automation with agentic workflows
240×cost drop per token since GPT-3 (2022) → Claude 3 Haiku (2024)
24/30major AI agents launched/updated in 2024–25 (MIT AI Agent Index)
>All2024 "AI agent" papers exceed all prior years combined
§10 · Reference

Quick-Reference Flash Cards

Tap to reveal the answer. If you can answer all six, you're ready for Module 1.

§11 · Reference

Course Track Map

7 tracks, 30 modules — building block by building block.

TrackBlockModules
1Brain — how LLMs thinkM01–04
2Tools — the handsM05–07
3Memory — RAGM08–11
4Plan — ReActM12–15
5GuardrailsM16–18
6ObservabilityM19–20
7DeployM21–22

"In five years most APIs will still be FastAPI and most ML models still pickle/ONNX. The change is Layer 3 — the reasoning that decides how to use them. That's what this course teaches."

Open the full study guide on desktop

The desktop version is the complete, print-ready study guide — the full era timeline, all comparison tables, the 12 flash cards, and the course roadmap laid out for review or printing.

Open the full study guide on desktop → Print-ready reference · 11 sections + roadmap

M00 Study Guide · Building AI Agents with Claude