The State of API Management

About this paper

API management is the software other companies buy so that their APIs will be well-run. It sells contracts, governance, developer portals, rate limiting, analytics and lifecycle discipline. More than any other market in the catalog, it sells API practice itself — which makes it the one market where a gap between what a vendor sells and what a vendor publishes is not an interesting irony. It is a product defect.

API management is also a fuzzy category, and no automated rule draws its edge correctly. A tag match returns six companies; a loose read stops being about API management at all. So this cohort is 35 vendors named by hand — 20 platforms that sell the whole lifecycle as one product, and 15 gateways, ingress controllers and data planes that sit in front of an API. Developer portals, documentation, metering, analytics, API security and service mesh are real adjacent markets, and each is covered in its own area rather than folded in here.

The answer arrives in two halves. This market is genuinely excellent: it averages 52.3 against a whole-catalog average of 22.6, puts 85.7% of its vendors in the upper three bands against 19.1% catalog-wide, and lands not one in the Minimal band where 42.7% of the catalog sits.

And then five clean zeros. Idempotency 0 of 35. Consent and delegated identity 0 of 35. Agent card 0 of 35. Dry-run mode 0 of 35. A .well-known catalog 0 of 35. Not low — nobody, in the market that sells the control plane where all five would be implemented for everyone else. The highest-scoring vendor in the market is also the one with the widest agent gap: Apigee, at 74.0 on the composite and 30.6 on agents. Six of thirty-five publish OAuth scopes and zero gateways publish any. Eight vendors sell MCP as a product capability and not one runs an MCP server for its own control plane.

This is the first Area Market Report — the first cut of the catalog by what an API does rather than who it sells to. The full report maps the suite-versus-data-plane split, the self-referential taxonomy, and the facet and dimension data behind every number above. It covers the standards layer, where this cohort is itself the standards body. And it closes on a provenance audit of a score with two authors: where these numbers rest on a catalog API Evangelist actively improves, why that balance is deliberate, and which numbers only a vendor can move.

What's inside

1. Executive summary — scoring API Evangelist's own neighbourhood
2. The state of the market — what stayed when the product unbundled
3. The resource taxonomy — a market that models itself
4. The composite Kin Score — and the ergonomics finding
5. Agent readiness — and five clean zeros
6. The blueprint — what the leaders satisfy, and what nobody does
7. Provenance — a score with two authors
8. The standards layer — when the cohort IS the standards body
9. The regulatory layer — the first market to fail to adopt its own standard
10. Artifacts for the agentic turn
11. Security, authentication, scopes
12. Vendor-by-vendor intelligence
13. The investable thesis
14. Where this is going

What you get for $500.00