Provenance
observed · 7 Aug
Freshness
fresh
Dispute
none
Revision
sha256:362bb4b1cb99…

Agent report card

Can an agent use Vercel REST API through Deployment operations?

Grade D: Only part of the applicable terms is machine-readable.

Vercel / active

Agent ReadinessDBlocked
Coverage
complete: 11/11
Freshness
fresh
Last tested
Evidence
observed: not disputed

Five-stage assessment

Where agent autonomy holds and where it breaks

First break: Evaluate

  1. Evaluate

    Limited

    Only part of the applicable terms is machine-readable.

    An ARD declaration has not been established.

    An agent can discover the product and funnel from the tested public entrypoints.

    Eligibility can be decided from explicit public criteria.

    Pricing or the absence of a charge is explicit and machine-readable.

    Evidence and actions

    ARD declaration unknown

    missing: unknown

    An ARD declaration has not been established.

    ard_declaration: Unknown

    Decidable eligibility

    supported: fresh

    Eligibility can be decided from explicit public criteria.

    Vercel's Terms of Service explicitly specify public eligibility criteria, including an age requirement of at least 16 years and mandatory valid account information during sign-up.

    decidable_eligibility: Ready: tested 7 Aug

    Method http 1

    Machine discovery

    supported: fresh

    An agent can discover the product and funnel from the tested public entrypoints.

    The Vercel REST API documentation and its deployment endpoints are fully discoverable and documented at the public REST API entrypoint.

    machine_discovery: Ready: tested 7 Aug

    Method http 1

    Readable pricing

    supported: fresh

    Pricing or the absence of a charge is explicit and machine-readable.

    Pricing details across Hobby ($0/mo), Pro ($20/mo), and Enterprise plans are explicitly published and machine-readable on the Vercel pricing page.

    readable_pricing: Ready: tested 7 Aug

    Method http 1

    Structured terms limited

    supported: fresh

    Only part of the applicable terms is machine-readable.

    Vercel's Terms of Service are available as readable HTML web pages but are not published as a dedicated structured data format.

    structured_terms: Limited: tested 7 Aug

    Method http 1

    What would improve this stage

    • Publish complete applicable terms in a stable machine-readable document.

  2. Sign up

    Blocked

    The signup flow could not be operated by an agent.

    Whether CAPTCHA blocks signup has not been established.

    Whether phone verification is required has not been established.

    A stable signup entrypoint is available.

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    Evidence and actions

    CAPTCHA-free signup unknown

    supported: fresh

    Whether CAPTCHA blocks signup has not been established.

    The headless rendering of the Vercel signup page encountered an error page, so the presence or absence of a CAPTCHA on the signup flow could not be verified from the captured DOM text.

    captcha_free: Unknown: tested 7 Aug

    Method headless 1

    Machine-operable signup unavailable

    supported: fresh

    The signup flow could not be operated by an agent.

    The headless capture of the signup page failed to render controls and displayed 'Something went wrong', preventing machine operation.

    machine_operable_form: Blocked: tested 7 Aug

    Method headless 1

    Phone-free signup unknown

    supported: fresh

    Whether phone verification is required has not been established.

    Because the headless signup render failed with an error, whether phone verification is required during registration cannot be determined.

    phone_verification_free: Unknown: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    The signup HTTP entrypoint at https://vercel.com/signup renders successfully and presents login and signup options including email and social providers.

    stable_entrypoint: Ready: tested 7 Aug

    Method http 1

    Supported identity flow

    supported: fresh

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    Vercel documents a supported identity flow using API access tokens created under account settings, with support for scoping access to personal accounts or specific teams and passing the token as a Bearer header.

    supported_identity_flow: Ready: tested 7 Aug

    Method headless 1

    What blocks agents

    • The signup flow could not be operated by an agent.

    What would improve this stage

    • Expose labelled, deterministic controls and documented validation without requiring hidden human interaction.

  3. Pay

    Ready

    The required price or no-charge status is explicit before commitment.

    Machine-operable checkout has not been established.

    A supported payment rail has not been established.

    Whether sales intervention is required has not been established.

    Evidence and actions

    Explicit price

    supported: fresh

    The required price or no-charge status is explicit before commitment.

    Vercel explicitly details plan pricing on its pricing page, including a $0 Hobby plan, $20/month Pro plan, and usage-based component pricing.

    explicit_price: Ready: tested 7 Aug

    Method http 1

    Machine-operable checkout unknown

    supported: fresh

    Machine-operable checkout has not been established.

    The signup page rendered an error during headless testing, preventing observation of machine-operable checkout capabilities.

    machine_operable_checkout: Unknown: tested 7 Aug

    Method headless 1

    Sales-free purchase unknown

    supported: fresh

    Whether sales intervention is required has not been established.

    The signup page produced an error during headless execution, leaving sales intervention requirements unverified in the tested flow.

    sales_intervention_free: Unknown: tested 7 Aug

    Method headless 1

    Supported payment rail unknown

    supported: fresh

    A supported payment rail has not been established.

    Headless testing of the signup route encountered an error, preventing verification of supported payment rails.

    supported_payment_rail: Unknown: tested 7 Aug

    Method headless 1

  4. Provision

    Ready

    Successful onboarding automatically activates usable access.

    A bounded provisioning delay has not been established.

    Usable credentials or delegated access are delivered through a documented flow.

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Evidence and actions

    Automatic activation

    supported: fresh

    Successful onboarding automatically activates usable access.

    Calling the POST /v13/deployments endpoint immediately creates and activates a new deployment resource, transitioning automatically through QUEUED, INITIALIZING, and BUILDING to READY or ERROR.

    automatic_activation: Ready: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    The REST API documentation describes the build state lifecycle but does not provide a specific, documented bound or SLA for provisioning completion time.

    bounded_delay: Unknown: tested 7 Aug

    Method http 1

    Credential delivery

    supported: fresh

    Usable credentials or delegated access are delivered through a documented flow.

    Vercel API Access Tokens can be created and scoped within Account Settings and used as Bearer tokens in the Authorization header for API requests.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status

    supported: fresh

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    The API response includes a machine-readable `readyState` field indicating the deployment state along with structured error codes and fields.

    machine_readable_status: Ready: tested 7 Aug

    Method http 1

  5. Operate

    Limited

    Recovery is available only for some failure modes or requires human intervention.

    An agent protocol interface has not been established.

    A documented API or tool interface is available for operation.

    Authentication is documented and usable within an agent authorization boundary.

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Evidence and actions

    Agent protocol interface unknown

    missing: unknown

    An agent protocol interface has not been established.

    agent_protocol_interface: Unknown

    API or tool access

    supported: fresh

    A documented API or tool interface is available for operation.

    Vercel REST API provides a fully documented direct HTTP REST service and SDK interface under api.vercel.com for managing deployments and project resources programmatically.

    api_tool_access: Ready: tested 7 Aug

    Method http 1

    Delegated recovery limited

    supported: fresh

    Recovery is available only for some failure modes or requires human intervention.

    Deployment operations include recovery endpoints such as deployment cancellation via REST API, but complex failure paths like domain purchase additions require contacting support.

    delegated_recovery: Limited: tested 7 Aug

    Method http 1

    Documented limits and errors

    supported: fresh

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Vercel REST API documents specific error structures, HTTP error codes, rate-limit response headers, and deployment limits across endpoints.

    documented_limits_errors: Ready: tested 7 Aug

    Method http 1

    Usable authentication

    supported: fresh

    Authentication is documented and usable within an agent authorization boundary.

    Vercel Access Tokens are created in account settings with support for team scoping and can be passed directly via standard HTTP Authorization Bearer headers.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

    What would improve this stage

    • Provide delegated credential rotation, revocation, retry, and recovery paths without requiring unrestricted human intervention.

What works

  • Pay: The required price or no-charge status is explicit before commitment.
  • Provision: Successful onboarding automatically activates usable access.

What blocks agents

  • Evaluate: Only part of the applicable terms is machine-readable.
  • Sign up: The signup flow could not be operated by an agent.
  • Operate: Recovery is available only for some failure modes or requires human intervention.

Improve the report

Correct it, rerun it, or improve the funnel

Every request carries the exact profile revision, projection, declaration, and Catalog release.

Report outdated evidenceRequest reassessmentClaim this vendorView the exact declaration
Method, policy, and immutable identifiers

Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.

Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.

Profile ID
arp_01kzf0m4xn2p7wd9g3a5rt8zq6
Revision
sha256:362bb4b1cb9969420eff5732182d92192820b7334f2d5d70519f267a15917474
Projection
sha256:baae76e0f0f34f416b053dd661fb54beb3fd0df2fd35ebc0eb7d4f17927f98da
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6