Integrations · v0
Guild agents use v0, Vercel’s app builder, to turn a prompt or existing code into a working web app. The agent starts a v0 chat, sends follow-up messages to iterate, and deploys the result. Guild stores your v0 API key and injects it server-side, so agent code never sees it.
Book a demo
See how teams govern agents that use v0.
Talk to sales
Get access to Guild, then connect v0 to your first agent.
What the v0 integration exposes
The integration isguildai~v0, and it calls the v0 Platform API at https://api.v0.dev. It has seven tools:
v0_v0_create_chatsstarts a chat from a prompt.v0_v0_init_chatsstarts a chat from existing files or a repository.v0_v0_send_message_chatssends a follow-up message to iterate.v0_v0_get_chatsreads a chat and its latest version.v0_v0_projects_createandv0_v0_projects_findcreate and look up projects.v0_v0_deployments_createdeploys a chat version.
How it works
1
Create a v0 API key
Sign in to v0 with your Vercel account, open API keys, and create a key. It starts with
v0_, and v0 shows it only once.2
Connect the key in Guild
Go to Access & setup > Credentials, click Connect, select v0, and paste the key into API Key.
3
Import the tools
Import
V0Tools from @guildai-services/guildai~v0 and add them to the agent’s tools.Why v0 access needs governing
Generating apps spends v0 credits, and a deployment puts code on a public URL. Guild keeps the key server-side and checks every request against your credential policies, so an agent can draft apps while a DENY rule onv0_v0_deployments_create keeps it from shipping them.
Authentication
- Type: API key
- Header: Guild sends the key as
Authorization: Bearer <key>
Usage
Tools
Tools in the latest published version ofguildai~v0:
Frequently asked questions
Why do the tool names start with v0_v0_?
Why do the tool names start with v0_v0_?
Every tool name starts with the integration name,
v0_, followed by the operation ID, and v0’s operation IDs start with v0 too.Can the agent push v0's code to GitHub?
Can the agent push v0's code to GitHub?
Not through these tools. Pair v0 with the GitHub integration and have the agent commit the files it reads from the chat.
Can I let an agent generate apps but not deploy them?
Can I let an agent generate apps but not deploy them?
Yes. Write a credential policy that denies
v0_v0_deployments_create. See Credential policies.