Authenticate the Vercel Sandbox SDK from a non-Vercel environment (external CI/CD, self-hosted server) using an access token, team ID, and project ID instead of OIDC.

Documented steps

1. Obtain your Vercel team ID (https://vercel.com/docs/accounts#find-your-team-id) and project ID (https://vercel.com/docs/project-configuration/general-settings#project-id).
2. Create a Vercel access token with access to the team (https://vercel.com/docs/rest-api#creating-an-access-token).
3. Set these as environment variables in your CI/CD system: `VERCEL_TEAM_ID=team_xxx`, `VERCEL_PROJECT_ID=prj_xxx`, `VERCEL_TOKEN=your_access_token`. Docs: https://vercel.com/docs/sandbox/concepts/authentication
4. In JS/TS, pass them explicitly: `const sandbox = await Sandbox.create({ teamId: process.env.VERCEL_TEAM_ID!, projectId: process.env.VERCEL_PROJECT_ID!, token: process.env.VERCEL_TOKEN! })`.
5. In Python, pass equivalents: `Sandbox.create(team_id=os.environ.get("VERCEL_TEAM_ID"), project_id=os.environ.get("VERCEL_PROJECT_ID"), token=os.environ.get("VERCEL_TOKEN"))`, or rely on the SDK auto-reading `VERCEL_TOKEN`, `VERCEL_PROJECT_ID`, `VERCEL_TEAM_ID` env vars directly.
6. Use access-token auth for: external CI/CD systems, non-Vercel hosting, or any environment where `VERCEL_OIDC_TOKEN` is unavailable. Use OIDC (automatic) when the code actually runs on a Vercel deployment.