429 Too Many Requests / Rate Limit Exceeded
Error: 429 Too Many Requests / rate_limit_exceeded / Rate limit reached for model
OpenClaw troubleshooting · Updated 2026
Error Message
Error: 429 Too Many Requests / rate_limit_exceeded / Rate limit reached for model
What Causes This
You've exceeded your API provider's request quota. Rate limits apply across three dimensions simultaneously: requests per minute, input tokens per minute, and output tokens per minute. Hitting any one of them triggers a 429.
How to Fix It
Wait briefly and reduce request frequency:
# Check your current usage
openclaw status --usage
# Immediate fix: wait 60 seconds, then retry
# The API returns a retry-after header
# Long-term fixes:
# 1. Use a cheaper model for heartbeat/cron
openclaw config set agents.defaults.heartbeat.model "google/gemini-2.5-flash-lite"
# 2. Add fallback models so OpenClaw auto-rotates
# In openclaw.json:
# agent.model.fallbacks: ["openrouter/deepseek/deepseek-chat"]
# 3. Increase your API tier by adding credits
# Anthropic: platform.claude.com → Billing
# OpenRouter: openrouter.ai → Settings → API Keys → Limit
Free-tier models are especially prone to rate limits. If this happens during sub-agent work or heavy cron usage, switch those tasks to a different provider.