Vercel's v0 API v2 Lets AI Agents Build and Ship Apps Without Humans
v0's new API v2 lets you embed its full app-building agent — prompt, preview, iterate, deploy — directly into your own products and pipelines
- v0 API v2 is now in public beta, giving programmatic access to v0's full app-building agent: prompt, preview, iterate, and deploy to Vercel.
- VMs replace the old browser-based runtime, enabling richer file operations, real dev server previews, and a direct path to Vercel deployments.
- Three execution modes (sync, async, streaming) are now explicit separate endpoints, making it easier to build interactive UIs or background pipelines.
- Chats can be seeded from a prompt, a GitHub repo, or a ZIP archive, and the API supports follow-up messages for iterative generation.
- API access requires the Premium plan ($20/mo) or higher; usage is credit-based and tied to token consumption per generation call.
- MCP integration lets the API connect to Stripe, Supabase, Neon, Shopify, and more without bespoke connectors — full docs here.
v0 API v2 is now in public beta, and it's a meaningful step beyond what the original Platform API offered. Where v1 gave you a REST endpoint that turned prompts into code files, v2 gives you the full agent: a VM-backed chat that can start from a prompt, a GitHub repo, or a ZIP archive, render a live dev server preview, accept follow-up messages, and deploy straight to Vercel , all programmatically.
From chat interface to headless app builder
The v0 API gives your product v0's app-building agent, including code generation, secure live previews, integrations, and deployment to Vercel. The key shift in v2 is that the underlying runtime changed entirely. Vercel had already shifted v0 toward production readiness with a sandbox-based runtime mirroring real environments, native GitHub integration for branches and PRs, support for API routes, server actions, and database connections, and the ability to import and work on existing codebases. The API v2 exposes all of that programmatically.
The Platform API v2 beta lets you start v0 chats from GitHub repos programmatically , a clear signal that Vercel wants v0 embedded into CI/CD pipelines and internal tooling, not just used interactively.
What actually changed from v1
The v1 API was organized around projects and versions. v2 throws that model out. In v2, the chat is the durable workspace. Messages are the history of what happened. This means you no longer need to choose between chat IDs, project IDs, and version IDs for common workflows. Most operations now come down to operating on the chat itself, or interacting with it through messages.
The other big architectural change: v2 chats run on VMs. VMs are more capable than the old browser-based next-lite runtime used in v1: they can run a fuller project environment, support richer file operations, and provide a more direct path to Vercel projects, previews, and deployments.