Read AI Agents Book Online Free: Part I of the Book, Mapped

You can read the opening of an AI agents book online free, with no sign-up: the Preface, Part I (Chapters 1 and 2) and the glossary of AI Agents, Engineered are open in the web reader. That is about 64 minutes of chapters plus a 22-minute glossary, written for engineers with no machine-learning background and tied to no framework.

A note on the search itself. When I typed “read AI agents book online free” into a search engine in October 2026, much of the first page was about a meeting-notes product called Read AI, because the phrase parses two ways. This page is about the book, and I wrote it as a map: what each free section teaches, how long it takes, what it leaves out, and who would be better served by something else.

I’ll start with what the chapters say, since a map is easier to trust once you have walked a little of the ground. The table of contents comes after.

What does the free part actually teach?

The free part teaches three things an engineer needs before building anything: a testable definition of an agent, a working model of the language model underneath, and the arithmetic of why long runs fail. Each comes with a decision rule you can use the same day, at work or in an interview.

The Preface sets the terms of the deal in one sentence: “The only prerequisite is ordinary engineering literacy; whenever a term of art appears, I define it on the spot, in plain words.” It also states the thesis the rest of the book keeps returning to: “an agent is only as trustworthy as the signal you can use to verify it.”

How does Chapter 1 define an agent?

Chapter 1 defines an agent as a language model placed in a loop, given a goal and tools, that picks an action, sees the result and goes again until it judges the goal met or a stopping rule ends the run. It opens by shrinking the topic to size: “Strip away the demos and the marketing, and the idea is small enough to hold in one hand.”

Then the chapter runs a small experiment on you, and it works better if you play along. It describes three systems.

The first is a question-and-answer assistant that explains code and waits for your next message. The second is a support pipeline that classifies a ticket, fetches a policy, drafts a reply and checks it, “four steps, in that order, every time.” The third is told to fix failing tests, and it searches, edits, reruns and stops when the suite is green. Its instruction is “Decide which of them is the agent before reading on.”

The chapter expects your instinct to pick the third, and the instinct is right. The useful part is the reason, which the chapter puts in one line: “That question—who owns the control flow—is the entire distinction.” All three could run on the same model. What differs is who decides the next step: you, your code, or the model.

That reasoning becomes the litmus test I find myself using more than anything else in the chapter: “If you can confidently draw the control-flow diagram before the request arrives, you are looking at a workflow. If the diagram can only be drawn in hindsight, once the model has reacted to what it found, you are looking at an agent.” A workflow, in the book’s vocabulary, is several model calls wired along paths your code defined in advance. The post on the difference between an AI agent and a chatbot applies the same test to the most common confusion, and a five-check test for what counts as an AI agent turns it into a procedure you can run on a real system.

What is the compass?

The compass is the book’s own device: four bearings stated in Chapter 1 and used to decide design questions throughout. They are verifiability, the scarcity of context, compounding error and the simplest thing that works. Chapter 1 states them briefly and admits the defense is the rest of the book.

The third bearing is where the chapter does arithmetic. As an illustration it supposes each step of a run succeeds 95% of the time; twenty chained steps then succeed about 36% of the time (0.95²⁰). The chapter is careful about what the example is worth: “The particular numbers vary; the arithmetic does not, and it is merciless.” If you want to try your own numbers, the compounding error calculator does it.

The chapter’s last section asks whether you need an agent at all and prices one in six costs: more model calls, more latency, nondeterminism, a wider failure surface, a wider attack surface and a larger operational burden. It closes on the sentence I would hand to any team about to build one: “An agent, then, is a cost you pay for adaptability you can name. If you cannot name the adaptability, keep your money.” The should this be an agent? decision tool walks the same ladder interactively.

What does Chapter 2 add about the engine?

Chapter 2 explains how a language model works, from next-token prediction to the ways it fails, and promises up front to do it “intuition first, with no mathematics beyond arithmetic.” It is the longest free chapter and the one I find students need most, because it replaces “it’s magic” with a model you can debug against.

Its central picture is the desk, the book’s image for the context window: the work surface on which everything the model consults during one call must fit at once. The chapter’s advice about it is one of the most quotable lines in Part I: “So the window is a ceiling, not a target; the useful question is the smallest desk that actually holds your task.”

Two more ideas from Chapter 2 change how you read any agent demo. On structured output, the model’s answer forced into a machine-readable shape, it draws a hard line: “One boundary I want marked in ink: a guarantee about shape says nothing about truth.” And after a catalog of failure modes that starts with hallucination, it returns to the compounding arithmetic, adds a worse case and ends on two sentences: “Exponentials do not negotiate.” and “Per-step accuracy is a ceiling, not a forecast.”

