{
  "schema_version": "1.1",
  "id": "s4:https://vercel.com/blog/introducing-the-new-v0-api",
  "slug": "introducing-the-new-v0-api-1rprgj9",
  "url": "https://feed7.dev/p/introducing-the-new-v0-api-1rprgj9",
  "title": "Introducing the new v0 API",
  "why_included": "The generally available v0 API gives agents headless app generation with stateful chats, sandboxed execution, streamed traces, live previews, and one-call Vercel deployment.",
  "summary": "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.",
  "practical_implication": "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.",
  "agent_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.\n\nTreat 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.\n\nChats 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.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/blog/introducing-the-new-v0-api",
    "published_at": "2026-08-05T04:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "tools",
  "domains": [
    "coding"
  ],
  "topics": [
    "cloud-agents",
    "coding-agents",
    "agent-sdks"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "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."
  ],
  "connected_context": {
    "meaning": "This makes v0 a headless, stateful app-building component rather than another general coding-agent runtime: the host application owns chat-to-app identity, ordered UI rendering, preview proxying, and migration boundaries while v0 owns an isolated executable workspace. It strengthens the embedded-agent pattern but narrows it to app generation, with server-side key handling and expiring preview access as integration requirements.",
    "corpus_size": 368,
    "generated_at": "2026-08-06T10:04:21.917Z",
    "connections": [
      {
        "title": "How Notion used the Cursor SDK to embed coding agents",
        "source_name": "Cursor",
        "source_url": "https://cursor.com/blog/notion",
        "feed7_url": "https://feed7.dev/p/notion-07d02so",
        "reason": "Both support embedding coding work inside another product, but v0 supplies an app-specific stateful workspace and live preview rather than the issue-to-PR workflow described by Notion."
      },
      {
        "title": "github/copilot-sdk",
        "source_name": "GitHub",
        "source_url": "https://github.com/github/copilot-sdk",
        "feed7_url": "https://feed7.dev/p/copilot-sdk-0vwjjou",
        "reason": "Copilot SDK exposes a configurable general agent runtime, while v0 offers a more bounded app-building service whose host must manage chat identity, previews, and migration."
      },
      {
        "title": "Run Claude Managed Agents with Chat SDK",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/claude-managed-agents-with-chat-sdk",
        "feed7_url": "https://feed7.dev/p/claude-managed-agents-with-chat-sdk-0wtme2i",
        "reason": "Both retain execution state in a hosted agent service, but v0 adds an isolated runnable app workspace and preview while requiring the integrating application to proxy that preview."
      },
      {
        "title": "Vercel Plugin now available in VS Code and GitHub Copilot CLI",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/vercel-plugin-now-available-in-vs-code-and-github-copilot-cli",
        "feed7_url": "https://feed7.dev/p/vercel-plugin-now-available-in-vs-code-and-github-copilot-cli-11mhomy",
        "reason": "The plugin supplies Vercel guidance to external coding agents; v0 instead accepts up to three skills as request-time context within its own app-building workspace."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-08-05T04:00:00.000Z",
  "modified_at": "2026-08-05T04:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/introducing-the-new-v0-api-1rprgj9",
    "json": "https://feed7.dev/p/introducing-the-new-v0-api-1rprgj9.json",
    "markdown": "https://feed7.dev/p/introducing-the-new-v0-api-1rprgj9.md"
  }
}