Kong indexes at apis.io/providers/kong/ with 139 APIs and 132 API specifications, a Kin Score of 63.4 (strong), and an Agent Readiness score of 59.6 in the agent-ready band.
Kong describes itself as the AI Connectivity Company. Its platform spans Kong Gateway — the open-source API gateway built on NGINX and Lua — and Konnect, the managed control plane above it.
What’s in the surface
The catalog resolves Kong into two open collections, and that spareness is itself the architecture:
- Kong Enterprise Admin API — the gateway’s own control surface: routes, services, plugins, consumers, certificates
- Konnect Platform API — the SaaS control plane spanning multiple gateway deployments
Two collections across 139 APIs is the coarsest decomposition in this week’s sweep — the opposite end of the spectrum from Slack’s 32. It reflects a product where there genuinely are only two surfaces: the thing running in your cluster, and the thing managing the things running in your clusters.
The company that sells API management, scoring 63.4
This is the interesting tension. Kong’s business is helping other companies run their APIs well. Its own composite is strong, not exemplar — below Adyen (77.8), Palo Alto (75.3), Merge (75.3), FactSet (73.5), and Slack (73.1) from this same week.
That is not a gotcha, and the reason is architectural rather than negligent.
An Admin API is a configuration surface, not a business surface. Its objects are routes, plugins, and upstreams — infrastructure primitives whose meaning is defined by the gateway’s runtime behaviour rather than by a domain model. Documenting “what a plugin does” is a runtime-semantics problem that a specification does not capture well. You can specify the shape of a plugin config object precisely and still not convey what enabling it does to traffic.
Compare Merge, profiled yesterday at 75.3, whose entire product is a published data model. Merge’s surface is inherently more specifiable.
The Gateway/Konnect split
The two-collection structure maps to a real decision Kong made: keep the data plane open-source and self-hostable, sell the control plane. The Admin API is what the community runs; the Konnect API is the commercial surface.
For an integrator that split matters more than any endpoint detail — it determines whether your automation targets a cluster you own or a service you subscribe to, and those have entirely different auth and availability models.
Takeaway
139 APIs, 132 specifications, two collections, and a strong-band score that reflects a genuine limit: configuration surfaces are harder to specify meaningfully than domain surfaces. The API management company scoring below the payments and security companies is a statement about what infrastructure APIs are, not about how seriously Kong takes them.
Browse it at apis.io/providers/kong/.