Yes he can complain, and bombarding a free service for unlimited requests isn't okay.
For starters because the people doing that, will usually be among the first to cry when the free service stops being free, blocks their requests or suddenly requires an API key.
Hummmm.... OP's website on https://getjsonip.com/ says:
> Supports unlimited requests and is free.
Seems like we have a bit of a contradiction here.
There's something about reasonability and fair-use and use over time going on here, but I just can't put my finger on it.
For example here's the Backblaze team verifying that their unlimited personal backup is indeed unlimited, with one single user storing 430TB for $6/month. The users spending $6/month who use a couple GB more than offset the cost of the 430TB guy. If your business model doesn't support the ability to get in the black, you have a failing business. This isn't the user's responsibility to fix, it's the failing service with a bad business model.
> As you can see, we lose money on a few customers at the high end (we cannot store 430TB of data for only $6/month), but since more customers just want to be reasonable and backup their laptops we are profitable and fully sustainable on the "average"
> Somebody who is costing Backblaze $2,150/month and is only paying $6/month :-)
https://www.reddit.com/r/IAmA/comments/b6lbew/comment/ejlbsq...
There is a difference between gracefully and responsibly using something that is offered for free, and just bombarding it with requests like no tomorrow.
People can of course do the latter. But then they don't get to complain when at some point, the available offerings present walls of legalese instead of a few simple and clear statements, and the user experience goes from seamless and easy to "Click here to register an API Key"
One thing is to own a service that's used by 10 MAU and you extend the service with a job that calls the OP's service 100 times a second. That's bad, you are using way more than you need.
Another thing is to own a mobile app used by 10M MAU and you embed the OP's service into the app. That's not bad intention, you just added a new service to your app. The problem is that the OP's definition of "unlimited" is not really unlimited.
No difference here.