AI and Rate Limit Headers: Don't Get Blocked

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-builders-ai-coding-AI-and-rate-limit-bypasses-r6

1. What HTTP status code does a server return when you've sent too many requests in a short time?

   1. 200 OK
   2. 500 Internal Server Error
   3. 404 Not Found
   4. 429 Too Many Requests

2. What does the X-RateLimit-Remaining header tell you?

   1. How many requests you can still make before being blocked
   2. The exact time when the rate limit will reset
   3. The server's current processing load
   4. The total number of requests allowed per hour

3. You receive a 429 response. What should your code do next?

   1. Retry immediately with the same request
   2. Retry immediately with more data
   3. Give up and stop making requests entirely
   4. Wait and then retry the request

4. What is 'exponential backoff'?

   1. Using multiple servers at once
   2. Sending requests in alphabetical order
   3. Increasing your request speed gradually
   4. Waiting longer between each retry attempt

5. What does adding 'jitter' to a backoff strategy do?

   1. Adds randomness to the wait time to avoid thundering herd
   2. Guarantees you'll never get blocked
   3. Makes every retry take exactly the same time
   4. Removes the exponential growth

6. What is the purpose of the Retry-After header in an API response?

   1. It tells you which endpoint to call next
   2. It lists all rate limits for all endpoints
   3. It indicates how long to wait before retrying
   4. It provides a new API key for your app

7. Why is retrying immediately after a 429 a bad idea?

   1. It will delete your rate limit headers
   2. You'll likely hit the limit again and worsen the problem
   3. It wastes your API quota
   4. The server will remember and ban you forever

8. What is a token bucket limiter?

   1. A type of authentication
   2. A client-side method to stay under the rate limit
   3. A way to store retry attempts
   4. A bucket that collects API keys

9. What information does X-RateLimit-Limit provide?

   1. When your limit will reset
   2. Your current API key
   3. The maximum number of requests allowed in the time window
   4. How many requests you've used so far

10. The lesson compares 'script kid' to 'professional API consumer.' What's the key difference?

    1. Professionals use paid APIs
    2. Professionals never get 429 errors
    3. Script kids use Python, professionals use JavaScript
    4. Professionals read and respect rate limit headers

11. If the X-RateLimit-Remaining header shows 5 and your application needs to make 20 more requests, what's the best approach?

    1. Modify your code to batch requests or add delays
    2. Switch to a different API
    3. Send all 20 requests at once
    4. Wait until the limit resets before making more requests

12. What happens when you 'hammer' an API (send many rapid requests)?

    1. The server may block you with a 429
    2. You get faster responses
    3. The API gives you bonus requests
    4. Your requests are automatically prioritized

13. Which header would tell you when the rate limit window resets?

    1. X-RateLimit-Limit
    2. X-RateLimit-Remaining
    3. X-RateLimit-Reset
    4. X-RateLimit-Window

14. What is the main benefit of using exponential backoff over fixed delays between retries?

    1. It adapts to server load and reduces repeated failures
    2. It works on all networks
    3. It uses less memory
    4. It's faster overall

15. What's wrong with this approach: request fails with 429, so immediately try again 10 times?

    1. Nothing, this is the best strategy
    2. It will likely result in more 429s and longer waits
    3. The server will give you a faster response
    4. You will get more API credits