access-protected-vercel-deployment

Access Vercel deployments protected by authentication using vercel curl or OIDC token headers.

Updated Aug 21, 2025
One-click install
npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill access-protected-vercel-deployment-adithiya-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access-protected-vercel-deployment
Source: https://github.com/Adithiya-S/AI-Study-Companion/tree/main/.agents/skills/access-protected-vercel-deployment
Command: npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill access-protected-vercel-deployment-adithiya-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated requests to Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection fail with login pages, 401/403 responses, or TRUSTED_SOURCES_ENVIRONMENT_MISMATCH errors, blocking testing and verification workflows. ## Core Features & Use Cases - Authenticated HTTP requests: Replace raw curl with vercel curl (vc curl) to access protected preview and production deployments using existing Vercel CLI authentication. - Browser automation access: Attach the short-lived x-vercel-trusted-oidc-idp-token header from VERCEL_OIDC_TOKEN to agent-browser or Playwright sessions for protected URLs. - Trusted Sources diagnosis: Interpret protection responses and configure the correct developmentproduction environment pair in project settings when cross-environment access is required. - Use Case: A preview deployment returns a Vercel SSO page when curled. Run vc curl https://my-app.vercel.app/api/health to authenticate with existing CLI credentials and retrieve the actual response. ## Quick Start Ask the assistant to curl your protected Vercel deployment URL, and it will use vercel curl or the OIDC token header to authenticate the request.

Frequently Asked Questions about access-protected-vercel-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I curl a Vercel deployment protected by authentication?

Use `vercel curl` (or `vc curl`) instead of raw curl. It accepts standard curl options and authenticates with your existing Vercel CLI credentials to reach protected preview and production deployments.

How do I access a protected Vercel URL in browser automation?

Attach the short-lived `x-vercel-trusted-oidc-idp-token` header containing your local VERCEL_OIDC_TOKEN. With agent-browser, inject it via `vc env run`; with Playwright, set it in the browser context's extra HTTP headers before navigation.

What does TRUSTED_SOURCES_ENVIRONMENT_MISMATCH mean on Vercel?

It means your token is valid but its caller environment is not allowed to reach the target environment. A local development token accesses Preview by default; protected Production requires a Trusted Sources rule allowing `development` → `production`.

Why does my Vercel deployment return 401 or 403 after bypassing protection?

A 401 or 403 generated after Vercel protection is bypassed comes from the application's own authentication layer, not Deployment Protection. Debug it separately as an application-level auth issue.

Can a local Vercel token access protected production deployments?

Not by default. Local development tokens access the same project's Preview deployments automatically, but protected Production requires the project's Trusted Sources settings to explicitly allow the `development` → `production` pair.