# xAI API problem

**URL:** <https://forum.cursor.com/t/xai-api-problem/152455>\
**Category:** Bug Reports\
**Tags:** byok, grok\
**Created:** [February 20, 2026, 7:58pm UTC](https://forum.cursor.com/t/xai-api-problem/152455 "2026-02-20T19:58:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ed\_pranc](https://avatars.discourse-cdn.com/v4/letter/e/d78d45/32.png) [@ed\_pranc](https://forum.cursor.com/u/ed_pranc)\
**Post date:** [February 20, 2026, 7:58pm UTC](https://forum.cursor.com/t/xai-api-problem/152455/1 "2026-02-20T19:58:38Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Request ID: baa908d4-0c0e-490c-ba7f-cccdeff20015  
Error: ERROR\_PROVIDER\_ERROR – “We’re having trouble finding the resource you requested”  
That your API key is correct and the error still happens  
OS: e.g. macOS  
Cursor version (e.g. Help → About)

### Steps to Reproduce

Try adding Grok xAI API key

Request ID: baa908d4-0c0e-490c-ba7f-cccdeff20015  
{“error”:“ERROR\_PROVIDER\_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble finding the resource you requested. If the problem persists, please contact support.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}  
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.  
aXt: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.  
at upA (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32115:39729)  
at cpA (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32115:38717)  
at fpA (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32116:5088)  
at uol.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32116:9098)  
at async art.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44360:7632)  
at async wOl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:8884)  
at async wOl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:9837)  
at async ALe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32182:15752)  
at async Js (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43415:4781)

### Operating System

MacOS

### Version Information

Version: 2.5.20  
VSCode Version: 1.105.1  
Commit: 511523af765daeb1fa69500ab0df5b6524424610  
Date: 2026-02-19T20:41:31.942Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.4.0  
Chromium: 142.0.7444.265  
Node.js: 22.22.0  
V8: 14.2.231.22-electron.0  
OS: Darwin x64 24.6.0

### For AI issues: add Request ID with privacy disabled

baa908d4-0c0e-490c-ba7f-cccdeff20015

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 21, 2026, 6:49am UTC](https://forum.cursor.com/t/xai-api-problem/152455/3 "2026-02-21T06:49:53Z")

</div>

Hey, thanks for the report and the request ID.

xAI isn’t currently supported as a BYOK provider. Supported providers are OpenAI, Anthropic, Google, Azure OpenAI, and AWS Bedrock. You can find the full list here: [API Keys docs](https://cursor.com/docs/settings/api-keys).

Since you’re on the Pro plan, you can use Grok models directly from the model picker without your own API key, they’re included in your plan.

---

<div class="post-metadata">

**Author:** ![ed\_pranc](https://avatars.discourse-cdn.com/v4/letter/e/d78d45/32.png) [@ed\_pranc](https://forum.cursor.com/u/ed_pranc)\
**Post date:** [February 21, 2026, 7:26am UTC](https://forum.cursor.com/t/xai-api-problem/152455/4 "2026-02-21T07:26:48Z")

</div>

Hi Dean, this is very surprising that it is not supported. And it is rather discriminating. It really takes minimal programming effort to add xAI on top of the existing supported APIs. I yesterday searched the forums and many users have this complain. When do you think you will add it?

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 21, 2026, 8:20am UTC](https://forum.cursor.com/t/xai-api-problem/152455/5 "2026-02-21T08:20:08Z")

</div>

I get that you’d like to use your own xAI API key. Unfortunately, we don’t have plans to add xAI as a BYOK provider anytime soon.

Adding new BYOK providers is a product team decision and depends on a lot of factors, not just integration effort. It also includes provider agreements, support, security, and overall priorities.

Grok models are already integrated and available to all Pro users directly in the model picker, so you don’t need your own API key. That’s our main way of providing access to Grok.

If you want to share feedback or vote for features, you can use the Feature Requests category. Feel free to post a separate request there so the team can see the demand.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [March 15, 2026, 8:20am UTC](https://forum.cursor.com/t/xai-api-problem/152455/6 "2026-03-15T08:20:54Z")

</div>

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
