Never "bet the farm" building on top of an API / service / platform that you don't control. It's almost inevitable that it will come back to bite you. If it's just a side project, or just something you want to try and generate some passive revenue from, and you won't lose your shirt if you get shut down, then sure, go for it. But if this what you intend to be the next billion dollar thing, and you're hamstrung by being tied to someone else's API, I'd consider going in a different direction.
Just search HN for all the horror stories over the past few years where some promising service got screwed over by changes from upstream providers (Twitter, Craigslist, etc., etc., etc.).
This. I'm mainly giving advice in a "side-project, passive revenue" mindset because I assume doing anything else on top of someone else's api is nothing short of suicidal. Keep it low-key and manage your expectations and you'll be fine.
Just search HN for all the horror stories over the past few years where some promising service got screwed over by changes from upstream providers (Twitter, Craigslist, etc., etc., etc.).