When to Use LangChain Reference Docs Instead of the Main Documentation Site

Updated

Use LangChain Reference Docs (reference.langchain.com) when you need to look up an exact API detail — a class, function, method signature, or type — across the LangChain ecosystem. Use the main documentation site when you need to learn a concept, follow a tutorial, or understand how a workflow fits together. The reference is a lookup tool; the main site is a teaching tool. Most real work involves both, switching between them as your question changes from "how does this work?" to "what exactly does this function accept?"

What LangChain Reference Docs Covers

According to the site itself, Reference Docs is a unified API reference for:

  • LangChain
  • LangGraph
  • DeepAgents
  • LangSmith
  • Integrations

It lets you browse packages and explore classes, functions, and types across the entire LangChain ecosystem, with packages available in Python, TypeScript, Java, and Go.

That scope matters for the decision: because it spans multiple products and languages in one place, it's the natural destination when you already know what you're looking for but not its exact shape.

Reference Docs vs. Main Documentation Site

Your question looks like… Go to
"What parameters does this class take?" Reference Docs
"What's the return type of this method?" Reference Docs
"Which module is this function in?" Reference Docs
"How do I build a RAG pipeline?" Main documentation site
"Walk me through a LangGraph agent" Main documentation site
"Why would I use this pattern?" Main documentation site

The site states this split directly: for guides, tutorials, and conceptual docs, it points you to the main documentation site. The reference assumes you already understand the concept and just need the precise interface.

Typical Lookup Tasks Suited to the Reference

  • Checking a method signature before calling it, so you pass arguments in the right order and type.
  • Confirming a type when your editor's autocomplete is ambiguous or you're working in a language whose tooling you're less familiar with.
  • Finding which package a class or function lives in, especially when the same concept appears across LangChain, LangGraph, or an integration.
  • Comparing the same API across languages — for example, verifying that a Python and TypeScript equivalent expose the same options.
  • Debugging a type error by reading the actual declared types rather than inferring them from an example.

How the Two Sites Complement Each Other

A common workflow alternates between them:

  1. Start on the main site to understand the approach — read the guide or tutorial for the task you're doing.
  2. Move to Reference Docs when the guide's example isn't quite your case and you need to see the full set of options.
  3. Return to the main site if the reference reveals a concept you don't recognize, since the reference explains what exists, not why or when to use it.

For example, a tutorial might show one way to configure a component. When your requirements differ, the reference tells you what else that component accepts — but the main site is where you'll learn which choice fits your situation.

A Practical Rule

If you can name the thing you're looking for (a class, function, or type), go straight to Reference Docs. If you can only describe the outcome you want, start on the main documentation site and let it point you toward the right API — then verify the details in the reference.