v0 Introducing the new v0 API

Today we're introducing the new v0 API: programmatic, headless access to v0's app-building agent. Send a prompt and v0 generates an app, starts a dev server in a Vercel Sandbox, and gives you a preview URL you can embed in your own UI.

Each chat is an isolated workspace for one app, where v0 can read, edit, and run the files. Follow-up messages continue from the current state. v0 verifies the code running in the Sandbox, so it can catch and fix errors in your app in real time.

The new API is now generally available.

How it works

Create a chat from a prompt, stream its work, and render the live preview, all from your own interface. First, install the v0 SDK.

Then, create a chat. Send a prompt, and v0 generates your app.

Send follow-up messages to the same chat to keep building. Each one continues from the current state.

Then embed the app.

A prompt goes in, a running app comes out. v0 operates the Sandbox, dev server, and preview behind it. When you're ready, deploy to Vercel in one API call. v0 manages the whole pipeline.

What this unlocks

The new API lets you run v0's app builder inside your own product or pipeline. This opens use cases like:

• A white-labeled app builder: Your users describe an app and get one back.

• Automated app changes: Trigger v0 from a script, CI job, or webhook to generate a new app or update an existing one.

• A build tool for your agents: An agent hands back a working app instead of a code snippet.

Below, we break down the API primitives behind this workflow.

Start with a chat

Each chat holds the state for one app, and a repo or Vercel project can have many. Keep each chat's ID and send its follow-up messages to that chat. Metadata lets you group chats by customer, workspace, app, or any key you already use.

Learn more about messages.

Stream the trace

Your interface needs to show what happens between sending a request and seeing the updated preview.

Every message includes ordered parts: text, thinking, file reads and edits, searches, bash commands, tool calls, and agent actions. The same object can drive a one-line status, a changed-files view, or the full trace.

Usage is returned with chat and message responses, so you can account for the work when it finishes.

Choose sync, async, or streaming

Chat creation and messages support synchronous, asynchronous, and streaming responses. Use sync when the caller needs the completed response. Use async to queue the work and receive updates via webhook or poll for v0's response later. Stream the request to render v0's work as it happens.

Work from existing code

You can also create a chat from a repository, ZIP archive, or set of files.

Render the dev server preview

Each chat gets a short-lived preview token. Fetch it from a server route and proxy browser requests through it, so your v0 API key never reaches the browser. When a preview is ready, traffic forwards to it; while the Sandbox spins up, requests fall back to a loading route. Point an iframe at your proxy route and cache the preview details until they expire.

Read more about Accessing Previews in the docs.

Bring your own tools and design systems

Turn on specific MCP servers for a chat, or use the defaults.

Design Systems 2.0 saves a design system as a skill. Include it in a request to load its components, tokens, setup, and starter app.

You can pass up to three skills per request, from team or user memory, skills.sh, or the connected repo, or let the agent pull them in for you.

Use v0 from agents

If you're building an agent, give it v0 as a tool. When the agent needs to produce a working app, it calls v0, and gets back a running preview or deployment to hand to the user. Your agent stays in charge of everything else.

There are three ways to connect it:

MCP

Connect the v0 MCP server to an IDE, desktop assistant, or agent runtime that supports MCP.

The first connection starts an OAuth flow. The MCP server exposes tools for creating chats, listing chats, getting chat details, listing and sending messages, resolving pending tasks, and getting preview URLs.

AI SDK

For TypeScript agents built with AI SDK, use @v0-sdk/ai-tools to expose v0's API operations as tools in the agent's own loop.

The agent decides when to create or continue a chat. Your AI SDK run keeps control of the orchestration and final response.

eve

For eve agents, add an OpenAPI connection file. eve turns the allowed operations into tools and attaches the API key at execution time, out of model context.

Connect a Vercel project

Create a Vercel project for the chat, then manage its environment variables, integrations, and settings through the Vercel API. Your apps get Vercel's security and observability by default.

When you're ready to ship, deploy the chat to Vercel.

Migrate your chats

Chats from the previous version of the v0 API don’t run on the new one, so carry them forward. Pick the version you want to keep, download it as a ZIP, and create a new chat from that ZIP. Store the old identifiers in the new chat’s metadata if you need traceability.

The migration guide covers the full mapping. The main changes:

• Use https://api.v0.dev/v2 for new requests.

• The chat holds current app state, and messages hold its history.

• Replace version workflows with chat file workflows, and v0 Project organization with chat metadata.

• Use vercelProjectId plus the Vercel API for project operations.

• Render message parts, not only final text.

Get started

Create an API key in v0 settings and install the SDK.

Or, scaffold a full app.

Read the documentation and migration guide.

Read more