Offering an API is great. Just don't expect developers to voluntarily restrain their use of the API according to some words you put on a web page. Maybe most

Offering an API is great. Just don't expect developers to voluntarily restrain their use of the API according to some words you put on a web page. Maybe most will do so, but a significant portion will growth-hack their way right past whatever policy they agreed to. If you don't want someone to do something with your API, you better make it impossible to accomplish using said API. The problem is in offering an API that makes abuse trivially simple and putting all of your faith in the "click agree" model of expecting developers to (a) understand and (b) actually comply with your policy. Particularly when many of the developers in question are non-native English speakers, or even if they are native speakers and don't bother to read the policy carefully.