What Are the Base APIs That Should Be Common?

These are APIs for the most common resources that are essentially API commodities. These are the APis we shouldn't be competing upon and should just exist, allowing for standardization and interoperability when it comes to the most fundamental building blocks of our applications..

	Accounts - We need an account for everything these days, and if you are a developer you likely have many accounts associated with your APIs. This business of APIs is the first place we should be standardizing and stopping reinventing the wheels and be utilizing the same base account API for every new service we launch, helping streamlining onboarding of users and API consumer accounts.	More Info
	Images API - Images have been done, and there is no reason we shouldn't all be using the same image API for all of the base images of our applications. A common images API would go a long way towards helping companies focus on what they do best, and not reinventing the wheel, while also promoting interoperability.	More Info
	Train Travel - The Train Travel OpenAPI example from Bump.sh, providing a real world example of an API that can be used as a baseline for your API. It is a modern, realistic, and functional API that provides a rich starting point for anyone learning OpenAPI and looking to apply to their own APIs.	More Info
	Videos API - Videos have been done, and there is no reason we shouldn't all be using the same image API for all of the base videos of our applications. A common videos API would go a long way towards helping companies focus on what they do best, and not reinventing the wheel, while also promoting interoperability.	More Info