Sanaf AI
Start free
Developer Tools

Vercel, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Vercel account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Signs in to your account
  • 35 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Vercel is

Vercel is a platform for frontend frameworks and static sites, enabling developers to host websites and web services that deploy instantly, scale automatically, and require minimal configuration.

You sign in with your own Vercel account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Vercel.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Vercel. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Vercel account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

35 tools it already has

What it can do in Vercel

These are the ready-made tools your AI employee already has in Vercel. It is not limited to them, but it never has to be taught these.

  • Add Environment VariableTool to add an environment variable to a vercel project. use after confirming the project exists and you need to configure secrets or configuration values across environments befor
  • Check Cache Artifact ExistsTool to check if a cache artifact exists by its hash. use when verifying whether a cache artifact is already stored before upload.
  • Check Domain AvailabilityTool to check if a domain is available for registration. use when you need to verify domain availability before purchase.
  • Check Domain PriceTool to check the price for a domain before purchase. use when evaluating cost and availability prior to domain registration.
  • Create Auth TokenTool to create a new authentication token. use when you need to programmatically generate a new token after validating permissions. example: "create auth token named my-token"
  • Create Edge ConfigTool to create a new edge config for a vercel project. use when you need to define edge caching settings before deploying your project across a specified repository.
  • Create Edge Config TokenTool to create a new token for a specific edge config. use when you need a read-only access token after provisioning your edge config.
  • Create new deploymentTool to create a new deployment. use when you need to deploy files or a git commit to a vercel project.
  • Delete Auth TokenTool to delete an authentication token. use when you need to revoke a token programmatically after confirming its validity. example: "delete auth token with id abc123"
  • Delete DeploymentTool to delete a specific deployment by its unique id. use after confirming the deployment identifier to clean up unused or failed deployments.
  • Delete Edge Config TokensTool to delete tokens associated with a specific edge config. use when you need to revoke one or more access tokens from an existing edge config by its id.
  • Delete Environment VariableTool to delete a specific environment variable from a project. use after verifying the correct variable id to remove it.
  • Delete Vercel ProjectTool to delete a specific project by its id or name. use after confirming the correct project id or name to permanently remove it.
  • Deploy Edge FunctionDeploy edge functions to vercel. use when you need to deploy serverless functions that run on the edge runtime with fast cold starts and global distribution.
  • Get Auth Token MetadataTool to retrieve metadata for an authentication token. use when you need to inspect details of a specific token for auditing or debugging.
  • Get deployment detailsTool to retrieve detailed information about a specific deployment. use after triggering a deployment and you need to inspect its status and configuration. example: "get details for
  • Get Deployment EventsTool to retrieve events related to a specific deployment. use when monitoring or debugging deployment history or streaming real-time events. example: "get events for deployment dpl
  • Get Deployment LogsTool to retrieve logs for a specific vercel deployment. use when monitoring deployment execution, debugging issues, or analyzing deployment performance. example: "get logs for depl
  • Get Domain Transfer InfoTool to get information required to transfer a domain to vercel. use when you need to check transfer availability or current status before initiating a transfer.
  • Get Edge ConfigTool to retrieve details of a specific edge config. use when you need to inspect edge config metadata by id before updating or deleting.
  • Get Edge Config ItemTool to retrieve a specific item within an edge config. use after obtaining the edge config id and when you need to inspect or validate a particular configuration item by its key.
  • Get Edge Config TokenTool to retrieve details of a specific token associated with an edge config. use when you need metadata for an existing edge config token.
  • Get Vercel ProjectTool to retrieve information about a vercel project by id or name. use when you need project metadata after obtaining its identifier.
  • List All DeploymentsTool to list all deployments. use after authenticating to retrieve deployments under your user or team context. example: "list deployments for project qmx...".
  • List All TeamsTool to list all teams accessible to the authenticated user. use after authentication to retrieve their ids and slugs.
  • List Auth TokensTool to list authentication tokens. use when you need to retrieve all tokens for the current user or an optional team.
  • List Deployment ChecksTool to retrieve a list of checks for a specific deployment. use after a deployment to inspect check statuses and results.
  • List Edge Config ItemsTool to retrieve a list of items within a specific edge config. use when you need to inspect or manage all key–value items after creating an edge config.
  • List Edge Config TokensTool to retrieve a list of tokens for a specific edge config. use after obtaining an edge config's id to list its tokens.
  • List Edge ConfigsTool to list all edge configs. use when you need to enumerate all edge config definitions for your account or team.
  • List Environment VariablesTool to list environment variables for a specific project. use when you need to inspect or page through the environment settings before deployment.
  • List Vercel AliasesTool to list all aliases for the authenticated user or team. use when you need to retrieve aliases filtered by various criteria.
  • Update Edge ConfigTool to update an existing edge config. use when you need to rename the slug of an edge config for reorganization or migration purposes. only the slug field may be updated; ensure
  • Update Edge Config ItemsTool to update items within a specific edge config. use when you need to batch modify, add, or remove key-value pairs in an existing edge config.
  • Update Vercel ProjectTool to update an existing project. use when you need to modify a vercel project’s configuration before deployment. use after confirming the project id or name.
Access, and who is in charge of it

You stay the boss of your Vercel account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Vercel account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Vercel is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Vercel and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Vercel

Can an AI employee really work inside Vercel?
Yes. It signs in to your own Vercel account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Vercel?
No. Nothing moves and nothing is replaced. Your records stay in Vercel, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Vercel account?
You sign in with your own Vercel account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Vercel?
It has 35 ready-made tools in Vercel today, among them Add Environment Variable, Check Cache Artifact Exists and Check Domain Availability. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Vercel and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Vercel and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Vercel?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Vercel is written down with what it did and when.