Pydantic AI
No written verdict yet. Here is what commenters said.
Why people recommend it
“multi-provider (OpenAI/Claude/Gemini/Bedrock), swappable in one line via PydanticAI.”
“pydantic-ai has been a superb addition to the AI engineering toolkit”
Show 3 more
“migrate an app from Claude SDK to Pydantic AI to get off claude API pricing”
“We maintain 5 open-source libraries built on Pydantic AI”
“I think the PydanticAI framework has the right approach of encouraging Agent Delegation & sequential workflow first”
Caveats and dissent
“Getting those agent systems to behave reliably was often annoying and tricky.”
Show 1 more
“Pydantic is a VC backed business now trying to funnel people into using their paid cloud services. No thanks.”
Often compared with
Who recommends it in their own words
From the makers not counted in the ranking
“we’re implementing Code Mode in https://github.com/pydantic/pydantic-ai/pull/4153”
“We’re implementing Code Mode in https://github.com/pydantic/pydantic-ai/pull/4153”
“one of the fastest growing agent frameworks”
Threads where it came up
- Agent design is still hard 4 mentions
- Python interpreter written in Rust for use by AI 2 mentions
- Why we migrated from Python to Node.js 2 mentions
- Ask HN: Who is hiring? (September 2026) 1 mention
- Ask HN: Who wants to be hired? (August 2026) 1 mention
- Ask HN: Who is hiring? (August 2026) 1 mention
Also written as PydanticAI, pydantic-ai, Pydantic-AI. Data: pydantic-ai.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 29
“Stack: Python, PydanticAI, Restate for durable execution”
“multi-provider (OpenAI/Claude/Gemini/Bedrock), swappable in one line via PydanticAI.”
“Python/Django/Pyramid/Pydantic AI hacker”
“Getting those agent systems to behave reliably was often annoying and tricky.”
“pydantic-ai has been a superb addition to the AI engineering toolkit”
“migrate an app from Claude SDK to Pydantic AI to get off claude API pricing”
“them had it.”
“built on Pydantic AI”
“We maintain 5 open-source libraries built on Pydantic AI”
“Pydantic is a VC backed business now trying to funnel people into using their paid cloud services. No thanks.”
“I think the PydanticAI framework has the right approach of encouraging Agent Delegation & sequential workflow first”
“uses PydanticAI and MCP-based tools”
“patch the framework (e.g. PydanticAI) at the entry point”
“It works pretty well, and is comparable to Langchainv1 and Pydantic-AI”
“a framework that extends Pydantic-AI with powerful”
“built on top of Pydantic-AI”
“This framework extends pydantic-ai with the stuff I kept rebuilding across projects”
“It's built on top of pydantic-ai”
“built on top of Pydantic AI”
“Pydantic also has a first party integration with DBOS”
The framework has the following capabilities: 1. A way to create function tools 2. A way to create specialised subagents that can use their own tool or their own model. The main agent can delegate to subagent exposed as a tool. Subagents don’t get confused because they have their own context window, tools and even models (mix and match Remote LLM with Local LLM if needed) 3. Don’t use all tools of the MCP servers you
I agree with your analysis of building your own Agent framework to have some level of control and fewer abstractions. Agents at their core are about programmatically talking to an LLM and performing these basic operations: 1. Structured Input and String Interpolation in prompts 2. Structured Output and Unmarshalling String response to Structured output (This is getting easier now with LLMs supporting Structured outpu
“We've tried many approaches and frameworks over the past 2 years (e.g. PydanticAI), but using cc is the first that has felt magic.”
“I really like https://ai.pydantic.dev/ as it builds on existing developer knowledge and there is not much to learn in the framework itself.”
“I use it with the PydanticAI framework and it's quite nice.”
“PydanticAI has DBOS built in”
async python has problems, but "anyio exists" is not one of them that can be blamed on python, simply dont use weird third party libraries trying to second guess the asyncio architecture edit: ironically I'm the author of a weird third party library trying to second guess the asyncio architecture but mine is good https://awaitlet.sqlalchemy.org/en/latest/ (but I'll likely be retiring it in the coming year due to lack
100% same experience. If it were up to me, I'd started with typescript, but the client insisted on using a python stack (landed on FastMCP, FastAPI, PydanticAI). While, `PydanticAI` does the best it can with a limited type system, it just can't match the productivity of typescript. And I still can't believe what a mess async python is. The worst thing we've encountered was a bug from mixing anyio with asyncio which r
“We're using pydantic AI where the entire Agent loop is taken care of by the framework. Highly recommend.”