Hi angelxmoreno ,

We don't really care as long as you aren't tripping over the request rate limiting (I just moved the information about this on to the main docs, you can read it there).

The clause you mention here was put in before we had rate limiting as a precautionary measure to ensure we had a legal means to enforce usage. Since we have rate limiting in place now, the rate limits are basically what we consider to be reasonable.

A quick question to you Travis: I am currently dumping the database. Each time I make a movie request, If the movie id is a valid tmdb id, I make a request to movie cast and then for each cast and crew member, I make a person request plus company, keyword + trailer requests. Then the loop sleeps for 10 seconds before making an another call. So the number of requests/10 seconds really depends on how big the movie cast and crew is. I might break the 10 seconds rule with a couple of extra requests from movie to movie. Is this a problem?

I have done 2900 API requests the past hour.

Take a look at using the append_to_response parameter. You'll cut your requests down by a significant amount, in the movie example by 1/5.