Enterprises with mature API governance, OpenAPI specs, and developer portals are best positioned for the agentic AI era. Kin Lane, API evangelist and co-founder of Naftiko, argues that MCP is simply a long-lived HTTP connection serving JSON — nothing fundamentally new — meaning organizations that already have clean API foundations, access controls, and documentation standards can reuse those assets directly. The key shift is directional: instead of exposing APIs outward to a small developer community, companies now face a flood of inbound AI agents. Those without API portals, governance structures, or context-engineered permissions will struggle with security and operational resilience. Lane's research across 300+ enterprises shows that consistent, compounding investment in API design and governance — not reactive trend-chasing — is what determines readiness for agentic AI adoption.

8m read timeFrom thenewstack.io
Post cover image
Table of contents
MCP is just an APIReversing the polarity of the neutron flowContext engineering as API designThe portal as a proxy for readinessIf you’re behind, you’re not outStay the course
83 Impressions