Prompt · Developer Tools

Rate Limit Designer

Designs rate limiting for an API endpoint: algorithm, limits, and headers.

Have ready: Describe the endpoint, its traffic, and your abuse concerns

Fill in · 5 fields

METHOD + PATH, WHAT IT DOESCHEAP READ / EXPENSIVE COMPUTE / SENDS EMAIL, BE SPECIFICREQUESTS PER USER PER MINUTE/HOURSCRAPING / CREDENTIAL STUFFING / COST EXHAUSTION / SPAMFRAMEWORK + WHERE IT RUNS

Your prompt

Design rate limiting for this endpoint.

Endpoint: [METHOD + PATH, WHAT IT DOES]
Cost per request: [CHEAP READ / EXPENSIVE COMPUTE / SENDS EMAIL, BE SPECIFIC]
Expected legitimate traffic: [REQUESTS PER USER PER MINUTE/HOUR]
Abuse concern: [SCRAPING / CREDENTIAL STUFFING / COST EXHAUSTION / SPAM]
Stack: [FRAMEWORK + WHERE IT RUNS]

Deliver:
1. Algorithm choice (token bucket / fixed window / sliding window / leaky bucket) and why for THIS endpoint.
2. Concrete limits: per-IP, per-user, per-API-key tiers, with numbers and your reasoning.
3. Response contract: status code, Retry-After, and RateLimit-* headers with examples.
4. What happens on the frontend/client when limited, the UX.
5. How to exempt or elevate trusted clients, and how limits are stored (memory/Redis) with failure behavior if the store is down.

No generic advice, every number must be justified against my traffic profile.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Breaking Change Check

Caching Strategy

Edge Case Enumerator

Webhook Handler Template

Fixture Factory

Retry Logic Review