Checked October 11, 2026: Claude’s usage guide describes session and weekly limits on paid plans. Your model, effort, context and tools affect consumption. Read your own usage view for reset times.
Different limits need different responses
| Limit | What it means | What to do |
|---|---|---|
| Plan allowance | Session or weekly allowance used | Wait for reset or review eligible additional usage options. |
| API rate limit | Too many requests or tokens in a short period | Honor retry guidance and reduce concurrency. |
| Spend or credit limit | Billing budget or balance exhausted | Review authorized budget and payment settings. |
| Context length | Conversation exceeds supported context | Reduce context or start a focused session. |
| Tool-run budget | A run stops after a tool or turn budget | Review completed work before a bounded continuation. |
More usage is not unlimited usage
Usage credits may extend eligible subscription use, but cost money and have applicable terms. API access has its own rate limits, balance and spending controls. A gateway can introduce additional limits, not remove the provider’s.
Reduce waste before increasing spend
- Read the actual limitDo not treat every stopped task as a subscription quota issue.
- Keep tasks focusedUse only relevant files and stop repeated failing loops.
- Set a budgetEstimate a small task first; monitor actual charges.
- Review alternative clients honestlyA client change does not increase your provider entitlement. Local models also need hardware and have capacity limits.
FAQ
Is Claude Pro or Max unlimited?
No. Paid subscriptions have allowances. Consult your account and current plan documentation.
Is the Claude API unlimited?
No. Pay-as-you-go is a billing method, not a promise of unlimited throughput or spending.
Can a router remove limits?
No. Provider limits, organization policies and the router’s own terms still apply.