Developer ToolsProject Managementbearer, oauth2172 EndpointsREST
For Agents
Programmatically update an access group, reads an access group. Covers 172 operations with bearer, oauth2 authentication.
Use for: I need to an access group, I want to reads an access group, Search for deletes an access group, Find all members of an access group
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
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.
Install Jentic One Beta
Connect the Vercel API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vercel API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvercel.com%2Fvercel" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvercel.com%2Fvercel" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Vercel API.
Update an access group
Reads an access group
Deletes an access group
List members of an access group
Creates an access group
Use Cases
Patterns agents use Vercel API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'update an access group', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
172 endpoints — vercel combines the best developer experience with an obsessive focus on end-user performance.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
V
Vercel API
- Non-Ready (C-)51/100
39
Foundational Compliance62
Developer Experience & Jentic Compatibility41
AI-Readiness & Agent Experience55
Agent Usability75
Security69
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
39
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
57%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
7%
Example Density
How richly the API is illustrated with examples.
96%
Example Validity
Percentage of examples that conform to their schemas.
53%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
41
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
24%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
86%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
56%
Summary Coverage
Coverage of summaries across operations/tags/info.
55
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: CSignals: 1
55%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
69
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
69%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Vercel API through Jentic.
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.
GET STARTED