rate limiting
Rate limiting is a technique that caps how many requests a user or program can send within a set period of time.
Rate limiting restricts the number of requests an API or web service accepts in a given time window, counted per user, API key, IP address or other unit. It protects servers from overload and abuse and shares capacity fairly among users. Requests over the limit are rejected or delayed, and HTTP services typically signal this with the 429 Too Many Requests status code.
AI model APIs commonly set limits on requests per minute and on the number of tokens processed. Common implementations use algorithms such as token bucket, fixed window and sliding window.
This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.
Articles covering this entry
The brainstorming agent read the project history, rate limits and configuration files in its own thread, and the main chat never froze.
…d as a halving, yet that shorthand combines different measures: an overall usage comparison, a GPT-6 Pro message cap and the removal of a short-term rate limit.
…t navigates, Webcmd builds persistent memory for the website’s domain: useful paths, page structures, shortcuts, request constraints, rate limits, and warnings.