What does “read AI agents book online free” get you here, section by section?

It gets you ten sections in a fixed order: the Preface, the three sections of Chapter 1 and the six of Chapter 2, plus the glossary as a reference. Each row below says what question the section answers, so you can stop at any row and still leave with something usable.

The table below is the whole answer to “read AI agents book online free” on this site. Chapter totals are the web reader’s own labels. Section minutes are my estimates, computed from each section’s length and scaled to those totals, so treat them as approximate.

Section	The question it answers	Minutes	Figures	Glossary terms it treats
Preface	Who is this for, what will it refuse to do, and what is the thesis?	5	1	harness
1.1 The Agent Idea	What is an agent in one sentence, why did agents become practical, and what are the four bearings?	~6	1	agent, the compass, context window
1.2 Agents, Workflows, and Chatbots	Which system is the agent, and who owns the control flow?	~5	2	workflow, augmented LLM
1.3 Do You Even Need an Agent?	What does an agent cost, and how do you climb the ladder only as far as you need?	~5	1	agent-washing
2.1 LLMs as Next-Token Predictors	What is a model, mechanically, and why doesn’t it learn from your chats?	~6	1	LLM, autoregressive generation, token
2.2 Tokens and the Context Window	What is a token, what is the desk, and what happens when it overflows?	~9	1	token (in full), the desk
2.3 How Text Is Generated	Why do two runs differ, and what do temperature and sampling change?	~6	1	(none of the Part I headwords)
2.4 Prompting Fundamentals	How do roles, examples and ordering steer a model?	~7	1	system prompt (the system message), message history, in-context learning
2.5 Structured Output and Function Calling	How does text become a checked request to run code?	~7	1	structured output, constrained decoding, tool call
2.6 Limitations and Failure Modes	How do models fail, and why do failures compound across steps?	~8	1	hallucination
Appendix B, Glossary	What does this term mean, right now?	22	0	all of them

Some counts from the source, for scale. The free chapters carry 11 of the book’s 133 figures. The glossary has 87 defined headwords, and 17 of them point back to Chapter 1 or 2, which makes them the vocabulary a Part I reader meets first. The glossary explains its own purpose well: “This appendix exists for the other way people actually read a book like this: you are three chapters deep on a Tuesday, someone’s design document says idempotent, and you need the meaning now, without archaeology.”

In what order should you read the free chapters?

Read the Preface and Chapter 1 in one sitting, about 21 minutes, then Chapter 2 one section at a time. Keep the glossary open in another tab. The Preface itself says the book’s “seven parts” are “ordered as a course,” and Part I is the first unit of that course.

The order answers a question students ask constantly. One wrote on Reddit in 2026 that they wanted to “actually understand how agents work and build them from scratch” instead of learning one framework (r/AI_Agents). Concepts first is the shortest route to that, because Chapter 1 gives you the words a framework hides and Chapter 2 tells you why the thing behind the framework misbehaves.

If you have an interview this week, the highest-yield stops are 1.2 (the litmus test), 1.3 (the cost of an agent) and 2.6 (the failure catalog). If you are pairing the reading with a course, an AI agents study guide built on the glossary gives you a review plan, and the agent fundamentals pillar collects the shorter explainers. The short chatbot, workflow and agent explainer is a good warm-up before 1.2.

Does this book fit you?

The book fits you if you can program, have no machine-learning background, and want ideas that transfer across frameworks before you write agent code. It fits less well if you need runnable code tonight or want the mathematics of training. Tick what is true for you; the list works the same on paper.

Here is how to read your ticks.

Ticks	What it suggests
6 or 7	Start with the Preface now; the free part was written for you.
4 or 5	Read Chapter 1 (16 minutes) and decide there.
3 or fewer	Look at the alternatives below first; one of them is probably a better first text.
The pseudocode item is unticked	Pair the reading with a free course, or start with the course.

What does the free part not contain?

The free part contains no runnable code, no framework, and none of the methods for evaluation, security, reliability or cost. It has pseudocode and plain-text blocks only: a triage prompt, few-shot examples, a JSON schema sketch, a five-step function-calling exchange and a tool definition. The annotated minimal agent is Appendix A, A Minimal Agent, Annotated (in the full book), also in pseudocode: the book never switches to one language or SDK, so runnable code is something you write, or take from a course.

