You got a 429 error or "rate limit reached." Here's which limit you hit, how long to wait, and how to stop it from happening again.
Your agent just stopped responding mid-conversation. The logs say "rate limit reached" or you're seeing HTTP 429 errors. Your first instinct is to try again. Don't. That makes it worse.
The OpenClaw rate limit error means you've sent too many API requests in too short a time. But here's what most people miss: there are three completely different rate limits that can trigger this error, each with a different cause and a different fix. Knowing which one you hit is the difference between waiting 60 seconds and spending an hour debugging.
What a rate limit error actually means
Your AI model provider (Anthropic, OpenAI, Google, DeepSeek) limits how many requests you can make per minute. When you exceed that limit, they reject the request with a 429 status code and a message telling you to slow down.
OpenClaw agents are especially prone to hitting rate limits because a single user action can generate multiple API calls. You send one message. The agent reads it, thinks about which tools to use, calls a tool, reads the result, thinks again, and generates a response. That's 3-5 API calls from one message. During complex tasks with multiple tool calls, a single request can generate 10+ API calls in rapid succession.
Multiply that by heartbeats (48 per day), cron jobs, and any concurrent conversations, and you can hit your provider's rate limit faster than you'd expect.
Which rate limit are you hitting? (there are three)
This is where most people get it wrong. They assume all rate limits are the same. They're not.
Provider rate limit (the most common)
This is the limit set by your AI model provider. Anthropic, OpenAI, Google, and others each have different rate limits based on your API tier. Free tiers have very low limits (sometimes 5-10 requests per minute). Paid tiers are higher but still finite.
How to identify it: The error message usually includes the provider's name or mentions "tokens per minute" (TPM) or "requests per minute" (RPM). Check your provider's dashboard for rate limit metrics.
Typical wait time: 60 seconds for most providers. Some reset on a rolling window. Anthropic and OpenAI both publish their rate limit tiers, and you can request increases by depositing more credits or contacting support.
OpenClaw's own request throttle
OpenClaw has internal throttling to prevent runaway loops from burning through your API credits. If your agent enters a loop (a skill errors, the agent retries, the skill errors again), OpenClaw eventually throttles the requests to protect you.
How to identify it: The error appears in OpenClaw's logs rather than the provider's response. The message references OpenClaw's internal limits rather than the provider name.
Typical wait time: This usually clears once the loop condition is resolved. Use the /new command to reset the session state and break the loop.
Skill-specific rate limits
Some skills (especially those that call external APIs like web search, email, or calendar) have their own rate limits independent of your model provider. A web search skill that calls a search API might be limited to 100 queries per day regardless of how many model API calls you have available.
How to identify it: The error references the specific skill or external service, not your model provider. The rest of your agent works fine, but one specific capability stops working.
Typical wait time: Varies by service. Some reset hourly, some daily.
For the full model provider comparison including rate limit tiers, our guide covers what each provider offers at different pricing levels.
Rate limit errors have three possible sources: your model provider, OpenClaw's internal throttle, and individual skills. The fix depends on which one you hit. Check the error message carefully before doing anything.
How to fix it right now
If you're staring at a rate limit error and need your agent working again, here are the immediate fixes in order of speed.
Wait 60 seconds. Most provider rate limits reset within a minute. The simplest fix is patience. Don't send repeated requests while rate-limited. Each failed retry counts against your limit and extends the cooldown.
Use /new to reset your session. If the rate limit was triggered by a long conversation (each message sending the entire conversation history), starting a fresh session with /new reduces the token volume per request. For the complete guide to how session length drives costs and rate limits, our API cost guide covers the mechanics.
Switch to a fallback provider temporarily. If your Anthropic key is rate-limited, switch to OpenAI or DeepSeek while the limit resets. Having a fallback provider configured means rate limits on one provider don't stop your agent entirely.
How to prevent rate limits from happening again
Prevention is cheaper than debugging.
Set up model routing with a fallback. Configure a primary provider (Claude Sonnet, for example) and a fallback provider (DeepSeek or Gemini Flash). When your primary hits a rate limit, the fallback handles requests until the limit resets. For the model routing configuration guide, our routing post covers the setup.
Manage your session length. Long conversations generate exponentially more tokens per message. By message 30, you're sending 20,000+ input tokens per request, which eats through your TPM (tokens per minute) limit faster. Using /new every 20-25 messages keeps your per-request token volume manageable and reduces how quickly you approach the limit.
Set maxIterations to 10-15. This prevents runaway loops that blast through your rate limit in seconds. Without iteration limits, a single buggy skill can generate 50+ API calls in a minute, burning through even generous rate limits.
Upgrade your provider tier. If you're hitting rate limits regularly during normal usage (not loops, not excessive sessions), your provider tier might be too low. Most providers offer higher limits when you add credits to your account or move to a paid tier.
If configuring fallback providers, iteration limits, and rate limit monitoring isn't how you want to spend your time, Better Claw includes model routing and health monitoring with auto-pause on anomalies. $29/month per agent, BYOK. Rate limit errors surface with clear explanations so you know which limit you hit and why.
When rate limits are actually a symptom of something bigger
Here's what nobody tells you about OpenClaw rate limits.
Sometimes the rate limit isn't the problem. It's the symptom. If your agent is hitting rate limits during normal, light usage, something else is wrong.
The most common hidden cause: your agent is stuck in a loop. A skill returns an error. The agent retries. The skill errors again. The agent retries harder. Each retry is an API call. A 10-iteration loop generates 10 API calls in 5 seconds. A loop without iteration limits generates 50+ calls in under a minute. That's enough to trigger rate limits on any provider tier.
For the complete guide to diagnosing and fixing agent loops, our loop troubleshooting post covers the specific patterns and fixes.
The second hidden cause: heartbeat frequency. OpenClaw sends heartbeat checks (roughly 48 per day by default). Each heartbeat is an API call. On the free tier of some providers, 48 heartbeats plus 20 conversations per day might exceed the daily or hourly limit. Route heartbeats to a cheap provider with generous limits (Haiku or DeepSeek) to keep your primary provider's rate limit budget available for actual conversations.
The rate limit error is your provider protecting you from excessive usage. The question is whether the usage is legitimate (you're just using the agent a lot) or wasteful (loops, bloated sessions, unoptimized heartbeats). Fix the waste first. Upgrade the tier second.
If you want rate limit monitoring, model routing, and loop detection handled automatically, give Better Claw a try. $29/month per agent, BYOK with 28+ providers. Health monitoring with auto-pause catches loops before they drain your rate limit budget. The infrastructure handles the edge cases so you don't debug them yourself.
Frequently Asked Questions
What does "rate limit reached" mean in OpenClaw?
It means you've sent more API requests to your model provider than they allow within a given time window. Most providers limit requests per minute (RPM) and tokens per minute (TPM). OpenClaw agents are especially prone to hitting these limits because a single user message can generate 3-10 API calls (reasoning, tool use, response generation). Wait 60 seconds for the limit to reset, then continue.
Which rate limit am I hitting in OpenClaw?
There are three possible sources: your model provider's rate limit (Anthropic, OpenAI, etc.), OpenClaw's internal request throttle (protects against runaway loops), and skill-specific rate limits (external APIs called by individual skills). Check the error message for the provider name or skill reference to identify which one. Provider limits reset in 60 seconds. OpenClaw throttle clears when the loop is resolved. Skill limits vary by service.
How do I fix an OpenClaw 429 error?
Immediate fix: wait 60 seconds and don't retry during the cooldown (retries extend the limit). If it keeps happening: use /new to reset your session (reduces token volume per request), configure a fallback model provider, and set maxIterations to 10-15 to prevent loops. If you're on a free API tier, upgrading to a paid tier significantly increases your rate limit allocation.
How do I prevent OpenClaw rate limits?
Four changes prevent most rate limit issues: configure model routing with a fallback provider so one provider's limit doesn't stop your agent, use /new every 20-25 messages to keep per-request token volume low, set maxIterations to 10-15 to prevent runaway loops, and route heartbeats to a cheap provider with generous rate limits. These changes reduce your API call volume by 40-60% without changing what your agent does.
Are rate limits different on free vs paid API tiers?
Significantly. Free tiers on most providers allow 5-20 requests per minute. Paid tiers (even at the lowest deposit level) typically allow 50-500+ requests per minute. Anthropic's rate limits increase with your spending tier. OpenAI's limits increase with account age and usage history. If you're hitting rate limits during normal usage with a paid tier, the issue is likely a loop or bloated session, not the tier itself.
Related Reading
- OpenClaw Agent Stuck in Loop: How to Fix It — The hidden cause behind most rate limit errors
- OpenClaw Session Length Is Costing You Money — How long sessions burn through your TPM limit
- OpenClaw Model Routing Guide — Set up fallback providers to survive rate limits
- Cheapest OpenClaw AI Providers — Provider comparison including rate limit tiers
- OpenClaw API Costs: What You'll Actually Pay — Full cost and usage breakdown by provider
