My Anthropic-powered code is ready, but Vercel still needs a safe, rock-solid path to it. Your first task is to wire up the connection with a single private API key, keeping that key inside Vercel environment variables so it never lands in the repo or client bundles. Once the integration is live and confirmed through a quick end-to-end test call, I’d like to keep working together on performance tuning and, a bit later, building out user-authentication features that sit in front of the Anthropic endpoints. For now, success means: • Environment variable configured in Vercel (both preview and production) • Server-side call to Anthropic returns the expected response without exposing the key anywhere public • Brief note or snippet that shows me exactly where to drop new rotated keys in the future If you’ve handled Vercel secrets, Next.js serverless functions, or similar before, you should feel right at home. Let’s get this connection locked down so we can move on to the fun optimisation work.