If your app is hitting a third party rate limit, you need to prevent your app from hitting their API as often. There are a number of ways to do this

1. You should upgrade your code to detect rate limits and prevent itself from over fetching. Rate limits are generally communicated by the x-rate-limit headers in the response which tells you how many more requests you can make.

There are fetch wrappers like Ky that implement this for you, so you can set a retry and it won't try again until the rate limit resets https://github.com/sindresorhus/ky

GitHub

GitHub - sindresorhus/ky: 🌳 Tiny & elegant JavaScript HTTP client based on the Fetch API

🌳 Tiny & elegant JavaScript HTTP client based on the Fetch API - sindresorhus/ky

2. Cache the results you get. If a dozen users come to your page at the same time, your app should only make one request to the third party API. If your app is a public dashboard, you can pre-render it with Incremental Static Revalidation. Add export const revalidate = 60 and your dashboard will only refresh once a minute

https://nextjs.org/docs/app/guides/incremental-static-regeneration

3. If you need to do more elaborate filtering, then you can mirror the data from the third party into your own database. Your app talks to your database, and you have some code that runs regularly to pull new data from the API. This is ideal especially if you have multiple sources you want to combine together

Hey @davidpui-9287, just checking in to see if you still need help with the Coingecko API rate limits or if you've found a solution. Let me know if that helps!