access-protected-vercel-deployment

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

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill access-protected-vercel-deployment-dsgalkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access-protected-vercel-deployment
Source: https://github.com/dsgalkar/dnyaneshwar_portfolio/tree/main/.agents/plugins/vercel/skills/access-protected-vercel-deployment
Command: npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill access-protected-vercel-deployment-dsgalkar

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 without exposing the token. - Trusted Sources diagnostics: Interpret protection pages, 401/403 responses, and TRUSTED_SOURCES_ENVIRONMENT_MISMATCH to determine when a developmentproduction Trusted Sources rule is required. - Use Case: A preview URL returns a Vercel SSO page in your browser automation; inject the OIDC token header via vc env run and continue the session without disabling Deployment Protection. ## Quick Start Ask the AI to access your protected Vercel deployment URL using vercel curl or by attaching the OIDC token header to your browser automation session.

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 access a Vercel deployment protected by authentication?

Use `vercel curl` (`vc curl`) instead of raw curl for HTTP requests; it accepts native curl options and authenticates with your existing Vercel CLI session. For browser automation, attach the `x-vercel-trusted-oidc-idp-token` header with your local VERCEL_OIDC_TOKEN.

How do I test a protected Vercel preview with Playwright or agent-browser?

Set the `x-vercel-trusted-oidc-idp-token` header in the browser context's extra HTTP headers before the first navigation. With agent-browser, run it through `vc env run` so VERCEL_OIDC_TOKEN is injected without printing or persisting the token.

Why does my Vercel request return TRUSTED_SOURCES_ENVIRONMENT_MISMATCH?

This error means your token is valid but its caller environment is not allowed to reach the target environment. A local development token accesses same-project Preview deployments by default; protected Production requires a Trusted Sources rule allowing `development` → `production` in the target project's settings.

What is the difference between x-vercel-trusted-oidc-idp-token and x-vercel-oidc-token?

Use `x-vercel-trusted-oidc-idp-token` for Trusted Sources access to protected deployments. The `x-vercel-oidc-token` header carries an OIDC token into a Vercel Function and serves a different purpose, so it is not a substitute.

Should I disable Vercel Deployment Protection to run automated tests?

No. Disabling Deployment Protection weakens access control and is unnecessary. Use `vc curl` for HTTP requests or an origin-scoped OIDC token header for browser automation, and only adjust Trusted Sources rules with explicit authorization.