Agent report card
Can an agent use Vercel REST API through Deployment operations?
Grade B: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Vercel / active
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayReady
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
Applicable terms are stable, readable, retrievable, and materially complete.
Eligibility conditions and required inputs are explicit and decidable.
Price or no-charge status, variables, currency, and material conditions are explicit.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshEligibility conditions and required inputs are explicit and decidable.
Vercel's Terms of Service explicitly state age and eligibility conditions, requiring users to be at least 16 years of age and to use or access services through an electronic device controlled by the user.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
Vercel's pricing page discloses plan options including Hobby ($0/mo) and Pro ($20/mo), with explicit usage rates, included credits, variable resource limits, and currency in USD.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
The Vercel REST API documentation explicitly provides the service details, HTTP/1 and HTTP/2 SSL architecture support, and the base entrypoint URL at https://api.vercel.com.
Are verified structured discovery artifacts available?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
Vercel's Terms of Service agreement is retrievable, readable, and materially complete, covering applicable terms, schedule additions, and commitments for using Vercel's Services.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
A stable canonical route begins the required access bootstrap.
Evidence and actions5 signals
Can an agent operate the access controls and safe handoffs deterministically?
supported: freshCurrent admissible evidence does not resolve this finding.
The sign-up page displays options to continue with Google, GitHub, ChatGPT, Apple, or Email. Current admissible evidence does not resolve whether the access controls, navigation, and handoffs are fully machine-operable.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable sign-up page at https://vercel.com/signup presents options to continue with third-party providers or email to begin service access.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The captured sign-up pages display third-party login and email authentication options. Admissible evidence does not explicitly establish whether CAPTCHA challenges are present or if a supported alternative exists.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Vercel API access tokens can be created in personal account settings or via the CLI and scoped to user accounts, teams, or single projects. However, newly created tokens are shown in plaintext only once and require manual copying and storage into secret managers or environment variables.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The sign-up capture presents third-party and email login options, but current admissible evidence does not explicitly document whether phone verification is required, absent, or supported through a resumable boundary.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
A documented direct purchase path reaches paid access without a vendor decision point.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence describes Pro plan checkout domain claims and payment method settings, but does not document an API, protocol, or web flow for deterministic checkout construction, approval handoff, and resumption.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Vercel discloses that the Pro plan payments are billed at the beginning of each billing cycle in USD (if converted by the card provider) via Credit/Debit card.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The documentation mentions automatic credit card charges upon invoice issuance and adding new cards in billing settings, but does not document scoped delegation rails or human-confirmed payment authorization protocols with receipts.
Is a direct self-service path to paid access documented?
supported: freshA documented direct purchase path reaches paid access without a vendor decision point.
A direct self-service upgrade path is documented where new subscriptions can claim a domain at checkout during the upgrade or add a payment method via team settings under Billing.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshDelivery needs additional human transfer or has weak scope or lifecycle semantics.
Tokens can be created via the account settings page or using the `vercel tokens` CLI command. The CLI displays the plaintext token value only once upon creation, requiring manual copy and storage in a secret manager or environment variable.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshCompletion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Deployment creation returns an object and exposes pollable progress and terminal states, but the retained evidence does not establish a documented completion bound.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Deployment provisioning can be programmatically initiated via the Vercel REST API endpoint `POST https://api.vercel.com/v13/deployments` by passing an access token in the Authorization header along with deployment file configuration in the JSON request body.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
- Expose bounded machine-readable terminal status and reconciliation semantics.
Safe failure handling is documented only partially.
Only part of the credential lifecycle is agent-operable.
Every essential target has a stable documented agent-usable interface alternative.
Request-time authentication is documented and usable under scoped agent authority.
Essential operations have stable readable request, response, and effect semantics.
Evidence and actions6 signals
Is an agent-native protocol interface verified against the essential targets?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
First-party documentation states that Vercel access tokens can be created inside account settings or via the Vercel CLI (`vercel tokens add`), listed, and revoked/removed using `vercel tokens rm <token-id>`. However, evidence does not document full agent-executable automated credential rotation, compromise handling, or recovery semantics.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Documentation establishes generic error responses (such as `forbidden`, `rate_limited`, `bad_request`, `internal_server_error`, and `not_found`) along with rate limit headers and error payloads. However, safe failure handling semantics such as explicit request idempotency, retry procedures, cancellation, and reconciliation are not fully documented in the evidence.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Request-time authentication is documented using Vercel Access Tokens passed via the `Authorization: Bearer TOKEN` HTTP header, which can be scoped to personal accounts, specific teams, or individual projects.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Essential endpoints and error payloads are documented across all evaluated targets. For instance, creating a deployment via POST to `/v13/deployments` specifies HTTP methods, query parameters (`teamId`, `forceNew`), JSON body fields (`files`, `deploymentId`, `customEnvironmentSlugOrId`), response structures (`id`, `readyState`, `target`), and state transition flow (`QUEUED` → `INITIALIZING` → `BUILDING` → `READY`/`ERROR`).
- deployment-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Every essential target is accessible through agent-usable machine interfaces, specifically the Vercel REST API (`https://api.vercel.com`) and the Vercel CLI.
- deployment-api
What would improve this stage
- Document applicable structured errors, retry, cancellation, and reconciliation semantics.
- Provide scoped expiry, rotation, revocation, compromise, and recovery operations.
What works
- Evaluate: The exact service and stable evaluation or access entrypoints are publicly discoverable.
- Pay: Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
What blocks agents
- Sign up: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
Startup offers
Vercel on the startup-offers board
- Up to $30,000 in creditsVercel for Startups
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xn2p7wd9g3a5rt8zq6
- Projection
- sha256:44ea9638480511a23bf110de9baf35b88bb621719ddc9c07103de5eee9bffff1
- Policy
- service-use-2026-08-20-public-evidence-r9 · sha256:57bf95fd6d0fe6fe9173a68b60e8d8dc2179b357c88ff4349675a72d0e1d4139
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration