LangGraph vs Pydantic AI: Which Agent Framework to Use?

LangGraph and Pydantic AI both let you build an agent, but they sit in different parts of the stack and they assume different things about who's writing the code.

LangGraph is LangChain's stateful workflow framework — a graph of nodes (functions) connected by edges with shared state.

Pydantic AI is a type-safe agent framework built by the Pydantic team.

Underneath, both wrap the same thing: a model call, a tool dispatch, a loop. The decision is about which abstraction your team wants to think in day to day, and which ecosystem you're willing to inherit along with it. There's an honest, framework-free version of the same pattern in about 60 lines of Python in the lesson at the bottom of this page — useful as a baseline regardless of which framework wins.

Pick LangGraph if langGraph earns its weight when your agent is a workflow — explicit branches, checkpoints, parallel branches, or a human approval gate. For a single-agent loop, the graph machinery is overkill and a plain while loop is faster to write, debug, and ship. The tradeoffs in its intro should match how your team already thinks about agents; Pydantic AI will feel like translation if they don't.

Pick Pydantic AI if pydantic AI adds genuine value if you want compile-time type checking across your agent's tools, outputs, and dependencies. If you already use Pydantic in your stack, it fits naturally. But the core agent logic — loop, dispatch, validate — is still ~60 lines of Python you can own entirely. The tradeoffs in its intro should match how your team already thinks about agents; LangGraph will feel like translation if they don't.

Whichever you pick, you're inheriting a dependency tree and a vocabulary your team has to learn before they ship anything. LangGraph has its own class hierarchy and tool registration conventions; Pydantic AI has its. Either way, when something misbehaves you'll be reading framework source before you reach the actual HTTP call.

If the real workload is one model and a handful of tools, both can feel like a workbench for driving a nail. The lesson below builds the same pattern in plain Python — useful as a comparison point even if you ultimately keep the framework.