Fundamentals that still matter
REST, HTTP, auth, JSON, and the request-response dance — taught the way a senior writer would actually teach a junior, not the way Wikipedia would.
A free, opinionated course rewritten for 2026 — from REST fundamentals to MCP, function-calling, and writing docs that LLMs can actually use. Taught through one running example: the Greenfield Library API.
/books/{id}: get: summary: Get a book by id parameters: - name: id in: path required: true schema: type: string responses: '200': description: OK▌
GET /books/{id}
Fetch a single book from the Greenfield Library.
Use this when a reader scans a barcode or an agent resolves a citation. Returns title, author, due date, and the hold queue length so your UI can show "3 ahead of you" without a second round-trip.▌
"The next decade of API documentation isn't about writing more — it's about writing so that an agent at 2am can use your API without paging a human."
— Maya, Lesson 14
Every lesson rewritten with AI as a thread — not a chapter you skip to. You'll learn REST the old-fashioned way (because the fundamentals didn't change), then carry the same fictional Greenfield Library API through structured outputs, function-calling, and MCP servers.
REST, HTTP, auth, JSON, and the request-response dance — taught the way a senior writer would actually teach a junior, not the way Wikipedia would.
Streaming, SSE, WebSockets, gRPC, GraphQL, AsyncAPI — the API shapes that didn't exist when most courses were written.
Writing for LLMs, MCP, function-calling schemas, agent-friendly errors, and the AI co-pilot tip in every single lesson.
I've documented APIs at three companies you've probably used today. This course is the one I wish I'd had when I started — opinionated, honest about the boring parts, and built around one fictional API (the Greenfield Library) instead of a different vague example in every lesson.
The big change in 2026: I'm not your only co-author anymore. An LLM is reading these docs alongside you, and almost certainly reading yours too. So every lesson ends with an AI co-pilot tip — the actual thing I'd do, with the actual model, today.
I write one lesson a week. I answer questions in the floating chat. I send one email when a new lesson lands. That's the whole deal.
Tuesday evening at the branch. I was at the desk updating index cards for the new arrivals. Sam, an old friend of Devon's, came in returning a book and stayed to chat. He watched me for a minute. "You know you could just expose this as an API, right?"
A few days later I was sitting with Devon, looking at what that actually meant. Before we could write a single line of documentation, I had to understand what we were even trying to build.
Continue reading →No course-bro upsells. About one email every two weeks when a new lesson goes live or a tool changes.
No sign-in. No password. Just a first name we'll store on your device so Maya can stop saying "friend."
Stored in your browser only. Clear any time from the footer.