“• TypeScript-first, ergonomic API with excellent Next.js integration; streaming and tool calling are rock solid. • Consistent abstractions across multiple model providers (great with OpenRouter) minimize vendor lock-in and churn. • Clear docs and examples reduce boilerplate and accelerate iteration; fewer edge-case failures in production.”
AI SDK & Agent FrameworkMaker says so +1 · source ↗
AI SDK
Provider-agnostic TypeScript toolkit for streaming, tool calls and chat UIs.
5 makers' products we track use AI SDK. For AI SDK & agent framework it's 4th most chosen of 7 options: 5 of the 115 makers' products we know the AI SDK & agent framework of (4%). 241 open-source projects also declare it in their code. What makers like most: One TypeScript API across many model providers, so swapping models needs no code rewrite. Their most common complaint: Easy to drop in but hard to make resilient: no resumable streaming after a dropped connection and no multi-device support. On GitHub, 4 public pull requests moved projects to AI SDK from tools we list, and 3 moved them away.
Profile checked
How makers use AI SDK
Makers' products we track use AI SDK for AI SDK & agent framework (5).
What AI SDK is used for
AI SDK vs the alternatives makers chose
For AI SDK & agent framework, 5 of the 115 makers' products we know the choice of picked AI SDK (4%), behind LangChain (57%).
| Option | Makers' products | Open source | |
|---|---|---|---|
| 66 57% | Yes | ||
| 24 21% | Yes | Compare → | |
| 16 14% | Yes | ||
| 5 4% | Yes | ||
| 3 3% | Yes | ||
| 1 1% | Yes |
For AI SDK & agent framework: how many of the 115 makers' products we know the AI SDK & agent framework of chose each option.
When to use AI SDK, and when not
Pick AI SDK if
- Your app is TypeScript and you want agents without adding a Python service. AI SDK & Agent Framework →
Something else fits better if
- You want a small typed agent loop in Python, close to the raw API: Pydantic AI or OpenAI Agents SDK.
- Your agent works on files and runs commands, like a coding or research agent: Claude Agent SDK.
- You need many prebuilt connectors for models, tools and data sources: LangChain.
- Your agent is a long-running workflow with branches, saved state and human approval steps: LangGraph.
- The agent mostly retrieves and reasons over your own documents: LlamaIndex.
The AI SDK is Vercel's open-source TypeScript library for calling LLMs and building chat interfaces and agents on top of them. It puts one interface over the different provider APIs, so moving from one model vendor to another is a change of model, not a rewrite.
More about AI SDK
It has three parts. AI SDK Core has functions such as generateText and streamText, schema-checked structured output, tool calling, and a ToolLoopAgent class that runs the model-and-tools loop with stopping conditions. Providers are separate packages (@ai-sdk/openai, @ai-sdk/anthropic and many more) that implement a shared specification; a plain model string like anthropic/<model> goes through Vercel AI Gateway unless you set a different default provider. AI SDK UI has hooks (useChat, useCompletion, useObject) for React, Vue, Svelte, Angular and SolidJS. A third surface runs existing agent harnesses such as Claude Code and Codex. Core runs in Node.js and Deno as well as inside Next.js, Nuxt and SvelteKit.
The UI hooks handle streamed messages and loading and error state, and they read a documented stream protocol, so the backend can be written in another language, such as Python with FastAPI. Agents can connect to MCP servers over HTTP. It is a library with no hosted service required: it deploys wherever your JavaScript runs, and the Gateway is optional.
It is a toolkit, not a full agent platform: storing chat history is something you implement around useChat and streamText. The migration guides list four major versions, 4.0 through 7.0, and APIs prefixed experimental_ can change in any release.
How AI SDK itself is built
2 tools, from its own code, website and Product Hunt page.
AI SDK pros and cons
What makers like most: One TypeScript API across many model providers, so swapping models needs no code rewrite. Their most common complaint: Easy to drop in but hard to make resilient: no resumable streaming after a dropped connection and no multi-device support.
Pros
- One TypeScript API across many model providers, so swapping models needs no code rewrite. PHPH 2HN
- Streaming and tool calling are dependable, with tight Next.js and React integration. PHHNPH 2
- A well-written core that other agent libraries build on, with version-matched docs shipped in the package. HNHN 2HN 3HN 4
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
5.0★ from 5 reviews on Product Hunt ↗Reliability and open issues
The most wanted open issue on GitHub has 66 👍.
Most wanted on GitHub
- retry strategies and fallbacks👍 66 · opened Aug 2024 · active Jul 2026
- convert model messages to ui messages👍 24 · opened Jul 2025 · active Sep 2026
- Support tool call round trips in streamUI👍 21 · opened Jun 2024 · active Jul 2026
- openai responses `background` parameter👍 20 · opened Jun 2025 · active Jul 2026
- Programmatic access to the model capabilities and provider listings👍 18 · opened Jun 2024 · active Jul 2026
Who switches
More projects move to AI SDK: 4 pull requests in, 3 out; the most come from LangChain and leave for LangChain.
LangChain → AI SDK4 PRs
- server/llm: migrate from LangChain to Vercel AI SDKsagemathinc/cocalc · 2026-04-14
- Migrate LLM evaluation from LangChain to Vercel AI SDKsagemathinc/cocalc · 2026-04-10
- Migrate LangChain to Vercel AI SDKriccjohn/grimoire-oracle-web · 2026-03-02
- Migrate from LangChain to Vercel AI SDKliam-hq/liam · 2025-05-08
AI SDK → LangChain3 PRs
- Migrate from Vercel AI SDK to LangChain for chat infrastructurekarthicksakkaravarti/projectX · 2026-04-28
- refactor: migrate from Vercel AI SDK to LangChain + LangGraphjjinendra3/AceFrame · 2025-08-17
- Moving Backend LLM Integration to from Vercel AI SDK to LangChainwesfloyd/vibe-avs-builder · 2025-04-29
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.
Who uses it
5 makers' products, each linked to the source that shows it, and 241 open-source projects that declare it in their code. The best known on Product Hunt: onlook (1,089 followers), Quartr (573 followers), Fuser (487 followers), Sparks AI (204 followers), Zyntax IDE (55 followers).
“Used for multi-agent orchestration, state management, debugging, and structured artifact streaming for our AI application.”
AI SDK & Agent FrameworkMaker says so · source ↗“AI SDK made super simple to integrate all the different models into our app. Its the best sdk for build ai apps right now.”
AI SDK & Agent FrameworkMaker says so · source ↗“I liked it because its a unified TypeScript SDK for building AI apps. Helped building Zyntax Agent.”
AI SDK & Agent FrameworkMaker says so · source ↗None of these in makers' own words.
Open source: a project that declares AI SDK as a dependency in its public code — verifiable, but not necessarily a live product.
What its projects tell coding agents
122 of the 155 open-source products built with AI SDK that were worked on in the last 180 days keep instruction files for coding agents — 79%, against 53% of all the projects we read. AGENTS.md is in 102, CLAUDE.md in 74.
Alternatives to AI SDK
All alternatives by situation →Further reading
Questions makers ask about AI SDK
Is AI SDK good for production?
5 makers' products we track run on it. On GitHub, 4 public pull requests moved projects to AI SDK from tools we list, and 3 moved them away. The watch-out makers raise most: Easy to drop in but hard to make resilient: no resumable streaming after a dropped connection and no multi-device support.
What is AI SDK used for?
Provider-agnostic TypeScript toolkit for streaming, tool calls and chat UIs. Makers' products we track use it for AI SDK & agent framework (5).
What are the pros and cons of AI SDK?
Pros makers name: One TypeScript API across many model providers, so swapping models needs no code rewrite. Streaming and tool calling are dependable, with tight Next.js and React integration. A well-written core that other agent libraries build on, with version-matched docs shipped in the package. Cons: Easy to drop in but hard to make resilient: no resumable streaming after a dropped connection and no multi-device support. Streaming tool-call JSON is re-parsed on every chunk, which stalls on large payloads.
What are the alternatives to AI SDK?
For AI SDK & agent framework, the other options makers' products we track chose most are LangChain (66), Mastra (24), LlamaIndex (16), CrewAI (3), LangGraph (1). Open source or self-hostable among them: LangChain, Mastra, LlamaIndex, CrewAI, LangGraph. Each alternative, with the situation it fits, is on the AI SDK alternatives page.
Do developers switch to or away from AI SDK?
On GitHub, 4 public pull requests moved projects to AI SDK from tools we list, most from LangChain (4); 3 moved them away, most to LangChain (3).
When should you use AI SDK?
Your app is TypeScript and you want agents without adding a Python service (AI SDK & agent framework). Something else fits better if: you want a small typed agent loop in Python, close to the raw API, pick Pydantic AI or OpenAI Agents SDK; your agent works on files and runs commands, like a coding or research agent, pick Claude Agent SDK.
Does it work outside React and Next.js?
Yes. The UI hooks support React, Svelte, Vue.js, Angular and SolidJS, and AI SDK Core also runs in plain Node.js or Deno with no UI framework. source ↗
Can my backend be in Python?
Yes. useChat reads a documented stream protocol (Server-Sent Events with the x-vercel-ai-ui-message-stream: v1 header), so any backend that emits it works; the docs link a FastAPI example. source ↗
Do I need Vercel or the AI Gateway?
No. Plain model strings use Vercel AI Gateway as the default global provider, but you can set your own default, such as the OpenAI provider, or pass provider instances to call vendors directly. source ↗
Does it store chat history for me?
No. You write the load and save functions around useChat and streamText; the guide stores messages in files as an example and says to use a database in a real app. source ↗
Will upgrades break my code?
Breaking changes to stable APIs only come in major versions, which ship with migration guides and codemods where possible. APIs prefixed experimental_ can change in any release, so pin the exact version if you use them. source ↗
Can agents use tools from MCP servers?
Yes. The MCP client connects over HTTP (recommended for production), SSE or stdio, which is for local servers only, and gives the model the server's tools. source ↗
Is AI SDK free?
Yes — it is free, open-source software.
Is AI SDK open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with AI SDK?
No llms.txt, official MCP server or CLI found yet.
Who uses AI SDK?
5 makers' products we track, each with a source, and 241 open-source projects declare it in their code. The best known of them on Product Hunt: onlook (1,089 followers), Quartr (573 followers), Fuser (487 followers), Sparks AI (204 followers), Zyntax IDE (55 followers). source ↗