I have followed the instructions in the v0 documentation, entered the URL and key, and manually added the v0 models: v0-1.5-md&v0-1.5-lg. However, it still doesn’t work. The error message can be seen in the screenshot. I hope to get some help, thank you!
Hi @hizahon-1027, welcome to the Vercel Community!
I’m sorry that you’re facing this issue. I followed the same steps from the docs and got it working in Cursor for the first time.
Can you try closing and reopening Cursor and then adding the settings again?
I’ve restarted the cursor many times, but it’s still not working. This has been bothering me all day. Could you please record a video showing your steps? Thank you!
Hey, I won’t be able to record screen. But, here’s exactly what I did step by step:
- Opened v0 > Settings > API keys > Created a new one & Copied it
- Opened Cursor > Settings > Models > API Keys
- Enable OpenAI API Key and paste the copied key here
- Enable Override OpenAI Base URL and replace the value with
https://api.v0.dev/v1 - In the Models section > Add Custom Model, added
v0-1.5-lgandv0-1.5-md
Oh, I see. Can you copy the whole error block {"error": {"type"...... and paste here? Also, try the Copy Request Details button if it works.
I can then ask the team to see what is going wrong with your API requests.
Request ID: d75d4a78-8d8e-4dfe-9b66-488afe28c951
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We encountered an issue when using your API key: Streaming error\\n\\nAPI Error:\\n\\n`\n{\"error\":{\"type\":\"provider\",\"reason\":\"provider_error\",\"message\":\"Provider returned 500\",\"retryable\":true,\"provider\":{\"status\":500,\"body\":\"{\\\"success\\\":false,\\\"error\\\":\\\"Unknown error\\\"}\"}}}\n`”,“additionalInfo”:{},“buttons”:[ ],“planChoices”:[ ]},“isExpected”:true}
ConnectError: \[unauthenticated\] Error
at szc.$endAiConnectTransportReportError (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12375:456006)
at xBo.\_doInvokeHandler (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:22831)
at xBo.\_invokeHandler (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:22573)
at xBo.\_receiveRequest (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:21335)
at xBo.\_receiveOneMessage (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:20152)
at zLt.value (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:18244)
at Ee.\_deliver (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
at Ee.fire (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
at Tvt.fire (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12360:12156)
at MessagePort. (vscode-file://vscode-app/g:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15027:18433)
The copied information is as follows,Thanks.
Hi @hizahon-1027, are sharing images in your message by any chance? Or is it plain text that’s erroring out?
it’s plain text that’s erroring out
Hey @hizahon-1027, I’m sorry it’s taking longer but I’m still on it. Trying to find the root cause with different team members.
Thank you, I will wait for the solution.
Same issue here
I had the same issue but it only works if you have a paid subscription to cursor. I switched off from cursor because I was spending a lot, I was loving using windsurf.
The good news is that I was able to config all these models:
BUT v0-mini, pro and max fallbacks to v0-1.5-md, is there a workaround to use the latest models?
Same thing here. I did follow the steps of the documentation but none of the v0 models are working on my cursor, so I get: “We’re having trouble finding the resource you requested. If the problem persists, please contact support.”
I am also facing this same problem. I went ahead and tried with the Vercel AI Gateway with a different type of api key and different gateway. Same error is seen.