Cursor Model Provider Errors — 401, 429, Unable to Reach
With a custom OpenAI base URL and key, Cursor sends GPT and Gemini requests to that endpoint, so most failures are either the key/base-URL configuration or the endpoint's own response passed through. The pages below separate the two.
| Error | Meaning |
|---|---|
We're having trouble connecting to the model provider. This migh… | Cursor reports it cannot reach the model provider when the request dies before an HTTP response: wrong base URL, network path, or a provider outage. How to tell which one you have. |
Invalid API key | Cursor rejects an API key on verify when the key and the base URL do not belong together, or the override field still points at the default OpenAI endpoint. The checklist that fixes it. |
Request failed with status code 401 | A 401 inside Cursor chat means the endpoint answered and rejected the credentials: key and base URL mismatched, key revoked, or account access withdrawn. The fix path. |
{"error":{"message":"Rate limit reached. Please retry shortly.",… | With a custom API key, a 429 in Cursor is the rate or concurrency ceiling of the account behind that key, not Cursor's plan limits. Why agent runs trigger it and how to stop the loop. |
Cursor: Unable to Reach the Model Provider — Causes and Fixes
Cursor reports it cannot reach the model provider when the request dies before an HTTP response: wrong base URL, network path, or a provider outage. How to tell which one you have.
Cursor Invalid API Key With a Custom Base URL — Why Verify Fails
Cursor rejects an API key on verify when the key and the base URL do not belong together, or the override field still points at the default OpenAI endpoint. The checklist that fixes it.
Cursor: Request Failed With Status Code 401 — Custom API Key Fix
A 401 inside Cursor chat means the endpoint answered and rejected the credentials: key and base URL mismatched, key revoked, or account access withdrawn. The fix path.
Cursor Rate Limit / 429 With Your Own API Key
With a custom API key, a 429 in Cursor is the rate or concurrency ceiling of the account behind that key, not Cursor's plan limits. Why agent runs trigger it and how to stop the loop.