Troubleshooting · Cursor

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.

What you see

HTTP 429
{"error":{"message":"Rate limit reached. Please retry shortly.","type":"rate_limit_error","param":null,"code":"rate_limit_exceeded"}}

Why it happens

  • The rate or concurrency ceiling of the account behind your key was exceeded. With a custom key, Cursor's own plan limits are out of the picture — this is your key's budget.
  • Agent runs and several busy chat tabs send requests at the same time, and together they reach the ceiling.
  • The same key is shared with other tools or teammates, and their traffic counts against the same ceiling.
  • Rapid-fire retries after the first 429 keep the window full.

How to fix it

  • Run fewer agent runs and chats at the same time on one key.
  • Pause the other tools that share the key while a long Cursor run works.
  • Wait for the Retry-After interval before retrying; tight manual retries prolong the condition.

Related searches

  • cursor rate limit exceeded custom api key
  • cursor 429 custom api key

FAQ

Is this Cursor's fast-requests limit?+
No. With your own key, requests bypass Cursor's plan metering entirely. The 429 comes from the endpoint behind your key.
Why do agent runs hit 429 more often than chat?+
An agent run sends many requests back to back and often in parallel, so it reaches a rate or concurrency ceiling sooner than a single chat.
Does upgrading my Cursor plan help?+
Not for this error. The ceiling belongs to the account behind the API key. Reduce parallel usage, or wait for the Retry-After interval.

Skip the broken setup

apiToken.sale serves GPT and Gemini models through OpenAI-compatible, Messages (Anthropic format) and native Gemini endpoints — standard SDKs, one key, one prepaid balance. Point your tool's base URL at it, and the config on this page works as written.