Somewhere in your CRM right now, there’s probably a deal marked closed-lost, with a reason such as budget, or timing, or no decision. Somewhere in the back of your mind, you’re not entirely sure that’s what actually happened.
It’s a familiar pattern for anyone who’s sat through a win-loss review. The stated reason rarely tells the full story. Inspect more closely, and it often turns out the buyer had already formed a view of how you compare to the competitor they went with, built from whatever they could find publicly, well before your sales team got a real chance to shape it. Nobody flags that in the CRM, because nobody on the call realised it was happening until it was too late to do anything about it.
That’s the part worth sitting with.
Buyers aren’t doing anything sophisticated or unusual to get there. They’re reading documentation, checking what each platform actually claims about itself, comparing notes with a colleague who evaluated something similar last year. All public. All available to your own team too, if anyone had thought to gather it before the call rather than after the deal went quiet.
Sometimes a buyer finds a real gap: something on your product roadmap for a future release. Sometimes it’s the opposite: a strength you actually have, that your own sales team has rarely used as an advantage, because nobody flagged it as worth mentioning.
Either way, it points to the same uncomfortable question for anyone leading sales or product marketing right now:
Is it possible your prospective customers understand your position in the market better than you?
A Low Score Isn’t Always What It Looks Like
If that question makes you want to know your own answer, the honest next one is: would you actually know what a buyer finds if they went looking?
Most vendors haven’t checked. There’s rarely time, it doesn’t age well, and there’s no one obvious to keep it current. So the ranking happens without you rather than with you. If you did check and didn’t love what you saw, it’s worth knowing that a weak result doesn’t automatically mean a weak product. It could mean the capability genuinely isn’t there yet. It could mean the capability exists but it’s not yet publicly visible. Or the evidence is out there, but just too hard for a buyer to find in the time they have.
Those are three different problems, calling for three different approaches to tackle them. One is a product conversation. One is a documentation conversation. One is a positioning conversation. Knowing which one you’re facing is most of the battle, and it’s exactly what most teams are currently guessing at rather than working from evidence.
This is what The State of API Management was built to answer. It draws on years I’ve spent assessing API service providers through the lens of technology, business and politics, shaped into a structured score — the Kin Score — that looks at contract quality, developer ergonomics, commercial clarity, operational transparency, governance and discoverability, with agent readiness scored on its own separate axis, across thirty-five API management platforms, gateways and data planes in 2026.
The Stakes Are Rising With AI
It’s more important now than ever because the ground is shifting under the whole market. Buyers aren’t only assessing whether a product’s API foundations are solid anymore. They’re starting to ask whether platform providers are really thinking ahead about how AI agents will discover, understand and use APIs, including through things like Model Context Protocol (MCP) and Agent Skills.
It’s a new layer of scrutiny, and the report found five agentic primitives where the score across the entire market comes back at absolute zero — idempotency, consent and delegated identity, agent cards, dry-run mode, and a .well-known catalog, each at zero out of thirty-five vendors. As above, a zero doesn’t necessarily mean the capability is missing. It might just mean nobody can find proof that it exists. Either way, if a buyer can’t see it, it isn’t influencing their decision, no matter how real it is on your side.
Apigee, Boomi, MuleSoft, Amazon API Gateway, Zuplo, Apidog and Azure API Management stand out in the report as exemplars, not because they talk about strong API practices, but because they demonstrate them through evidence anyone can actually go and check. That’s really the whole game. The gap between what’s true about your platform and what’s visible about it is where deals get lost, and where advantages sit unused.
Before Someone Else Tells You Where You Stand
The State of API Management gives sales, product marketing, product and leadership teams a shared, evidence-based starting point, whichever side of that gap you’re working on. It includes the full scoring breakdown, the reasoning behind it and a data bundle you can bring into your own tools to check the findings yourself. You can see exactly what’s included on the report page.
Before your next prospective customer forms their own view of where you stand, it might be worth forming yours first. See what’s in the report.
