[Resource]: OpenClaw Rate Limit Manager

[AtlasPA]

Display Name

OpenClaw Rate Limit Manager

Category

Tooling

Sub-Category

Tooling: Usage Monitors

Primary Link

https://github.com/AtlasPA/openclaw-rate-limit-manager

Author Name

AtlasPA

Author Link

https://github.com/AtlasPA

License

MIT

Description

Proactive rate limit management for OpenClaw agents - prevents 429 errors with sliding windows (per-minute/hour/day), request queuing, and pattern learning. Free tier: 100 req/min basic limiting. Pro tier (0.5 USDT/month): unlimited with queuing, pattern detection, and custom limits. Includes CLI with 7 commands and REST API dashboard on port 9094.

Validate Claims

1. Install the tool: cd ~/.openclaw && git clone https://github.com/AtlasPA/openclaw-rate-limit-manager.git && cd openclaw-rate-limit-manager && npm install && npm run setup
2. Start the dashboard: npm run dashboard (runs on http://localhost:9094)
3. Check rate limit status: node src/cli.js status --wallet 0xTestWallet
4. The tool will show current rate limits, active windows, and usage statistics
5. Make multiple rapid API calls through OpenClaw tools and observe the rate limiting in action

Specific Task(s)

Install the OpenClaw Rate Limit Manager and make it track API calls from other OpenClaw tools (Cost Governor, Smart Router, etc.). Observe how it prevents rate limit violations across multiple providers.

Specific Prompt(s)

"Install the OpenClaw Rate Limit Manager from ~/.openclaw/openclaw-rate-limit-manager and show me my current rate limit status. Then check the dashboard at http://localhost:9094 to see the sliding window tracking."

Additional Comments

This is part of the OpenClaw ecosystem (5 tools total: Cost Governor, Memory System, Context Optimizer, Smart Router, and Rate Limit Manager). All tools use the same x402 payment protocol for Pro tier subscriptions and follow consistent architectural patterns. The Rate Limit Manager sits in the provider-before hook to prevent rate-limited requests before they reach the API.

Recommendation Checklist

• I have checked that this resource hasn't already been submitted
• My resource provides genuine value to Claude Code users, and any risks are clearly stated
• All provided links are working and publicly accessible
• I am submitting only ONE resource in this issue
• I understand that low-quality or duplicate submissions may be rejected

[github-actions]

⚠️ This issue appears to be a resource recommendation

Thank you for your interest in contributing to Awesome Claude Code!

However, resource recommendations must be submitted using our official issue template to be processed correctly.

Why this matters:

• The template ensures all required information is collected
• Automated validation can only process properly-formatted submissions
• Missing fields will cause your submission to be skipped

Next steps:

1. Make sure you have read the CONTRIBUTING.md document.
2. Click here to submit using the correct template
3. Fill out all required fields

If this issue is not a resource recommendation, please comment below and we'll reopen it.

---

*This issue has been automatically closed.