I want us to evaluate an API before we build on it, because the cheapest time to discover a bad dependency is before it is wired into production. That means running third-party APIs through a procurement evaluation checklist so we judge them on real criteria instead of a demo, maintaining an SBOM so we understand what we are actually pulling in and what it depends on, and applying reuse scoring so we favor what we already have and adopt deliberately rather than accumulating redundant integrations. Too many dependencies enter through the back door with no scrutiny, and we pay for that later in security, cost, and lock-in. For the business this is disciplined procurement that reduces risk and duplication, and for the teams doing the building it replaces gut-feel adoption with a decision they can stand behind.
APIs Are Evaluated Before Adoption
Policies
Procurement Evaluation Checklist
Require that every API considered for adoption be run through a documented procurement evaluation checklist before a team commits to it. I want the same questions asked each time, covering security...
Dependency SBOM Maintained
Require that every API maintain a current software bill of materials enumerating the libraries, services, and versions it depends on. I want a machine-readable SBOM and dependency manifest kept in ...
Reuse Scoring Applied
Require that every API carry a reuse score that measures how widely and effectively it is being reused across teams and how much it duplicates existing capabilities. I want reuse assessed with a co...
Experiences
Procurement
Procurement is the experience of evaluating and adopting an API before building on it. Whether the API comes from another team or a third-party vendor, someone has to weigh its quality, reliability...
Reuse
The reuse of APIs in applications and integrations, but also in the producing of APIs plays an important part in the overall experience of teams who are producing and consuming APIs. The reuse of A...
Quality
The quality of HTTP APIs powering an enterprise tends to decline as the number of ungoverned APIs grows across internal, partner, and public landscapes. Low-quality APIs lead to poor downstream exp...
Governance
Governance is the experience of keeping API operations consistent and aligned as they scale across teams and time. It is the discipline that connects strategy at the top to the rules being enforced...
