Hercules 8202 Yeah this is would be really nice to have
naaiyy +1 on this !
Ed Hollinghurst Bumping this after three months with no response from the Vercel team. I've re-checked the current state today (30 Oct 2026): The Web Analytics API docs still list requestPath, route, country, referrerHostname, deviceType, browserName, UTM fields and flags as the supported dimensions. requestHostname isn't among them. The same list is enumerated in the OpenAPI spec and in the Vercel MCP tool schemas for visits/count and visits/aggregate. The response schema for both aggregate endpoints already includes a requestHostname field, so the data is clearly stored and queryable. It just can't be used
Anshuman Bhardwaj Hi @midego1, the forks are linked to the same project the original chat was part of. So, going to the Project view will show you all the forks: Regardless, I will share the feedback with our team. Thanks for posting it here.
Midego1 This is not the sidebar, the sidebar is cluttered with forks when you keep on chatting
Anshuman Bhardwaj Thanks for writing such a detailed use case. I've forwarded this feedback to our v0 team. You can already access v0-1.5-md model using the API. We've it on our documentation. Let me know if you face any issues.
William Not in Cursor: According to vercel.com/docs/v0/cursor, we are still stuck with v0-1.0 there.