From 2017d39a1244c493eb29e24cbbdf856f2923c8b4 Mon Sep 17 00:00:00 2001 From: Alpha Nerd Date: Mon, 13 Apr 2026 21:03:53 +0200 Subject: [PATCH] Rate Limits aktualisiert --- Rate-Limits.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Rate-Limits.md b/Rate-Limits.md index 38cfedc..15ace13 100644 --- a/Rate-Limits.md +++ b/Rate-Limits.md @@ -4,20 +4,20 @@ The NOMYO API (`api.nomyo.ai`) enforces rate limits to ensure fair usage and ser ## Default Rate Limit -By default, each API key is limited to **2 requests per second**. +By default, each API key is limited to **1 requests per second**. ## Burst Allowance -Short bursts above the default limit are permitted. You may send up to **4 requests per second** in burst mode, provided you have not exceeded burst usage within the current **10-second window**. +Short bursts above the default limit are permitted. You may send up to **2 requests per second** in burst mode, provided you have not exceeded burst usage within the current **10-second window**. -Burst capacity is granted once per 10-second window. If you consume the burst allowance, you must wait for the window to reset before burst is available again. +Burst capacity is granted twice per 10-second window. If you consume the burst allowance, you must wait for the window to reset before burst is available again. ## Rate Limit Summary | Mode | Limit | Condition | |---------|--------------------|----------------------------------| -| Default | 2 requests/second | Always active | -| Burst | 4 requests/second | Once per 10-second window | +| Default | 1 requests/second | Always active | +| Burst | 2 requests/second | Twice per 10-second window | ## Error Responses @@ -43,7 +43,7 @@ HTTP/1.1 503 Service Unavailable ## Best Practices -- **Throttle your requests** client-side to stay at or below 2 requests/second under normal load. +- **Throttle your requests** client-side to stay at ~1 requests/second under normal load. - **Use burst sparingly** — it is intended for occasional spikes, not sustained high-throughput usage. - **Implement exponential backoff** when you receive a `429` response. Start with a short delay (e.g. 500 ms) and double it on each subsequent failure, up to a reasonable maximum. - **Monitor for `503` responses** — repeated occurrences indicate that your usage pattern is triggering the abuse threshold. Refactor your request logic before the cool-down expires.