As the API Evangelist I score roughly 25,000 providers on two independent instruments. My “”Kin Score”” is a 0–100 composite of governance fundamentals — contracts, documentation, security, support, operations, and a conditional regulatory layer that applies only to banking, health, payments, insurance, securities and government. Agent Readiness is a separate 0–100 rating across twelve dimensions, measuring whether an autonomous consumer can drive an API safely without a human filling in the gaps. The two are computed independently and never blended, which makes the relationship between them such an industry finding when it comes to cutting through the AI hype.

The finding is that readiness is a layer, and a layer does not rise above its foundation. The dimensions that separate the agent-native band from everyone else — idempotency, error semantics an agent can branch on, auth and consent clarity, rate-limit signalling — are not AI features. They are governance disciplines that were always supposed to be there, now load-bearing in a way they never were when a human developer was around to work around them. An agent does not consume an endpoint; it tries to complete a capability, and it fails at whichever contract in that chain is ungoverned.

Enterprises and startups are racing to deploy MCP servers and publish Agent Skills to meet this moment, but without a proper API foundation that is well designed and governed, we are just assembling a house of cards. With the Kin Score I intend to cut through the hype and show were the press releases and mandates are not aligned with the foundation in which enterprises have built their businesses over the last 25 years. It can be tough to make sense of which companies have a handle on this moment from the stories we are all being bombarded with, and as a storyteller, it is important to me that we are able to tell.

This session walks the rubric facet by facet, shows what each one becomes once an agent is the consumer, and reads the scored catalog for what actually moves readiness — including the negative finding that shipping an MCP server on top of an ungoverned API does not move the number, and in a governed portfolio makes things worse by handing agents a confident interface to an unreliable contract. Governance is shifting from an offensive strategy to a defensive one, and the foundation underneath your platform is what determines how much of the agentic era you can absorb.

Takeaways

• The governance facets that become load-bearing the moment an agent is the consumer instead of a developer, and why readiness is bounded by the least-governed contract in a capability path.
• Why agent readiness scored separately from governance is the only way to prove the dependency between them — and what the scored catalog says about how far most portfolios actually are.
• How to map capabilities to contracts to scores and get a defensible readiness number for your own estate, instead of a press release.