canonical: https://jentic.com/apis/vercel.com/vercel

# Vercel API

Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work. The API exposes 172 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically update an access group, reads an access group. Covers 172 operations with bearer, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Update an access group
- Reads an access group
- Deletes an access group
- List members of an access group
- Creates an access group

## Use cases

### Developer Tools Operations

Use the Vercel API to perform developer tools operations programmatically. The API provides 172 endpoints covering core functionality including update an access group, reads an access group, deletes an access group.

Example prompt: Call POST /v1/access-groups/{idOrName} to update an access group

### Automated Access Groups Management

Automate access groups operations by combining multiple Vercel API endpoints. Agents can reads an access group and then deletes an access group in a single workflow.

Example prompt: Call GET /v1/access-groups/{idOrName} to reads an access group, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Vercel API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Example prompt: Search Jentic for 'update an access group', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/access-groups/{idOrName} | Update an access group |
| GET | /v1/access-groups/{idOrName} | Reads an access group |
| DELETE | /v1/access-groups/{idOrName} | Deletes an access group |
| GET | /v1/access-groups/{idOrName}/members | List members of an access group |
| POST | /v1/access-groups | Creates an access group |
| GET | /v1/access-groups | List access groups for a team, project or member |
| GET | /v1/access-groups/{idOrName}/projects | List projects of an access group |
| POST | /v1/access-groups/{accessGroupIdOrName}/projects | Create an access group project |

## Key resources

- **Access Groups** — Operations for access groups
- **Aliases** — Operations for aliases
- **Certs** — Operations for certs
- **Data Cache** — Operations for data cache
- **Deployments** — Operations for deployments

## Why Jentic

- **Setup:** Wiring the Vercel API by hand means handling its bearer token or OAuth2 auth against api.vercel.com and coding each access group, member, and project operation yourself. Through Jentic you install once, import the Vercel API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Vercel puts the access group id or name in the URL path (/v1/access-groups/{idOrName}), so a rule can pin your agent to one access group. You choose the operations it may call, so destructive ones like deleting an access group are not included unless you add them.
- **Credential handling:** Your Vercel bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an access group' or 'list access group members', and Jentic returns the matching Vercel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Vercel API use?

The Vercel API uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I update an access group with the Vercel API?

Yes. Use the POST /v1/access-groups/{idOrName} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Vercel API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I update an access group through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update an access group'. Jentic returns the matching Vercel API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Vercel API have?

The Vercel API exposes 172 endpoints covering access groups, aliases, certs operations.

### Can I limit what my agent is allowed to do with the Vercel API?

Yes. Because you run Jentic One yourself, your own rules decide which Vercel operations and credentials the agent may use. Since the access group id or name lives in the URL path (/v1/access-groups/{idOrName}), you can pin the agent to a single access group and expose only the calls it needs, such as reading an access group or listing its members and projects. Destructive operations like DELETE /v1/access-groups/{idOrName} stay off limits unless you explicitly add them.