We almost need the inverse: APIs that are showing signs of death ala Netflix. It's usually the case that you have an idea for something and an API is pretty easy to find. Getting your integration pulled out under your feet is really what sucks.
I'm working on APIs.json collections of deprecated APIs, as well as working on APIs.json references to building blocks like pricing, and TOS...then allow for inverse searching for APIs that do not have pricing, or have TOS that are not friendly. The next project after API Commons is to take TOS Didn't Read work and incorporate as part of APIs.json, so that APIs.io will have this type of data to search by.
Still, it's a risk often worth taking. If you look at many of the hypergrowth projects, a lot of them rely on a current market adopting their product as a supplement to a platform.
Comments
We almost need the inverse: APIs that are showing signs of death ala Netflix. It's usually the case that you have an idea for something and an API is pretty easy to find. Getting your integration pulled out under your feet is really what sucks.
I'm working on APIs.json collections of deprecated APIs, as well as working on APIs.json references to building blocks like pricing, and TOS...then allow for inverse searching for APIs that do not have pricing, or have TOS that are not friendly. The next project after API Commons is to take TOS Didn't Read work and incorporate as part of APIs.json, so that APIs.io will have this type of data to search by.
That's what happens when you build upon the shores of others.
Still, it's a risk often worth taking. If you look at many of the hypergrowth projects, a lot of them rely on a current market adopting their product as a supplement to a platform.