Rate Limiting

Last updated @ June 21st, 2026

api.lanzoor.dev is protected by a multi-layer rate limiting system powered by @upstash/ratelimit. This helps prevent abuse and ensures service stability. Please respect the rate limits below to avoid getting blocked.

About Multi-Layered Rate Limits

In most cases, a rate limit preset comes with two rate limit layers.

• per second - Prevents rapid burst attacks and aggressive scripting.
• per minute - Prevents sustained spam and overuse.

Rate Limit Presets

Custom Rate Limits

Some routes may use a custom rate limit preset.If so, it will be clearly listed in the route's documentation, and the preset identifier custom will be used.

Headers

For now, rate limit headers are only included when a request is rejected with HTTP 429.

• X-RateLimit-Preset: The rate limit preset that applied to your request. (e.g: normal, paranoid, custom)
• X-RateLimit-Limit: Represents the maximum number of requests allowed within the window.
• X-RateLimit-Reset: Represents the Unix timestamp in milliseconds when the limits are reset.
• Retry-After: Represents how many seconds remain until the rate limit resets.

Example

Here's a simple example of how a rate limit and its headers would look like:

Reference

Please refer to the rate-limit.ts helper script.

Tips

• Implement exponential backoff if you're making multiple requests.
• Cache responses whenever possible.
• Respect the headers.