Updated
Updated · InfoWorld · Oct 26
Kong Launches Context Mesh for Enterprise APIs, Cutting Agent Token Use by 99%
Updated
Updated · InfoWorld · Oct 26

Kong Launches Context Mesh for Enterprise APIs, Cutting Agent Token Use by 99%

3 articles · Updated · InfoWorld · Oct 26

Summary

  • Kong made Context Mesh generally available within Kong AI Management, positioning it as a way to make thousands of enterprise APIs usable by AI agents without exposing one MCP tool per endpoint.
  • A code-mode approach underpins the product: agents write short SDK-like code against APIs, fetch schemas on demand and return only final results, which Kong says cut one workflow’s token use to about 1,200 from 120,000.
  • Kong argues the older one-tool-per-operation MCP pattern breaks down on large CRM and ERP estates because hundreds of tools raise costs, slow responses and worsen tool selection accuracy.
  • The system routes agent traffic through Kong AI Gateway so existing authentication, authorization, rate limits and audit logging still apply, while a central catalog lets teams reuse agent-ready interfaces.
  • Kong says platform teams can compose one scoped context surface per agent from internal APIs, existing MCP servers and enterprise data sources, limiting access to only the systems each job requires.

Insights

Can sandboxed code execution truly secure enterprise APIs from rogue AI agents, or does it just mask deeper vulnerabilities?
If AI agents write their own integration code on the fly, who takes the blame when an enterprise workflow fails?
Will the rapid expansion of LLM context windows eventually render these complex API workarounds completely obsolete?