Personal access tokens return 404 "User not found" / invalidToken on every API call (Hobby plan)

Hi, hitting a consistent issue on a Hobby plan account (lcsanvitto@gmail.com, team: lcsanvittos-projects).

Personal access tokens (vcp_...) authenticate successfully at creation — shown correctly on the Tokens page with the right scope — but every subsequent API call with them returns a 404 "User not found" / invalidToken error.

What I've verified:

Tested Authorization: Bearer (no quotes) directly against https://api.vercel.com/v2/user — 404 "User not found"
- Tested against a team-scoped endpoint with ?teamId= — same 404
- - Reproduced with 5 separately created tokens, both "Full Account" and single-project ("lagu-simulador") scope
  - - The CLI's own device-flow login session (vercel dev, vercel env ls/add) works completely fine on the same machine — only vcp_ personal access tokens fail
    - - Noticed a "Non-SAML" badge on the "Full Account" scope option when creating a token, but support confirmed via the Vercel Agent chat that this is just an informational label, not the cause (account is Hobby, no SSO involved)
    - This is blocking a GitHub Actions CI setup that needs a PAT to run vercel dev non-interactively. Already went through the in-app Vercel Agent support flow, which escalated it but Hobby plan doesn't get a ticket for the Accounts category (redirected here instead).
  - Has anyone seen this, or is there something account-side that could cause every fresh PAT to be rejected like this?

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

I had the same issue - since I have a Pro account, I was able to ask support.

For me, I created a "team/project" scoped token, but creating a full account token fixed it for me:

Feedback support bot:

During initialization of any CLI command (including vercel pull), the Vercel CLI executes an internal preflight check against GET /v2/user to load the authenticated user identity.

When a Personal Access Token is created with Team Scope (scoped strictly to the specific team), it is restricted solely to team-level resources and is blocked from accessing the user-level /v2/user endpoint. As a result, the preflight check receives a 404 Not Found, causing the CLI execution to abort before it can pull the project settings.

Once the token has account-level scope, the CLI preflight check will succeed and vercel pull will successfully retrieve your project configuration and environment variables.

So its basically broken then? If you're allowed to create limited scope tokens but they do a pre-flight that never succeeds, that is broken. The 'fix' to create a wider scoped token just to pass arbitrary pre-flight checks is absolute trash.