access-protected-vercel-deployment

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 diagnosis: Interpret protection pages and environment mismatch errors, and determine when a development → production Trusted Sources rule is required. - Use Case: A preview URL returns a Vercel SSO page when curled in CI; use vc curl with the linked project to fetch the health endpoint without disabling Deployment Protection. ## Quick Start Ask the assistant to curl your protected Vercel deployment URL, and it will use vercel curl or inject the OIDC token header to authenticate the request.