For years I said “API capability.” I have dropped the first word, because the emphasis on the API was holding the conversation back.
A capability is a definition of something you want to accomplish as part of business operations — as small as scheduling a calendar event or as large as a segment of a supply chain. It integrates data, functions, and possibly events. And it has one defining property: it must matter to technical and non-technical stakeholders alike.
That requirement is what makes it a governance and business-alignment concept rather than a technical one. “We have a customer API” means nothing to the person who runs the business. “We can verify a customer’s identity in under two seconds, in these markets, at this cost, with these constraints” is a capability, and everyone in the room can act on it.
Practically, thinking in capabilities changes what you catalog. Instead of an inventory of four hundred APIs, you get a map of what the business can actually do, with the APIs, events and data underneath each one. That map is what makes portfolio decisions possible — where you are duplicated, where you are missing something, what you could sell, what you should retire.
It is also, not coincidentally, exactly the unit an agent needs.
