Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsAPI Rate Limiter Designer
Rate limiting fails in two directions: too loose and one bad client takes down the database for everyone; too crude and you rate-limit your own legitimate power users into churn.
$8.99
API Rate Limiter Designer
Example session with this skill installed
We expose a public REST API for a geocoding product with free, pro and enterprise plans. Traffic goes through nginx to Node services, and we already run Redis. Free users are hammering the batch endpoint. Design our rate limiting.
- Read your context and instructions
- Compiled the api rate limiter
Rate limiting design: token bucket in Redis, keyed by API key, tiered per plan, with a separate stricter limit on the batch endpoint.
Algorithm
- Token bucket via an atomic Redis Lua script: allows short bursts, enforces a steady rate.
- nginx
limit_reqper IP as a coarse outer guard against unauthenticated floods.
Limit keys
| Scope | Key |
|---|---|
| Authenticated | rl:{api_key}:{endpoint_group} |
| Unauthenticated | rl:ip:{ip} |
| Batch cost | tokens charged per address in the batch, not per request |
Tier structure
| Plan | Standard rate | Burst | Batch |
|---|---|---|---|
| Free | 5 req/s | 20 | 100 addresses/min |
| Pro | 50 req/s | 200 | 5,000 addresses/min |
| Enterprise | Contracted | Contracted | Contracted |
Values are starting points to tune against your capacity.
429 and headers
HTTP/1.1 429 Too Many Requests
RateLimit-Limit: 5
RateLimit-Remaining: 0
RateLimit-Reset: 3
Retry-After: 3
{"error":"rate_limited","limit_scope":"batch"}
Send the RateLimit-* headers on every response, not only on 429.
Monitoring
- Count 429s by plan, key and endpoint group.
- Alert when one key produces most of the 429s or Redis script latency rises.
- Fail open with a local in-memory limit if Redis is unreachable.
Next steps
- Publish the limits in your API docs before enforcing them.
- Roll out in log-only mode for a week, then enforce.
Connects securely to your tools. The creator never sees your data.
About this skill
Rate limiting fails in two directions: too loose and one bad client takes down the database for everyone; too crude and you rate-limit your own legitimate power users into churn. This skill designs your rate limiting strategy end-to-end: the right algorithm for your use case (token bucket vs. sliding window vs. fixed window and why it matters), the right granularity (per IP, per user, per API key, per endpoint — not all the same), Redis implementation that doesn't add latency on every request, the response format that doesn't enrage developers, and the exemption system for your high-trust clients. It also covers the abuse patterns rate limiting doesn't stop, so you're not surprised when someone routes around it. Give it your API shape, your traffic patterns, and your abuse concerns; it returns a rate limiting design you can implement in a day.
- Focuses on design and strategy over writing production-ready infrastructure code.
- Does not provide real-time traffic monitoring or automated threshold tuning.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 months ago
Permissions
No special permissions declared or detected