I would rather you knew that before reading than felt baited after. Part I raises questions on purpose and says where each one is answered, so the boundary of the free part is printed in the free part itself.

Part I raises it	Where in Part I	Where it is answered
What the loop looks like in code	1.1 The Agent Idea	Chapter 3, The Agent Loop (in the full book)
Why “are you sure?” is weak verification, and what a real verifier is	2.6 Limitations	Chapter 4, Planning, Reasoning, and Self-Correction (in the full book)
Routing exact work to tools, pushing bulk work into code	2.6 Limitations	Chapter 5, Tools and the Action Space (in the full book)
Deciding what deserves the desk	2.2 Tokens and the Context Window	Chapter 7, Managing the Context Window (in the full book)
Chaining, routing and parallelization	1.2 Agents, Workflows, and Chatbots	Chapter 10, Workflows and Composition Patterns (in the full book)
Whether to build an agent at all, with everything in between	1.3 Do You Even Need an Agent?	Chapter 14, Choosing Your Approach: When Not to Build an Agent (in the full book)
How to measure an agent and validate a model used as a judge	1.3 and 2.6	Chapter 16, Evaluating Agents (in the full book)
Blast radius and prompt injection	1.2, 1.3 and 2.6	Chapter 17, Security, Safety, and Guardrails (in the full book)
Checkpoints, so a failed run resumes instead of restarting	2.6 Limitations	Chapter 18, Reliability, State, and the Harness (in the full book)
The cost of re-reading a long context, and caching	2.2 Tokens and the Context Window	Chapter 19, Cost, Latency, and Performance (in the full book)

Is a book on AI agents outdated before you finish it?

Parts of any book on agents will age, and this one says so in the Preface. What it refuses to do is anchor on the season: no claim in it depends on which model is best, what a token costs or how large context windows are, and any number is marked as an illustration.

The worry is fair. A commenter on r/learnmachinelearning put it bluntly in 2024: “Agents are changing too fast for a book to be beneficial” (thread). A later reply in the same thread made the counter-case, that “there are are [sic] a few core ideas that are worth grokking for folks new to agents - the core agentic loop, orchestration patterns, ux consideration and integration into apps” (reply, 2026). The Preface makes the same wager in one line: “The bet this book makes is that principles outlive products.”

A related doubt is whether to learn this at all when a model can write an agent for you. My answer follows from the thesis: a model can write the loop, but you still have to judge whether it works, and you can’t judge a system you can’t describe. The litmus test and the compounding arithmetic are exactly the parts you need when reviewing an agent someone else, or something else, wrote.

Who should read something else instead?

Read something else if you want a complete free book today, runnable code this weekend, or the classical theory of agents. The free part here is a first part, ordered and short; the rest of the book is paid. If your search to read AI agents book online free was a search for one of those, here are honest alternatives by category, described from their own pages as I found them in October 2026.

If you want	Category	Examples
The classical, pre-LLM theory of agents, as a full textbook	Complete free textbook	Poole and Mackworth’s Artificial Intelligence: Foundations of Computational Agents, whose site says “The full text is now freely available”
A whole LLM-agent book, free, now	Complete free books	The open-source AI Agents in Depth (ten chapters and more than 90 open-source experiments, per its README in October 2026; the English edition is a community translation); Aslanyan’s 60-pattern guide on freeCodeCamp, one long page whose code it calls “schematic rather than runnable”
Hands-on code this weekend	Free courses	The Hugging Face Agents Course (it asks for basic Python and basic LLM knowledge, and its framework unit uses specific libraries); Microsoft’s AI Agents for Beginners (18 lessons, with code on that vendor’s own stack)
One short, high-signal read tonight	Free essays	Schluntz and Zhang’s “Building effective agents” (2024), which Chapter 1 cites; HumanLayer’s 12-Factor Agents

Some free books are written by companies that make agent frameworks; Mastra’s Principles of Building AI Agents, for example, is by the company’s CEO and is free in exchange for an email address. That is worth knowing; it is no reason to skip the book. For a wider, paid-and-free comparison, see an honest comparison of the best books on AI agents.

The one thing to keep

The free part of AI Agents, Engineered is an hour of reading that leaves you with a definition you can test, a model of the engine you can debug against, and arithmetic that explains why long runs fail. Read Chapter 1, “What Is an Agent?” first; if the litmus test changes how you see the next demo you watch, the rest of Part I will be worth your evening.

When you know whether the book fits, see the formats: the rest comes as PDF and EPUB on Leanpub, and as Kindle and paperback editions on Amazon.