Rate limit math for Web3 nft endpoint with offsets

[moralis]

Sorry, I’m super confused by the offset weighing thing.

For web3 endpoint /nft/{address}/trades:

Pagination is available still only by offset, not yet by cursor, correct?

If each call returns an array with up to 500 entries, and assuming my nft collection’s entire trades dataset is 25,000 entries, that’d be 500 calls.

With each subsequent call, I increase the offset value by 500 to retrieve the next page. And there’s an associated weight change with each call, based on that call’s offset value?

So for this example, is there a way to calculate a constant rate limit that I can set my program to adhere to?

Or should I actually be increasing the time between calls as the offset increases?

Thank you.

[cryptokid]

NFT Endpoints Temporary Offset Rate Limit

At the moment we temporary restriction on some endpoints (like NFT endpoints) pagination while we scale the systems: The weight of the NFT endpoint that uses offset is calculated like this (offset/500)*5 if the result of the above calculation plus the weight of other requests you made the same second is above 60 - wait 1 second if more requests are sent before 1 second i over - wait 5 seconds these are temporary restrictions we had to put in place as we scale our systems and will be removed …

I would say that you can use a delay between requests that handles the biggest offset, or you can increment the delay based on the current offset.