nomyo-ai/nomyo
2
1
Fork 0
Code Issues Pull requests Projects Releases 8 Packages Wiki Activity Actions

Rate Limits aktualisiert

Alpha Nerd 2026-04-13 21:03:53 +02:00
parent 150ca571c2
commit 2017d39a12
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
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 ## 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 ## 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 ## Rate Limit Summary
| Mode | Limit | Condition | | Mode | Limit | Condition |
|---------|--------------------|----------------------------------| |---------|--------------------|----------------------------------|
| Default | 2 requests/second | Always active | | Default | 1 requests/second | Always active |
| Burst | 4 requests/second | Once per 10-second window | | Burst | 2 requests/second | Twice per 10-second window |
## Error Responses ## Error Responses
@ -43,7 +43,7 @@ HTTP/1.1 503 Service Unavailable
## Best Practices ## 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. - **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. - **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. - **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.