Amy Egan Thanks for sharing the idea! No immediate plans for this, but this thread will stay open so others who are interested can weigh in

Ryu Hi Fabian, That would be a useful dashboard view. I don’t see a documented way to group the normal AI Gateway Overview by Custom Reporting user or tags yet. Right now those fields look like they’re mainly exposed through the reporting API, while the dashboard gives higher-level project/API-key style summaries. I’d be careful using lots of API keys only as feature labels, because key management, rotation, ownership, and budgets can get messy over time. I’d probably use API keys for real boundaries, like environment/app/team, and use reporting tags for feature-level attribution: Then query by ta

Tesvm For reference, the failing command was: codex mcp add vercel --url mcp.vercel.com The OAuth flow then generated a callback like: 127.0.0.1:49683/callback/J69OfRTZqnV5 Vercel rejected it before returning to Codex. That usually removes one back-and-forth.

luchao Has this been resolved? What would be the solution?

dan-lee Running into the same issue. With corepack enabled, I'd have expected Vercel to pick up the pinned pnpm version automatically.

Holmlab Developer Setting ENABLE_EXPERIMENTAL_COREPACK=1 env var in Vercel UI worked for me.

dan-lee Edit: Ok weird, in another project it seems to work just fine 🤨 Edit 2: Found the issue: It's a monorepo that had a sub-package that defined a pnpm@10 version. The error message picked up the root package.json hence my confusion. Are you sure? This is what I see:

MatthieuGD I'm in the same situation, i.e. paying 20$ a month for a real usage of 3-4$

Blacknetpk 8255 exactly that is why i have given the suggestion for vercel team to pay attention in this matter

Amy Egan If you can tell me more about the problem, I’d be happy to connect with the engineering team to get you the help you need or share your feedback!

Erik Sandquist Well I had a problem where AI gateway selects another provider than the BYOK option, but it doesn't disclose a reason for it. The status is ok for the provider, tried testing the key again and it worked and have balance at the provider but still chooses another provider which massively drained my Vercel balance since without BYOK i get charged about 5-6x more.

galb Speed Insights data is in the public API now. It is the same query that vercel metrics sends. My test on a real team: speedInsights({ since, groupBy: ["projectId"], outputs: { lcp: { metric: "vercel.speed_insights.lcp_ms", aggregation: "p75" } } }) - p75 LCP per project (1,524 ms from 383 samples) My open-source client vercel-analytics-api (MIT, unofficial) wraps it. For "healthy", compare each p75 with LCP 2.5 s, INP 200 ms and CLS 0.1.

Quest Same here, hopefully upvoting/commenting will get this attention

Taras Having the same issue here, persisting after redeploy. Happening only in one of my projects for some reason

0x00b7 This is due to their new firewall enforcement, which also blocks their own preview server from taking screenshots.

Pauline P. Narvas Thanks for sharing, @cole-loma! I've passed this onto our product teams internally.

Pauline P. Narvas Thanks for the feedback! We've shared internally.