[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # Why api.v0.dev returns 404 when requesting v0-1.5-md model 97 views · 9 likes · 11 posts Deceptive49 (@deceptive49-8913) · 2026-03-18 · ♥ 1 This endpoint is not available currently. Was this expected, or has this model been permanently removed? Deceptive49 (@deceptive49-8913) · 2026-03-19 · ♥ 1 any help?? Pauline P. Narvas (@pawlean) · 2026-03-19 · ♥ 1 The v0 API endpoint should be `https://api.v0.dev/v1` (not just `api.v0.dev`) Andrew Ross (@dopaminedriven) · 2026-03-20 · ♥ 1 You're right, @deceptive49-8913, it started on Monday AFAIK. I was messaging v0-1.5-md using a multi-provider platform I've scaffolded from scratch over the past 9 months just fine on Sunday evening. It seems that Vercel likely axed agentic api for v0 (hard deletion of the lighter agentic api for standard tool use and conversational interactivity) with 0 notice. Which is a huge bummer because even Google gives at least a week heads up before taking something fully offline like this usually. So i migrated to the AI Gateway and refactored my integration once I got off work The catch? After purchasing credits on the new AI Gateway *solely* to regain access to v0 models (I have 0 use for the gateway otherwise, all other providers on my platform are either integrated via first party SDKs or custom) I found that the Gateway itself actually 404s because it is trying to hit the same exact endpoint that was deleted sometime between Sunday evening and Monday evening (...the same one I, too, was using before it disappeared). Hoping to get some visibility on this...definitely not stoked about how this has been handled at all.  [X post](https://x.com/Dopamine_Driven/status/2033759811871936876) Deceptive49 (@deceptive49-8913) · 2026-03-20 · ♥ 1 i know…..it just everything on https://api.v0.dev/v1 returns 404, you can try use https://api.v0.dev/v1 to use v0-1.5-md model, it returns 404 Deceptive49 (@deceptive49-8913) · 2026-03-20 · ♥ 1 Vercel, such a big platform, yet they haven’t fixed this issue for so long. What’s worse, apparently, they haven’t even noticed that the api.v0.dev endpoint has stopped working. It’s honestly embarrassing for a company of their scale. Even more laughable — https://v0.app/docs/openai-codex is \*still\* pointing to api.v0.dev. Roblenderman 7762 (@roblenderman-7762) · 2026-03-23 Same issue with Kilo Code. Best I can tell you have to turn on the MCP server in VS code and have it use that but not ideal. Deceptive49 (@deceptive49-8913) · 2026-03-25 hello???no body??? Deceptive49 (@deceptive49-8913) · 2026-03-29 · ♥ 1 @pawlean hello, please take a look! Robotdreams (@robotdreams) · 2026-04-02 · ♥ 1 same issue on zed ‘language model provider API endpoint not found‘ Robotdreams (@robotdreams) · 2026-04-04 · ♥ 1 All docs about editor are removed :sweat_smile:
