Introducing the new v0 API
The generally available v0 API gives agents headless app generation with stateful chats, sandboxed execution, streamed traces, live previews, and one-call Vercel deployment.
The **v0 API is generally available** for headless app building. Each chat is an isolated, stateful app workspace that can edit and run files in a Vercel Sandbox, expose a live preview, and accept follow-up changes through sync, async, or streaming calls.
Treat v0 as a bounded app-building tool inside a larger agent loop: retain one chat ID per app, stream ordered work parts into your UI, and proxy preview traffic server-side. Existing repos, ZIPs, or files can seed a chat, and up to **three skills per request** can supply design-system context.
The **v0 API is generally available** for headless app building. Each chat is an isolated, stateful app workspace that can edit and run files in a Vercel Sandbox, expose a live preview, and accept follow-up changes through sync, async, or streaming calls. Treat v0 as a bounded app-building tool inside a larger agent loop: retain one chat ID per app, stream ordered work parts into your UI, and proxy preview traffic server-side. Existing repos, ZIPs, or files can seed a chat, and up to **three skills per request** can supply design-system context. Chats from the previous API do not run on the new version; migration requires exporting a chosen version as a ZIP and creating a new chat from it. Preview tokens are short-lived, and API keys must stay behind the server proxy.
This adds a specialized, headless app-building runtime to the embedded-agent landscape: the API owns a stateful sandbox, file editing, execution, previews, and iterative changes, while the host product owns orchestration, UI consumption, and secure preview proxying. Its bounded workspace reduces runtime assembly but introduces chat-state, token, migration, and platform-dependency constraints.