If you are selling services to the API space, you should have an API. It's just how this game works (if you are savvy). I was going through Tyk's API for their open-source API management solution and came across their API definitions API, which gives you a list of APIs for each Tyk deployment — baking in API discovery into the open-source API management solution by default.
The API API (I still enjoy saying that) gives you the authentication, paths, versioning, and other details about each API being managed. I'm writing about this because I think that an API API should be the default for all API service providers. If you are selling me API services, then you should have an API for all your services, especially one that allows me to discover and manage all the APIs I'm applying your service to.
I'm expanding my definition of a minimum viable blueprint for API service providers and adding an API API as one of the default APIs. I'm going to be adding the account, billing, and a handful of other essential APIs to my default definition. If I'm using your service to manage any part of my API operations, I need to be automating discovery, management, and billing in our relationship.
It seems obvious to me, but I'm looking to provide a simple checklist that other API service providers can consider as they craft their strategy. My goal is to help make sure each stop along the lifecycle can be orchestrated in a programmatic way like Tyk.