At Quicknode, we understand the importance of ensuring that our customers' applications remain responsive and available at all times. That's why we have implemented a credit-per-second (RPS) limit based on your pricing plan -- Pricing page, New Pricing and Plans

Exceeding this limit will result in a 429 Error,429 Client Error: Too Many Requests. You can view these errors on your Metrics (Endpoints > endpoint-name-example > Metrics)

Remember that batching also counts as CPS because each request is counted individually. Please refer to this link regarding API credit for each call. 

Preventing the error

You can deal with these 429 errors in many different ways:

1. Monitor the RPS usage: benchmark your code and adjust accordingly;
2. Implement a backoff logic: when experiencing the 429 error, wait a period of time before resuming;
3. Use a third-party package to throttle based on a fixed number, such as
   • https://pypi.org/project/ratelimit/
   • https://www.npmjs.com/package/axios-rate-limit
   • https://github.com/uber-go/ratelimit