v0
v0 is Vercel's AI-powered application builder. The v0 Platform API exposes the same chat, project, deployment, and code-generation primitives that power the v0 web product so AI tools, IDEs, and pipelines can drive v0 programmatically. An OpenAPI 3.1 spec is published at https://api.v0.app/openapi.json and a v0-sdk package is available for TypeScript.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles v0 the way a machine reads it — 31 machine-readable artifacts across 23 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — v0 scores 41.5/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile v0
Each block below is one kind of artifact we hold for v0. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 23
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
v0 agent API
The agent API from v0 — 1 operation(s) for agent.
v0 blankProject API
The blankProject API from v0 — 1 operation(s) for blankproject.
v0 chats API
Chats
v0 chatScreenshots API
The chatScreenshots API from v0 — 1 operation(s) for chatscreenshots.
v0 deployments API
The deployments API from v0 — 4 operation(s) for deployments.
v0 feedback API
The feedback API from v0 — 1 operation(s) for feedback.
v0 git API
The git API from v0 — 8 operation(s) for git.
v0 hooks API
The hooks API from v0 — 2 operation(s) for hooks.
v0 iap API
The iap API from v0 — 1 operation(s) for iap.
v0 integrations API
The integrations API from v0 — 4 operation(s) for integrations.
v0 magicLink API
The magicLink API from v0 — 1 operation(s) for magiclink.
v0 mcpServers API
The mcpServers API from v0 — 3 operation(s) for mcpservers.
v0 nativeVersion API
The nativeVersion API from v0 — 1 operation(s) for nativeversion.
v0 notifications API
The notifications API from v0 — 3 operation(s) for notifications.
v0 plans API
The plans API from v0 — 1 operation(s) for plans.
v0 products API
The products API from v0 — 1 operation(s) for products.
v0 projects API
The projects API from v0 — 9 operation(s) for projects.
v0 promptTemplates API
The promptTemplates API from v0 — 1 operation(s) for prompttemplates.
v0 rateLimits API
The rateLimits API from v0 — 1 operation(s) for ratelimits.
v0 reports API
The reports API from v0 — 2 operation(s) for reports.
v0 search API
The search API from v0 — 1 operation(s) for search.
v0 terms API
The terms API from v0 — 2 operation(s) for terms.
v0 user API
The user API from v0 — 8 operation(s) for user.
Scroll within the panel for all 23 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
v0 App API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
V0 Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
V0 Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
V0 Finops
FINOPSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for v0 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/v0 · machine-readable index on apis.io