Problem using SambaNova API with Cursor

We are attempting to use SambaNova API with cursor frontend. We notice that direct access to SN cloud API is blocked as the example shown below. However we can still access SN API through openrouter as well as the curl command example provided.

]

As cursor business plan subscribers, our organization is also very interested in trying the SambaNova API, and we’d appreciate any assistance or any general feedback on whether this is even possible.

1 Like

@ajit as a temporary fix, SN also offers endpoints through openrouter:
endpoint url: https://openrouter.ai/api/v1
model name: meta-llama/llama-3.1-405b-instruct:free
I tested this and confirmed that this is working. but the latency can be slightly worse than if we could directly access through SN cloud.

1 Like

@anon-9002714 team

Any idea how we can use SambaNova endpoints directly through Cursor?

OpenRouter seems viable but is really slow, which kinda kills the benefits of having a fast inference endpoint provider for 405B LLaMA…

I’m writing to report an issue I’ve encountered with version 0.43.5 of the program. When I try to add my API key from SambaNova, the program is unable to validate it, despite it being correct.

Here are the details of my environment:

  • Cursor Version: 0.43.5
  • VSCode Version: 1.93.1
  • Commit: 2eaa79a1b14ccff5d1c78a2c358a08be16a8e5a0
  • Date: 2024-11-27T09:11:51.854Z
  • Electron: 30.5.1
  • Chromium: 124.0.6367.243
  • Node.js: 20.16.0
  • V8: 12.4.254.20-electron.0
  • OS: Windows_NT x64 10.0.26100

The issue is that when I enter my SambaNova API key, the program is unable to validate it. I’ve double-checked the key multiple times, and it’s definitely correct. I’ve also reviewed the SambaNova documentation and confirmed that their API is compatible with the OpenAI standard, which I believe is the expected format for Cursor.

I’ve seen that others have already reported a similar issue, specifically kz919 on October 22, who mentioned that direct access to the SambaNova cloud API is blocked, but access through openrouter and curl commands is still possible. I’m experiencing the same problem and hope you can resolve this issue.

2 Likes