
What Is Retrieval-Augmented Generation (RAG)?
Most people assume an LLM knows everything. Ask it about your company's return policy, and it will confidently answer—even if that policy changed last week…
Read tutorialStep into more advanced LLM applications: retrieval-augmented generation (RAG) and building simple AI agents.
Tutorials
Follow these lessons in order, or jump directly to the topic you need.

Most people assume an LLM knows everything. Ask it about your company's return policy, and it will confidently answer—even if that policy changed last week…
Read tutorial
Most people assume RAG is a different kind of model—a smarter cousin of the plain LLM. It's not. RAG doesn't change the model at all. It changes what goes…
Read tutorial
Reading about RAG is easy. Building one is where the real learning happens—because the first pipeline you run will almost certainly fail in ways no diagram…
Read tutorial
An LLM agent is not a smarter chatbot. It is a goal-driven system that uses a language model as its brain, then loops through action and observation until…
Read tutorial
Most beginners expect an agent to be a special kind of model—something with built-in magic that can browse the web, run code, and get things done. Then…
Read tutorial
You can explain RAG. You can sketch an agent loop. But when a real question lands on your desk, do you know whether to retrieve, route, or just answer?…
Read tutorial
You know RAG retrieves documents and feeds them to a language model. But if someone asked you what actually happens between a source PDF and a grounded…
Read tutorial
You search your company's help docs for "how do I reset my password?" and get nothing useful. You know the answer is in there—you've read the page…
Read tutorial
You ask your RAG system a question. It retrieves a passage that is technically relevant and completely useless—a sentence fragment that starts mid-thought,…
Read tutorial
You have a task that needs an LLM. The temptation is to reach for an agent—something autonomous, something that "figures it out." But most of the time, a…
Read tutorial
When people first hear that an LLM can "use tools," they usually picture the model reaching out and doing something itself—searching the web, running code,…
Read tutorial
Your agent runs. It calls tools. It produces output. And yet, something is wrong—or it never stops running at all. The frustrating part is that you can't…
Read tutorial
A vector database is not a fancy search box or a generic "database for AI." It is the retrieval engine that decides which evidence earns a seat on the…
Read tutorial
Your knowledge base has the answer. You know it does. You wrote the documents, chunked them carefully, embedded them, and verified the chunks look right.…
Read tutorial
Your retriever returns ten chunks. They all look topically related to your question. None of them actually answer it. The LLM dutifully composes a response…
Read tutorial
A citation is not proof. It is a pointer — and a pointer is only as trustworthy as the instruction that produced it and the check that verifies it.
Read tutorial
You build an agent. You chat with it for a few turns. It helps you draft a plan, picks a tool, runs it, reports back. Then you ask: "What was the second…
Read tutorial
Here's the scene I've watched play out more times than I can count: someone builds their first agent, gives it a task, and watches it loop. It calls a…
Read tutorial
Structured output and tool calling look almost identical from the outside. Both accept a JSON schema. Both return clean key-value pairs instead of…
Read tutorial