Developer tools
Vercel in your product and your AI agents, through one API
The Vercel toolkit covers the teams, projects, deployments and domains of a Vercel account: create and update projects, start, cancel and promote deployments, read build logs, and add and check project domains. Through Connect, your product or AI agent calls these operations with one endpoint, while Connect stores the token and logs every execution.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/vercel_create_project/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"name": "<name>"
}
}How it works
From a connected customer to the first Vercel call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Vercel account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Vercel.
Deploy sites for your users
Create a project linked to a Git repository, start a deployment, and follow it with Get deployment until its readyState changes.
Custom domains
Add a customer's domain to a project and read the DNS config to show the recommendedIPv4 or recommendedCNAME values to set.
Agent that fixes failed builds
An AI agent reads the build log of a failed deployment, finds the cause, and promotes an older deployment to roll production back.
Tools
13 Vercel tools
- List teamsGETLists the teams the account belongs to. Each item has id, the teamId that the other tools take, and slug. Only a Full Account token needs teamId: a token created for a team already acts on that team. Paginate passing pagination.next of the response as until.
- List projectsGETLists the projects of the account or of a team, with their settings, Git link and latest deployments. Each item has id and name, which the other tools take as the project. Paginate passing pagination.next of the response as from.
- Create projectPOSTCreates a project and returns it, with its id. With gitRepository, every push to the repository deploys automatically; the Vercel app of the Git provider must have access to the repository. Build settings left out are detected by Vercel.
- Update projectPATCHChanges the name or the build settings of a project and returns it. Only the fields sent change. The new settings apply from the next deployment.
- List deploymentsGETLists deployments, newest first, with state, target, url and Git metadata. Each item has uid, the id of the deployment. Paginate passing pagination.next of the response as until.
- Get deploymentGETReturns a deployment by its id or its url, with readyState, target, alias, projectId and, for a failed build, errorCode and errorMessage.
- Create deploymentPOSTStarts a deployment and returns it, with id, url and readyState. Send deploymentId to redeploy an existing deployment, or gitSource to deploy a branch or commit of the connected repository. Without target it is a preview; production makes it the production deployment. The build takes minutes: follow it with Get deployment.
- Cancel deploymentPATCHStops a deployment that is still queued or building, and returns it with readyState CANCELED.
- Promote deploymentPOSTPoints the production domains of a project to an existing deployment, without building it again, such as to roll production back to an older production deployment. To put a preview in production with a new build, use Create deployment with its deploymentId and target production. Answers 201 or 202 when accepted.
- List deployment eventsGETReturns the build log of a deployment as a list of events, each with type (such as stdout, stderr or command), created and the text of the line. Use it to see why a build failed.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
Questions about the Vercel toolkit
Do I need to build against the Vercel API?
No. Connect ships 13 Vercel tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Vercel account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
