← Atlas · Topics: agents-and-prompts, components, landing-pages

v0

Site

v0.app

Type

ai builder

Verdict

Very useful

Licence

Conditional licence, proprietary paidproprietary-paidCredit-based. Free includes $5 of monthly credits and 7 messages a day. Plus is $30 per user per month (shown discounted from $90 at review) with $30 of credits plus $2 daily, Business is $100 per user per month with training opt-out by default, and Enterprise is custom. Usage is billed per million tokens by model tier. The service is proprietary; the v0-sdk package is Apache-2.0

Agent channels

mcp, llms-txt, api

Pricing

freemium

Reviewed

2026-09-25

What it is

v0 is Vercel's prompt-to-app builder. You describe a screen or product and its agent writes a working project, by default in Next.js, React, TypeScript, Tailwind CSS and shadcn/ui, with a live preview that runs server code, API routes and databases as they would run in production. You can refine it by chat or with Design Mode for visual edits, sync it to GitHub branches and pull requests, and publish it to Vercel. It also imports existing repos, zip files and Figma frames. Four model tiers (Mini, Pro, Max, Max Fast) trade speed for capability.

When to open it

Open it to get a first working version of a dashboard, landing page or component in shadcn/ui style, then carry the code into your own repo. It is strongest when your stack already matches its defaults, and when a design system is already set up so output stays on-brand.

Most useful

• Design Systems 2.0: teach v0 your components, tokens and conventions once from a package, repo, reference app, Storybook or Figma frames. The result is saved as a skill for the team or workspace
• shadcn/ui registries: the older route, a custom registry built from Vercel's registry starter template, still passes components and tokens to v0
• GitHub sync: branches, commits and pull requests are created from the chat, so work can be reviewed like any other code
• MCP out: attach your own MCP servers or Vercel Marketplace integrations to a chat for data and APIs
• Templates from the community to fork as starting points

Using it with agents

v0 is easy for agents to reach. Its remote MCP server at https://v0.app/api/mcp uses OAuth through npx mcp-remote, needs no API key, and lets an IDE agent create chats, answer v0's plan approvals and fetch preview URLs. The Platform API (v2 is current) and the Apache-2.0 v0-sdk package, downloaded about 125,000 times a month at review, let you build v0 into your own tools with an API key. For reading, /docs/agents.md describes the documentation surfaces, /docs/llms.txt contains the whole documentation as Markdown (about 1.3 MB), and any docs page can be fetched with .md added. The root v0.app/llms.txt returned the app's HTML at review, so use the docs paths.

Watch out for

• Under Vercel's terms, content from Hobby or trial accounts may be used for model training and shared with third parties unless you opt out. Business and Enterprise are opted out by default
• Token billing makes costs hard to predict. Long projects send large contexts, so short prompts can still use a lot of input tokens
• The best results come on Next.js with Vercel hosting. Code can be exported and deployed elsewhere, but some integrations assume Vercel
• Generated code needs human review for bugs and licensing, as Vercel's AI policy itself says
• Without a design system, output tends toward the default shadcn look

Reusable ideas

• Treat a design system as an installable package plus a short adapter skill, rather than pasting docs into every prompt
• Pause the agent for plan approval and let an outside agent answer it through MCP, so tools can hand work to each other
• Publish an agents.md that tells agents which docs surfaces exist and not to assume undocumented APIs
• Run previews on the production runtime, so what the user approves is what ships

Related

shadcn/ui, 21st.dev, shadcnblocks, Screenshot to Code, Kombai, Figma