Developer Platform & API Ecosystem Management › Public API Lifecycle Management

Public API Lifecycle Management

BC-4270.10 Level 2 Software & Technology 18 providers 33 API surfaces 8 rated strong or better

Specification, versioning, and deprecation of public APIs exposed to external developers.

Public API Lifecycle Management (BC-4270.10) is a level-2 business capability under Developer Platform & API Ecosystem Management in the Software & Technology model. The catalog holds 33 API surface(s) from 18 provider(s) that can perform some part of it, 8 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

API Specification Authoring BC-4270.10.10

Authoring and review of public API specifications in machine- readable form.

no catalog coverage

API Versioning BC-4270.10.20

Versioning of public APIs with documented compatibility guarantees.

no catalog coverage

API Deprecation Management BC-4270.10.30

Communication and execution of API deprecations with adequate notice.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 3 Complete, well-documented, and agent-ready
KongAPI Package SpecificationAPI SpecificationAPI Version3 APIs73.2ApigeeAPI DeploymentsAPI SpecsAPI VersionsSpecs5 APIs70.8Amazon API GatewayREST APIs1 API70.0
Strong 5 Solid coverage with minor gaps
API EvangelistGovernance1 API66.2GraviteeAPIs1 API65.2RoutebaseAPI Specs1 API64.3TykAPIsOAS APIsTykTyk OAS APIs4 APIs64.0NetcrackerOperation groupsOperationsPublish3 APIs57.4
Developing 6 Usable, with meaningful gaps to close
Google Cloud API GatewayProjects1 API50.0SwaggerHubAPIsDomains2 APIs50.03GPPAPF published APIs (Collection)Individual APF published API (Document)2 APIs45.8Google Cloud EndpointsServices1 API42.8SidekoAPI ProjectsAPI Versions2 APIs41.9SAP API ManagementAPI Proxies1 API40.0
Thin 3 Limited public surface area
APIIDAVersions1 API32.9Software AGAPIs1 API32.6API-FiddleSpecifications1 API30.8
Emerging 1 Early or largely undocumented
Deutsche TelekomApiChangelogApiSpecification2 APIs26.0
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Public API Lifecycle Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →