Subject: Hobby deployment restriction — API returns HTTP 402 despite team being within usage limits

Hello Vercel Team,

I need help clearing a deployment restriction on my Hobby team.

Team: Kalyandck Project: nifty500-momentum-scanner Project ID: prj_HF6aEFdaYjbbs6ijx2S26HEo6lwi Team ID: team_a5LzQS5T7cFfAo1gDUguxSzs GitHub: kalyandck/nifty500-momentum-scanner Production domain: nifty500-momentum-scanner.vercel.app

Deployment creation through the Vercel API is currently returning:

HTTP 402

{"id":null,"url":null,"error":"payment_required","message":null}

I have already verified:

the correct teamId is being supplied; production deployment creation returns 402; preview deployment creation also returns 402; the Vercel project exists and is in the correct Hobby team; the project has existing READY production deployments; there are no currently running/stuck builds; the project's current production deployment is READY; the visible team usage is well below the displayed resource limits.

The latest successful production deployment is:

dpl_9Nz9eMxh3CfaaCiaQASYkZ8CUD6X

Commit:

a6a442d8477a67d3a87af9380e9c6226e84d31c2

New commits are not being deployed because deployment creation itself is returning HTTP 402.

Please audit the Hobby team's deployment/build quota and deployment restriction state and reset/clear the restriction if it is stuck or incorrectly applied.

I am not requesting a plan upgrade. I would like the deployment restriction/quota state investigated so normal deployments can resume.

Thank you.