Rate limits

Rate limits

Niyra rate-limits per token using a sliding-window counter. Each token (OAuth access token or PAT) has its own budget — multiple tokens for the same user don't share a window.

Default limits

| Endpoint family | Limit | Window |
| --------------- | ----- | ------ |
| niyraask | 60 requests | 1 minute |
| niyraexecute | 20 requests | 1 minute |
| niyramemories / niyraremember | 120 requests | 1 minute |
| niyragettask polling | 600 requests | 1 minute |

Alpha-plan users get 5× these limits. Pro users get 3×. Standard users get 1×.

Response headers

On every response, Niyra returns:

Reset is a Unix timestamp — when the current window rolls over.

On a 429:

Retry-After is in seconds. Honor it — Niyra tracks repeated immediate retries as abuse signal.

Backoff pattern

Polling etiquette

For niyragettask:

- Minimum interval: 3 seconds. Anything faster will 429 you out before it speeds the result.
- Backoff: if the task has been running for 60+ seconds, drop to 10s polls. Most long-running tasks take 1–5 minutes.
- Cap: poll for at most 10 minutes. Beyond that, surface the task ID to the user so they can check the dashboard.

Burst behavior

The sliding window is not a token bucket — there's no burst credit. Sending 60 requests in the first second of a minute will exhaust your budget for the rest of the window. Spread requests across the window.

Related

- niyraask
- niyraexecute
- niyragettask