Agent report card
Can an agent use Vercel REST API through Deployment operations?
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.
The Vercel REST API is publicly discoverable and hosted at the stable base entrypoint URL https://api.vercel.com.
Structured discovery exists but covers only part of the evaluation surface.
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 state explicit eligibility conditions, requiring users to be at least 16 years of age, have electronic devices controlled by them, and possess legal authority to bind a company or legal entity when entering into the agreement on its behalf.
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 discloses its pricing tiers, including a $0/month Hobby plan and a $20/month Pro plan (which includes $20 of usage credit). Prices are stated in USD and exclude applicable taxes calculated based on billing address.
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 is publicly discoverable and hosted at the stable base entrypoint URL https://api.vercel.com.
Are verified structured discovery artifacts available?
supported: freshStructured discovery exists but covers only part of the evaluation surface.
Vercel changelog text notes automatic REST API documentation with OpenAPI, but the retained text does not provide a verified schema artifact for the complete evaluation surface.
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 are stable, readable, retrievable online, and materially complete, covering age eligibility, license terms, payment terms, and service API conditions.
Does the vendor deliberately describe access for web agents?
supported: freshCurrent admissible evidence does not resolve this finding.
Standard metadata directives appear, but retained admissible evidence does not establish an explicit web-agent or robot access policy for the assessed API documentation surface.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Vercel Access Tokens can be created in account settings or via Vercel CLI (`vercel tokens add`) and scoped to specific teams or projects, but initial creation relies on manual dashboard UI interaction or copying the secret.
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 signup page displays social login options and email entry, but does not provide complete evidence of deterministic validation, navigation, and handoffs.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Vercel's signup page provides a canonical entrypoint to begin account registration via OAuth providers and email.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The signup page captures do not contain an explicit declaration or verified-agent alternative regarding CAPTCHA boundaries across the signup flow.
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 Access Tokens can be created in account settings or via Vercel CLI (`vercel tokens add`) and scoped to specific teams or projects, but initial creation relies on manual dashboard UI interaction or copying the secret.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The initial signup screen does not state whether phone verification is required, absent, or explicitly resumable.
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.
The evidence discloses payment timing at the start of each billing cycle, card payment methods, and USD currency charging conditions.
An API, protocol, or accessible web flow supports deterministic checkout and resumption.
A documented rail supports scoped delegation or explicit human-confirmed authorization with receipts.
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: freshAn API, protocol, or accessible web flow supports deterministic checkout and resumption.
POST /v1/billing/buy lets an agent construct a credit purchase with a bearer token and returns a checkoutSessionId and checkoutSessionUrl, so approval can be handed to a person at the URL and the session resumed by id.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
The evidence discloses payment timing at the start of each billing cycle, card payment methods, and USD currency charging conditions.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshA documented rail supports scoped delegation or explicit human-confirmed authorization with receipts.
Credit purchases through POST /v1/billing/buy charge the payment method on file immediately and are limited to Owner, Member, Developer, Security and Billing roles, so payment is authorized within the scoped authority of the token holder.
Is a direct self-service path to paid access documented?
supported: freshA documented direct purchase path reaches paid access without a vendor decision point.
Vercel documents programmatic credit purchase through POST /v1/billing/buy against the payment method on file, charged immediately, alongside the self-service Pro plan upgrade; no vendor review stands in the path.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Vercel REST API's deployment creation returns a deployment object with a `readyState` field and indicates callers can poll `readyState` to track progress through states such as QUEUED, INITIALIZING, BUILDING, READY, or ERROR. However, current evidence leaves explicit reconciliation procedures and specific documented time bounds unresolved.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Credentials, grants, or configuration are delivered through a documented agent-usable flow.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshCredentials, grants, or configuration are delivered through a documented agent-usable flow.
Vercel provides an agent-usable CLI command (`vercel tokens add "<name>"`) that creates personal access tokens and prints the plaintext value directly to stdout for immediate capture in CI environments or scripts.
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.
Vercel REST API's deployment creation returns a deployment object with a `readyState` field and indicates callers can poll `readyState` to track progress through states such as QUEUED, INITIALIZING, BUILDING, READY, or ERROR. However, current evidence leaves explicit reconciliation procedures and specific documented time bounds unresolved.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Deployments can be initiated programmatically via direct HTTP POST requests to `https://api.vercel.com/v13/deployments` using a bearer access token.
What would improve this stage
- Expose bounded machine-readable terminal status and reconciliation semantics.
Safe failure handling is documented only partially.
The REST API documentation describes general error codes (such as forbidden, rate_limited with reset timestamps, bad_request, internal_server_error, and not_found), but complete safe handling semantics like explicit idempotency and reconciliation are not fully detailed.
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?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained excerpts describe REST or RPC interfaces, SDKs and CLIs for Vercel REST API; they contain no first-party statement that an agent-native protocol interface is absent, and several navigation excerpts mention MCP resources without establishing coverage of the assessed targets.
- deployment-api
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Vercel access tokens can be created, listed, and revoked via the Vercel CLI (vercel tokens add, list, rm) or account settings with project scoping. However, explicit recovery mechanisms following compromise are not fully detailed in the retained evidence.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
The REST API documentation describes general error codes (such as forbidden, rate_limited with reset timestamps, bad_request, internal_server_error, and not_found), but complete safe handling semantics like explicit idempotency and reconciliation are not fully detailed.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Requests to the Vercel REST API are authenticated using scoped Vercel Access Tokens passed via the Authorization header as a Bearer token.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Vercel defines explicit REST endpoints, parameters, request and response structures, status codes, and error formats across deployment and management operations.
- 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.
Essential service operations across Vercel REST API errors, reference overview, and deployment management endpoints are documented and accessible via standard HTTP REST requests.
- 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
No stage is established as blocked.
Where autonomy is limited
- Sign up: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
- Provision: Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
- Operate: Safe failure handling is documented only partially.
What this grade establishes
14 of 14 graded signals have current supporting evidence. 2 of 5 additional barrier checks are verified.Unknown checks are not a pass or a confirmed blocker. This report is not proof of an end-to-end purchase or service session.
How the grade is derived
A through C grades count Limited stages; D and F reflect Blocked stages by lifecycle severity.
Coverage is complete only when every graded signal has supported, fresh, non-conflicting evidence. Barrier and informational signals do not change coverage; only fresh, supported barrier values that passed their admission evidence rule participate in stage outcomes.
Each stage takes its worst graded signal or verified barrier. A fresh, supported mandatory barrier that passed its admission evidence rule can block that stage; incomplete or stale barrier evidence remains context only. The overall grade is derived from the five stage states.
Startup offers
Vercel on the startup-offers board
- Up to $30,000 in creditsVercel for Startups
Distribution
The grade’s badge
One stable image resolving the record’s current live facts, linking to the canonical page. Embed it once; it keeps itself current. Placement is never evidence and never affects rank.
[](https://sourcey.com/log/vercel/agent-readiness/vercel-rest-api/deployment-operations)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xn2p7wd9g3a5rt8zq6
- Projection
- sha256:067c54cc89ba4581463395948ef42812bb3c51600dbcf0f73ffde4a64543aca3
- Policy
- service-use-2026-09-07-blocking-barriers-r12 · sha256:fc9e8f046d86fcf19ab2f1bc547219e503cdc11ffa135d020db7285965cd7d1d
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration