LLM Request Rejected: What It Means and How to Fix Every Variant
LLM Request Rejected: What It Means and How to Fix Every Variant
You are in the middle of coding, researching, or running an AI workflow, and you hit this message: "LLM request rejected." Sometimes it comes with a longer explanation about third-party apps, extra usage credits, or workspace admins. Sometimes it is just those three words.
This guide covers every known variant of this error, what triggers each one, and how to fix it fast.
Quick Diagnosis: Which Error Are You Seeing?
The "LLM request rejected" error shows up in several forms. Each has a different cause and a different fix. Find yours in the table below.
| Error message | Root cause | Fix | |---|---|---| | LLM request rejected (no additional text) | Extra usage credits exhausted or account billing issue | Add credits at claude.ai/settings/usage | | ...third-party apps now draw from your extra usage, not your plan limits. We've added a $20 credit... | Anthropic billing change; starter credit not yet claimed | Claim the $20 credit at claude.ai/settings/usage | | ...We've added a $100 credit to get you started... | Same billing change, higher credit tier (heavier usage history) | Claim the $100 credit at claude.ai/settings/usage | | ...We've added a $200 credit to get you started... | Same billing change, team/enterprise tier | Claim the $200 credit at claude.ai/settings/usage | | ...you're out of extra usage. Add more at claude.ai/settings/usage... | Starter credit already claimed and fully spent | Add more funds or enable auto-reload | | ...ask your workspace admin to claim it and keep going | Organization account; only an admin can claim the credit | Contact your workspace admin (see below) |
Why This Error Exists
In early 2026, Anthropic changed how Claude usage is billed for third-party apps. Before the change, tools like Cursor, Windsurf, Claude Code, and VS Code extensions shared your Pro or Team plan's included usage. After the change, third-party app requests pull from a separate "extra usage" credit pool.
This means your $20/month Pro subscription can be fully active and you will still see "LLM request rejected" if your separate extra usage balance is empty. These are two independent pools.
Fix 1: Claim Your Starter Credit
When Anthropic rolled out this change, they added a one-time starter credit to every account. The amount depends on your account type:
| Account type | Credit amount | Who claims it | |---|---|---| | Pro (individual) | $20 | You, at claude.ai/settings/usage | | Pro (high usage history) | $100 | You, at claude.ai/settings/usage | | Team / Enterprise | $200 | A workspace admin must claim it | | Organization member | Varies | Your workspace admin claims it for the org |
Steps:
- Go to claude.ai/settings/usage
- Make sure you are signed into the correct account (the one linked to your third-party app)
- Look for the banner about your starter credit and click to claim it
- Your extra usage balance should now show the credited amount
- Go back to your tool and retry the request
If you do not see a banner, your credit may have been applied automatically. Check whether your extra usage balance already shows a positive number.
Fix 2: Add More Credits (If Starter Credit Is Spent)
If you already claimed and spent your starter credit, you need to manually add more funds:
- Go to claude.ai/settings/usage
- Click "Add credits" or the equivalent button
- Choose an amount to add (Anthropic accepts the same payment method as your subscription)
- Credits apply immediately; retry your request
Fix 3: Enable Auto-Reload
To avoid hitting the wall again, set up auto-reload:
- On the usage settings page, find the auto-reload option
- Set a reload amount (e.g., $10 or $20)
- Set a trigger threshold (e.g., reload when balance drops below $5)
- Credits will automatically top up before you run out
Fix 4: Organization Accounts (Workspace Admin Required)
If you see the message about asking your workspace admin, you are on an organization Claude account. Individual members cannot claim the credit themselves.
What to do:
- Find out who is the workspace admin. Check with your team lead, IT department, or whoever manages your company's Claude subscription.
- Send them a link to claude.ai/settings/usage and ask them to claim the organization credit.
- Once the admin claims it, all team members' third-party app requests will work again.
- The admin should also set up auto-reload so the whole team does not get blocked when the starter credit runs out.
Warning
Organization credits are shared across all team members. A team of five developers using Cursor heavily can burn through a $200 credit in a few days. Make sure your admin sets up auto-reload or manually adds enough credits for the team's usage.
How Fast Do Credits Get Used Up?
Usage rates vary widely depending on the tool and how aggressively you use it.
| Tool and usage pattern | Approximate cost per hour | $20 credit lasts | $100 credit lasts | |---|---|---|---| | Cursor autocomplete, light coding | $0.50 - $1.50/hr | 13 - 40 hours | 65 - 200 hours | | Cursor agent mode, heavy refactoring | $2 - $5/hr | 4 - 10 hours | 20 - 50 hours | | Claude Code CLI, single agent | $1 - $3/hr | 7 - 20 hours | 33 - 100 hours | | Claude Code, parallel agents (5+) | $5 - $15/hr | 1 - 4 hours | 7 - 20 hours | | VS Code Claude extension, chat only | $0.10 - $0.30/hr | 65+ hours | 330+ hours | | Windsurf, moderate use | $1 - $3/hr | 7 - 20 hours | 33 - 100 hours |
Tip
Check your per-app usage breakdown on the claude.ai/settings/usage page. This shows exactly which tools are consuming your balance, so you can identify unexpectedly expensive sessions.
Common Mistakes That Keep the Error Coming Back
Confusing plan limits with extra usage. Your Pro subscription's monthly reset does not refill extra usage credits. If claude.ai works fine but Cursor or Claude Code keeps rejecting, your plan is not the problem. Your extra usage balance is empty.
Thinking the starter credit is recurring. Whether you got $20, $100, or $200, it is a one-time bonus from the billing transition. There is no second free credit. After it is spent, you pay.
Wrong account linked. If you have multiple Anthropic accounts (personal vs. work), your third-party app might be authenticated against the account that has no credits. Check your tool's settings for which Claude account it connects to.
API key confusion. If you use a direct Anthropic API key with pay-per-token billing, that is a completely separate system. The extra usage change only affects third-party apps using OAuth-based Claude account access. Your API key usage is unaffected.
Not setting up auto-reload. If you rely on third-party AI tools for daily work, manually adding credits every few days guarantees interruptions. Set auto-reload once and do not think about it again.
Alternatives If You Do Not Want to Pay for Extra Usage
-
Use claude.ai directly. Your plan limits still cover direct usage. Copy your code or question into the web app, get the answer, and paste it back. Slower, but included in your subscription.
-
Use your own API key. If you are a developer, configure your tool to use a direct Anthropic API key instead of your Claude account. You get granular spending control and avoid the extra usage system. Cursor, Claude Code, and most tools support custom API key configuration.
-
Switch AI providers temporarily. If your editor supports multiple backends (Cursor supports GPT-4, Gemini, etc.), switch to another provider while your Claude credits are empty.
-
Use a local model. Tools like Ollama let you run models locally with no usage costs. The quality is lower than Claude, but there are no billing walls.
Troubleshooting: Still Seeing Rejections After Adding Credits
If you added credits or claimed your starter bonus and requests are still failing:
- Check the account. Make sure you are logged into the same Anthropic account in both claude.ai and your third-party app. Open your tool's settings and verify which account it is using.
- Clear the tool's cache. Some tools cache the rejected state. In Cursor, try closing and reopening the editor. In Claude Code, start a new session.
- Check for org vs. personal mismatch. If your workplace uses Claude Team or Enterprise, your personal Pro credits do not apply when working through the organization's tools. You need the admin to add credits to the org account.
- Verify the credit was actually claimed. Go back to claude.ai/settings/usage and confirm the balance is positive. Sometimes the claim button needs a page refresh to register.
Quick Reference: Error Messages and Fixes
| You see this... | Do this | |---|---| | "LLM request rejected" | Go to claude.ai/settings/usage, add credits or claim your starter bonus | | "...third-party apps now draw from your extra usage..." | Claim the one-time starter credit ($20/$100/$200) at claude.ai/settings/usage | | "...you're out of extra usage..." | Add more credits manually or enable auto-reload | | "...ask your workspace admin to claim it..." | Contact your Claude workspace admin; they need to claim the org credit | | Error persists after adding credits | Verify correct account is linked, restart your tool, check org vs. personal account |
Fazm is an open source macOS AI agent. Open source on GitHub.