NEW: UNIFY AI AGENT SPEND, SECURITY & GOVERNANCE IN ONE PLACE KONG JOINS SERVICENOW CONTROL TOWER ALLIANCE GARTNER® NAMES KONG A LEADER FOR 7TH YEAR GET THE API + AI SUMMIT 2026 RECAP KONG NAMED A LEADER IN FORRESTER WAVE: API MANAGEMENT SOFTWARE
  • [Why Kong ](/company/why-kong)Why Kong
  • _API & AI CONNECTIVITY TECHNOLOGIES_
    The AI Connectivity Platform
    []
    API ManagementAI ManagementEvent ManagementMonetization
    Migration Services
    API Advisory Services + Forward Deployed EngineersNEW
    • RUNTIMES
    • [API Gateway ](/products/kong-gateway)API Gateway
    • [AI Gateway HOT](/products/kong-ai-gateway)AI Gateway HOT
    • [Event Gateway ](/products/event-gateway)Event Gateway
    • [Service Mesh ](/products/kong-mesh)Service Mesh
    • [Context Mesh ](/products/kong-konnect/features/context-mesh)Context Mesh
    • [Kong Operator ](/products/kong-operator)Kong Operator
    • [Webhook Engine ](/products/kong-webhook-engine)Webhook Engine
    • CORE SERVICES
    • [AI Registry NEW](/products/mcp-registry)AI Registry NEW
    • [Catalog ](/products/kong-konnect/features/api-service-catalog)Catalog
    • [APIOps & Automation ](/products/apiops-automation)APIOps & Automation
    • APPS & AI AGENTS
    • [Developer Portal ](/products/kong-konnect/features/developer-portal)Developer Portal
    • [Usage Billing & Metering ](/products/kong-konnect/features/usage-based-metering-and-billing)Usage Billing & Metering
    • [Observability ](/products/kong-konnect/features/api-observability)Observability
    • [KAi Agent ](/products/kong-konnect/features/kai-ai-agent)KAi Agent
    • [Identity & Access ](/products/governance-and-identity)Identity & Access
    • [AI Cost Management ](/products/ai-cost-management)AI Cost Management
    DEVELOPER TOOLS
    [Insomnia ](https://insomnia.rest/)Insomnia [Plugins ](https://developer.konghq.com/plugins/)Plugins [Volcano ](https://volcano.dev/)Volcano [Kong MCP ](https://developer.konghq.com/konnect-platform/konnect-mcp/)Kong MCP [Documentation ](https://docs.konghq.com/)Documentation [Open Source ](/community)Open Source
      • FOR PLATFORM TEAMS
      • [Developer Platform ](/solutions/building-developer-platform)Developer Platform
      • [Kubernetes and Microservices ](/solutions/build-on-kubernetes)Kubernetes and Microservices
      • [Observability ](/solutions/observability)Observability
      • [Service Mesh Connectivity ](/solutions/service-mesh-connectivity)Service Mesh Connectivity
      • [Kafka Event Streaming ](/solutions/kafka-stream-api-management)Kafka Event Streaming
      • FOR EXECUTIVES
      • [Open Banking ](/solutions/open-banking)Open Banking
      • [Legacy Migration ](/solutions/legacy-api-management-migration)Legacy Migration
      • [Platform Cost Reduction ](/solutions/api-platform-consolidation)Platform Cost Reduction
      • [Kafka Cost Optimization ](/solutions/reduce-kafka-cost)Kafka Cost Optimization
      • [API Monetization ](/solutions/api-monetization)API Monetization
      • [AI Monetization ](/solutions/ai-monetization)AI Monetization
      • FOR AI TEAMS
      • [AI-Native API Management ](/solutions/ai-native)AI-Native API Management
      • [Agent Gateway ](/agent-gateway)Agent Gateway
      • [Trigger Agents from Events ](/solutions/event-driven-ai-agents)Trigger Agents from Events
      • [AI Governance ](/solutions/ai-governance)AI Governance
      • [AI Security ](/solutions/ai-security)AI Security
      • [Token Cost Management ](/solutions/ai-cost-optimization-management)Token Cost Management
      • [Agentic Infrastructure ](/solutions/agentic-ai-workflows)Agentic Infrastructure
      • [MCP Production ](/solutions/mcp-production-and-consumption)MCP Production
      • [MCP Traffic Gateway ](/solutions/mcp-governance)MCP Traffic Gateway
      • FOR DEVELOPERS
      • [Mobile App API Development ](/solutions/mobile-application-api-development)Mobile App API Development
      • [GenAI App Development ](/solutions/power-openai-applications)GenAI App Development
      • [API Gateway for Istio ](/solutions/istio-gateway)API Gateway for Istio
      • [Decentralized Load Balancing ](/solutions/decentralized-load-balancing)Decentralized Load Balancing
      • BY INDUSTRY
      • [Financial Services ](/solutions/financial-services-industry)Financial Services
      • [Healthcare ](/solutions/healthcare)Healthcare
      • [Higher Education ](/solutions/api-platform-for-education-services)Higher Education
      • [Insurance ](/solutions/insurance)Insurance
      • [Manufacturing ](/solutions/manufacturing)Manufacturing
      • [Retail ](/solutions/retail)Retail
      • [Software & Technology ](/solutions/software-and-technology)Software & Technology
      • [Transportation ](/solutions/transportation-and-logistics)Transportation
    NEW
    Kong for Startups
    Apply for $100k credits & 50% off AI Gateway
  • [Pricing ](/pricing)Pricing
      • DOCUMENTATION
      • [Kong Konnect ](https://developer.konghq.com/konnect/)Kong Konnect
      • [Kong Gateway ](https://developer.konghq.com/gateway/)Kong Gateway
      • [Kong Mesh ](https://developer.konghq.com/mesh/)Kong Mesh
      • [Kong AI Gateway ](https://developer.konghq.com/ai-gateway/)Kong AI Gateway
      • [Kong Event Gateway ](https://developer.konghq.com/event-gateway/)Kong Event Gateway
      • [Kong Insomnia ](https://developer.konghq.com/insomnia/)Kong Insomnia
      • [Plugin Hub ](https://developer.konghq.com/plugins/)Plugin Hub
      • EXPLORE
      • [Blog ](/blog)Blog
      • [Customer Stories ](/customer-stories)Customer Stories
      • [Learning Center ](/blog/learning-center)Learning Center
      • [eBooks ](/resources/e-book)eBooks
      • [Reports ](/resources/reports)Reports
      • [Demos ](/resources/demos)Demos
      • [Videos ](/resources/videos)Videos
      • EVENTS
      • [API + AI Summit ](/events/conferences/api-ai-summit)API + AI Summit
      • [Webinars ](/events/webinars)Webinars
      • [User Calls ](/events/user-calls)User Calls
      • [Workshops ](/events/workshops)Workshops
      • [Meetups ](/events/meetups)Meetups
      • [See All Events ](/events)See All Events
      • FOR DEVELOPERS
      • [Engineering Blog ](/blog/engineering )Engineering Blog
      • [Get Started ](https://developer.konghq.com/)Get Started
      • [Community ](/community)Community
      • [Certification ](/academy/certification)Certification
      • [Training ](https://education.konghq.com)Training
      • COMPANY
      • [About Us ](/company)About Us
      • [We're Hiring! ](/company/careers)We're Hiring!
      • [Press Room ](/company/press-room)Press Room
      • [Contact Us ](/company/contact-us)Contact Us
      • [Kong Partner Program ](/partners)Kong Partner Program
      • [Enterprise Support Portal ](https://support.konghq.com/s/)Enterprise Support Portal
      • [Documentation ](https://developer.konghq.com)Documentation
  • [](/search)
  • [Login](https://cloud.konghq.com/login)Login
  • [Book Demo](/contact-sales)Book Demo
  • [Get Started](/products/kong-konnect/register)Get Started
[Blog](/blog)Blog
  • [AI Gateway ](/blog/tag/ai-gateway)AI Gateway
  • [AI Security ](/blog/tag/ai-security)AI Security
  • [AIOps ](/blog/tag/aiops)AIOps
  • [API Security ](/blog/tag/api-security)API Security
  • [API Gateway ](/blog/tag/api-gateway)API Gateway
|
    • [API Management ](/blog/tag/api-management)API Management
    • [API Development ](/blog/tag/api-development)API Development
    • [API Design ](/blog/tag/api-design)API Design
    • [Automation ](/blog/tag/automation)Automation
    • [Service Mesh ](/blog/tag/service-mesh)Service Mesh
    • [Insomnia ](/blog/tag/insomnia)Insomnia
    • [Event Gateway ](/blog/tag/event-gateway)Event Gateway
    • [View All Blogs ](/blog/page/1)View All Blogs
We're Entering the Age of AI Connectivity [Read more](/blog/news/the-age-of-ai-connectivity)Read moreProducts & Agents:
    • [Kong AI Gateway](/products/kong-ai-gateway)Kong AI Gateway
    • [Kong API Gateway](/products/kong-gateway)Kong API Gateway
    • [Kong Event Gateway](/products/event-gateway)Kong Event Gateway
    • [Kong Metering & Billing](/products/kong-konnect/features/usage-based-metering-and-billing)Kong Metering & Billing
    • [Kong Insomnia](/products/kong-insomnia)Kong Insomnia
    • [Kong Konnect](/products/kong-konnect)Kong Konnect
  • [Documentation](https://developer.konghq.com)Documentation
  • [Book Demo](/contact-sales)Book Demo
  1. Home
  2. Blog
  3. Enterprise
  4. AI Governance Roadmap: A 4-step plan To Stop Model, MCP, and Agent Sprawl
[AI Gateway](/blog/tag/ai-gateway)AI Gateway
November 18, 2026
10 min read

# AI Governance Roadmap: A 4-step plan To Stop Model, MCP, and Agent Sprawl

Kong

“How much are we spending on AI models?”

It's the question everyone dreads, and as a marketer, even I can't answer it. I can't list the models in use, the [MCP servers](https://konghq.com/blog/learning-center/what-is-an-mcp-server)MCP servers running on people's laptops, or the agents two teams built twice. That gap is a real risk, and it shows up in four places: cost, security and access control, visibility, and resilience.

The root cause of this blind spot is AI sprawl. Models, MCP servers, and agents multiply faster than anyone can track them, so nobody owns them, nobody can see them, and nobody can govern them. The fix is an AI governance roadmap, a sequenced plan for controlling every model, MCP server, agent, and API your AI systems connect to, so cost, security, visibility, and resilience hold up as AI moves from pilot to production.

Most teams should start with sprawl, because you can't govern what you can't see. Find what's running, consolidate duplicates into one registry, standardize how new assets get built, then curate access for people and agents. That's the four-step plan below, laid out so you can run it this quarter. First, a quick way to see where you stand.

Why a maturity model won't tell you where to start

Maturity models only go so far. Alex Drag, Head of Product Marketing at Kong, says:
"Maturity looks different for everyone. It depends on your business, your use cases, your challenges that you're trying to solve, what governance means to you. Two companies at the same stage can need opposite first moves.”

A model still earns its keep as a way to name where you are. Kong's AI Governance Maturity Model plots four stages against time, with a track for each phase of the work.

Use the table as a quick audit. Can you list every model your teams call today? Do you know which MCP servers are running, including the ones on developers' laptops? Does model traffic pass through one gateway, or through whichever API key someone pasted into a script? If you answered no to the first two, you're in Stage 1 or 2, and sprawl is your starting problem. If you want the broader definition first, Kong's explainer on [what AI governance is](https://konghq.com/blog/learning-center/what-is-ai-governance)what AI governance is covers it.

What makes AI governance viable? Four requirements

Every vendor now promises governance. But, the real question is whether one vendor can do all of it. So judge any plan, against these four requirements.

Assets. Most teams stop at model access and MCP servers. Drag warns that the larger context estate "must also be governed, or else you have massive gaps in governing access to certain resources." The context estate is MCP servers plus what feeds them. And MCP isn't the whole story, since "behind a majority of MCP servers is your API estate," and agents will still call APIs directly. Don't skip events either. In fact, eventing is "the source of the most up to date real time information" and the place where agents get triggered, which is where [Kong Event Gateway](https://konghq.com/products/event-gateway)Kong Event Gateway comes in.

Angles. "Governance can't just be security." In AI, cost belongs on the same list as access control, because token spend grows with every new agent.

Scale. As more of the business depends on models, your governance infrastructure "also cannot go down when demand spikes." A control point that fails under load turns a safety measure into the outage.

Workloads. Models, providers, and runtimes will change. According to Alex Drag's advice:
"you must build a strategy around portability."

What is AI sprawl? Three kinds, three different risks

AI sprawl is the growth of models, MCP servers, and agents that nobody has inventoried, owns, or controls. In a recent Kong poll, MCP sprawl ranked first, model sprawl second, and agent sprawl a close third. Each one fails in its own way.

Model sprawl

Having many models isn't the problem. The trouble starts when teams or agents call models directly, with no governance, visibility, or access-control layer in between. You can spot it with one question: how much are you spending on models? A common answer is: "we have no idea what models are being used. We find out about a new one every other day."

MCP sprawl

MCP servers spread fastest on laptops. "MCP is just proliferated everywhere, especially on things like local machines." Many of them sit on top of APIs or data stores, so an unmanaged server is an unmanaged door into your data and you open yourself up to massive security compliance risk.

There's a cost problem too. "MCP on its own is not very token efficient." Servers built inconsistently can flood a model with "too much context or outdated context," which burns tokens, slows responses, and hurts answer quality. Kong's engineering team shows gateway-level patterns for this in [MCP tool governance: security meets context efficiency](https://konghq.com/blog/engineering/mcp-tool-governance-security-meets-context-efficiency)MCP tool governance: security meets context efficiency.

Agent sprawl

Teams spin up agents for their own tasks, and nobody can count them. Duplicates follow, because nobody can see what already exists: "if there's an agent that already exists, but folks don't know that it exists, well, they're just gonna go build their own."

This is the API sprawl story again. Teams that couldn't find an existing API built a new one, and some ended up behind a gateway while others didn't. Kong's [MCP registry explainer](https://konghq.com/blog/learning-center/what-is-an-mcp-registry)MCP registry explainer draws the same line: it's the sprawl microservices had before API gateways, except now the consumers are autonomous agents.

How to fix AI sprawl: discover, consolidate, standardize, curate

The four steps build on each other. Each one produces the input the next one needs, so run them in order.

Step 1: Discover what's running

There are two ways to find AI assets. The first is shadow AI detection, which means watching network traffic or running an agent on machines to spot MCP servers and models in use. "There is a place for that, and we believe organizations should do that... But it's not the only long time durable solution."

The durable fix is to make assets visible by design: "put these things behind gateways, see and watch the traffic, and then start to build an inventory."

  • Route model, MCP, and agent traffic through a gateway such as [Kong AI Gateway](https://konghq.com/products/kong-ai-gateway)Kong AI Gateway, so every call leaves a record.
  • Run shadow AI detection once to catch what's already off the books. Kong's guide to [shadow AI detection](https://konghq.com/blog/enterprise/shadow-ai-detection-enterprise-governance)shadow AI detection is a good starting point.
  • Write each asset into a catalog or registry. A workable minimum: name, owner, what it connects to, and which teams call it.

Step 2: Consolidate the duplicates

Once the inventory exists, the waste shows up. You may find duplicate MCP servers, or one that "hasn't been built to deliver context in the most token efficient manner." The fix is to generate a better one, or reuse a token-efficient server that already exists, and then register it as "the approved MCP server for x, y, and z at the org."

  • Group inventory entries by function and flag overlaps.
  • Pick one approved server per function and record it in your registry. [Kong MCP Registry](https://konghq.com/blog/product-releases/kong-mcp-registry-tech-preview)Kong MCP Registry is built for this.
  • Open self-service discovery, registration, and consumption, for the humans building on these servers and for the agents consuming them.

Sprawl shrinks because there's less to sprawl, and the approved option becomes the easy one to find.

Step 3: Standardize how new assets get built

This is where MCP servers go wrong most often. As per Drag's rule: don't throw "every single API endpoint for every API as a tool at an MCP server." It's "very token inefficient," and it makes the model parse every endpoint when the agent needs one or two. He named four techniques:

  • Progressive tool disclosure. Kong's code mode exposes only the tools that match the intent of the prompt.
  • Multi-API server generation. One MCP server exposes selected endpoints across several APIs.
  • Composite MCP servers. One interface sits on top of several MCP servers. For example, there can be a single software-development-lifecycle server in front of servers like GitHub, so those agents hit one endpoint.
  • Tool filtering and access control. Each agent or user sees only the tools they're cleared to use.

A good generation method isn't enough on its own. When someone creates an API and wants an MCP server for it, policy should force the approved generation path. Kong's [MCP Traffic Gateway](https://konghq.com/solutions/mcp-governance)MCP Traffic Gateway covers the traffic side of this.

Step 4: Curate access

Now you hold what Drag calls the "gold standard governed inventory of consistent standardized MCP servers." The last step is opening it to the wider agent estate, with something like a developer portal.

  • Publish approved models, MCP servers, and agents in one place people and agents can browse.
  • Set who can read each registry. Sales agents, for example, probably shouldn't discover the servers your engineering team uses.
  • Put the registry behind your gateway and enforce authentication and authorization on every call.

Where a gateway fits: one control point for everything agents call

A way to picture the problem starts with what an agent has to reach to get a job done. Let’s split it into two estates:

  • The intelligence estate is the reasoning layer: models, plus other agents.
  • The context estate is the data and tools that feed that reasoning: MCP servers, the API estate behind most of them, and your events and data.

Put a gateway in the middle and every model call, tool call, and agent-to-agent call crosses a point where you can see it, control it, and measure it. [Kong AI Gateway](https://konghq.com/products/kong-ai-gateway)Kong AI Gateway governs LLM and MCP traffic in one place, and [Kong Agent Gateway](https://konghq.com/blog/product-releases/kong-agent-gateway)Kong Agent Gateway covers agent-to-agent communication. If the idea is new to you, start with [what an AI gateway is](https://konghq.com/blog/enterprise/what-is-an-ai-gateway)what an AI gateway is.

You probably don't need to start from zero. Most organizations already run an API layer, and the best way is to modernize it so it's agent ready, building toward a "native AI traffic platform for governance."

What the roadmap looks like in Kong Konnect, and what to tackle next

The registry in practice

In Kong Konnect, the four things that map straight onto the roadmap:

  • Managed servers. The demo environment lists MCP servers for a support desk, GitHub, and Slack, all under management and likely sitting behind a Kong AI Gateway or MCP gateway.
  • Generated, not hand-built. Kong's context mesh builds code mode MCP servers from existing sources such as a knowledge base API, an HR directory API, Notion, Stripe, and Linear. You can also compose one server from several MCP servers or several APIs. The payoff in Drag's words:
    "now I don't have to go build net new APIs for the agent or net new MCP servers for the agent. I just automatically generate based on what I have."
  • Separate registries per team. Engineering, HR, and go-to-market can each have their own.The reasoning is that you may not want sales or HR agents to discover and leverage the servers engineering uses, so you set who can read each registry, for users and for agents.
  • One record for everything. Models, MCP servers, and agents are registered side by side, and the registry becomes "a central source of truth, not just for your MCP servers, but also the sources that your MCP servers leverage."

Cost and identity: your next two moves

Cost and identity are your next two problems, and Drag recommends an order for each.

On cost, Drag's rule is to "think about having tracking in place, setting up attribution, defining budgets before you ever start optimizing." Tracking means converting tokens into a currency value you can report. On identity, the control point is the agent's identity: "you can restrict, or control which kinds of tools that any given agent would ever have access to." Kong's pages on [AI cost governance and FinOps](https://konghq.com/solutions/ai-cost-governance-finops)AI cost governance and FinOps and [identity and access](https://konghq.com/products/governance-and-identity)identity and access cover each in depth.

Your first-week checklist

  1. List every model, MCP server, and agent your teams use. Mark your stage on the maturity model.
  2. Route model and MCP traffic through a gateway so the list stays current without manual effort.
  3. Stand up one registry and record the approved MCP server for each function.
  4. Choose your next problem, cost or identity, and start at the first step in the table above.

Ready to see it on your own stack? [Book a Kong demo](https://konghq.com/contact-sales)Book a Kong demo or explore [Kong Konnect](https://konghq.com/products/kong-konnect)Kong Konnect, the platform the demo ran on.

Frequently Asked Questions (FAQ)

What is an AI governance roadmap?

An AI governance roadmap is a sequenced plan for controlling the models, MCP servers, agents, APIs, and data your AI systems use. It covers cost, security, visibility, and resilience, and it starts with the problem hurting your organization most.

What is the first step in AI governance?

Discovery. Find every model, MCP server, and agent in use, then make the list durable by routing traffic through a gateway so you can "see and watch the traffic, and then start to build an inventory." Shadow AI detection helps with the first sweep.

What is MCP sprawl?

MCP sprawl is the uncontrolled spread of MCP servers, often on local machines, that open access to your APIs and data. It creates security and compliance exposure, and it wastes tokens because "MCP on its own is not very token efficient."

Is using many AI models a governance problem?

No. Many models are fine. The problem is teams or agents calling models directly, with no governance, visibility, or access-control layer between them and the provider.

Can Kong govern the decisions an agent makes?

Partly. When a decision means calling a tool, "that is for sure something that Kong can govern," because you can restrict which tools an agent reaches based on its identity. A separate question is whether an institution has authorized the business commitment that results from a tool call.

- [AI Gateway](/blog/tag/ai-gateway)AI Gateway

## More on this topic

_Videos_

## AI Connectivity: Kong AI Gateway 2.0 Delivers the Infrastructure to Run and Govern Enterprise Agents

_Videos_

## How Kong’s AI Gateway Governs Autonomous Agents for EU Payment Compliance

## See Kong in action

Accelerate deployments, reduce vulnerabilities, and gain real-time visibility. 

[Get a Demo](/contact-sales)Get a Demo
**Topics**
- [AI Gateway](/blog/tag/ai-gateway)AI Gateway
Kong

Recommended posts

# AI Traffic Needs a Control Point

[Enterprise](/blog/tag)EnterpriseNovember 17, 2026

What Gartner & Forrester See: API Infrastructure is Becoming AI Infrastructure "Managing and governing APIs is now critical for every organization, as API infrastructure quickly becomes AI infrastructure ." That's from the 2026 Gartner® Magic Qu

Eric Pulsifer

# Agent, Identity, and MCP Governance in One Control Layer

[Enterprise](/blog/tag)EnterpriseNovember 17, 2026

What is unified AI governance? Unified AI governance is a single runtime control layer that enforces identity, access, policy, and audit across every AI call — LLM requests, MCP tool calls, agent-to-agent traffic, and traditional APIs — using the s

Kong

# How to Manage and Secure AI Coding Agents

[Enterprise](/blog/tag)EnterpriseOctober 8, 2026

An AI coding agent is software that writes, tests, and ships code independently. This level of autonomy earlier tools never had. It doesn't wait for you to accept a suggestion line by line. It takes a goal, breaks it into steps, and executes. To do

Kong

# AI Token Cost Management: Why AI Spend Gets Out of Control (and How To Fix It)

[Enterprise](/blog/tag)EnterpriseSeptember 24, 2026

This post is based on Kong's webinar on token cost management. Watch it below, or keep reading for the breakdown. Token cost management is how a business tracks, controls, and governs what it spends on AI model usage, the same way it already track

Kong

# AI Governance Tools and Platforms: An Enterprise Guide

[Enterprise](/blog/tag)EnterpriseSeptember 23, 2026

AI adoption is outpacing the speed at which many organizations can establish standardized oversight. In fact, Stanford HAI reported that 78% of surveyed organizations were using AI in 2024, a significant jump from 55% the previous year ( AI Index Re

Kong

# How AI Agents Communicate: Managing Context in Multi-Agent Workflows

[Enterprise](/blog/tag)EnterpriseAugust 6, 2026

An AI agent isn't magic. It's a reasoning engine that makes decisions based on what it knows at a given moment. That "what it knows" is its context — the information available to it right now. Context is everything. Give an agent the wrong context,

Hugo Guerrero

# A New Dawn: Enterprise AI's Shadow — Trillions of Tokens, Zero Governance

[Enterprise](/blog/tag)EnterpriseAugust 6, 2026

You Can't Govern What You Can't See AI spending will reach $2.59 trillion in 2026. I regularly like to share what we're seeing in production at Kong. Not projections or analyst forecasts, but actual traffic flowing through Kong AI Gateway from

Augusto Marietti

# AI Traffic Needs a Control Point

[Enterprise](/blog/tag)EnterpriseNovember 17, 2026

What Gartner & Forrester See: API Infrastructure is Becoming AI Infrastructure "Managing and governing APIs is now critical for every organization, as API infrastructure quickly becomes AI infrastructure ." That's from the 2026 Gartner® Magic Qu

Eric Pulsifer

# Agent, Identity, and MCP Governance in One Control Layer

[Enterprise](/blog/tag)EnterpriseNovember 17, 2026

What is unified AI governance? Unified AI governance is a single runtime control layer that enforces identity, access, policy, and audit across every AI call — LLM requests, MCP tool calls, agent-to-agent traffic, and traditional APIs — using the s

Kong

# How to Manage and Secure AI Coding Agents

[Enterprise](/blog/tag)EnterpriseOctober 8, 2026

An AI coding agent is software that writes, tests, and ships code independently. This level of autonomy earlier tools never had. It doesn't wait for you to accept a suggestion line by line. It takes a goal, breaks it into steps, and executes. To do

Kong

# AI Token Cost Management: Why AI Spend Gets Out of Control (and How To Fix It)

[Enterprise](/blog/tag)EnterpriseSeptember 24, 2026

This post is based on Kong's webinar on token cost management. Watch it below, or keep reading for the breakdown. Token cost management is how a business tracks, controls, and governs what it spends on AI model usage, the same way it already track

Kong

# AI Governance Tools and Platforms: An Enterprise Guide

[Enterprise](/blog/tag)EnterpriseSeptember 23, 2026

AI adoption is outpacing the speed at which many organizations can establish standardized oversight. In fact, Stanford HAI reported that 78% of surveyed organizations were using AI in 2024, a significant jump from 55% the previous year ( AI Index Re

Kong

# How AI Agents Communicate: Managing Context in Multi-Agent Workflows

[Enterprise](/blog/tag)EnterpriseAugust 6, 2026

An AI agent isn't magic. It's a reasoning engine that makes decisions based on what it knows at a given moment. That "what it knows" is its context — the information available to it right now. Context is everything. Give an agent the wrong context,

Hugo Guerrero

# A New Dawn: Enterprise AI's Shadow — Trillions of Tokens, Zero Governance

[Enterprise](/blog/tag)EnterpriseAugust 6, 2026

You Can't Govern What You Can't See AI spending will reach $2.59 trillion in 2026. I regularly like to share what we're seeing in production at Kong. Not projections or analyst forecasts, but actual traffic flowing through Kong AI Gateway from

Augusto Marietti

# AI Traffic Needs a Control Point

[Enterprise](/blog/tag)EnterpriseNovember 17, 2026

What Gartner & Forrester See: API Infrastructure is Becoming AI Infrastructure "Managing and governing APIs is now critical for every organization, as API infrastructure quickly becomes AI infrastructure ." That's from the 2026 Gartner® Magic Qu

Eric Pulsifer

# Agent, Identity, and MCP Governance in One Control Layer

[Enterprise](/blog/tag)EnterpriseNovember 17, 2026

What is unified AI governance? Unified AI governance is a single runtime control layer that enforces identity, access, policy, and audit across every AI call — LLM requests, MCP tool calls, agent-to-agent traffic, and traditional APIs — using the s

Kong

# How to Manage and Secure AI Coding Agents

[Enterprise](/blog/tag)EnterpriseOctober 8, 2026

An AI coding agent is software that writes, tests, and ships code independently. This level of autonomy earlier tools never had. It doesn't wait for you to accept a suggestion line by line. It takes a goal, breaks it into steps, and executes. To do

Kong

# AI Token Cost Management: Why AI Spend Gets Out of Control (and How To Fix It)

[Enterprise](/blog/tag)EnterpriseSeptember 24, 2026

This post is based on Kong's webinar on token cost management. Watch it below, or keep reading for the breakdown. Token cost management is how a business tracks, controls, and governs what it spends on AI model usage, the same way it already track

Kong

# AI Governance Tools and Platforms: An Enterprise Guide

[Enterprise](/blog/tag)EnterpriseSeptember 23, 2026

AI adoption is outpacing the speed at which many organizations can establish standardized oversight. In fact, Stanford HAI reported that 78% of surveyed organizations were using AI in 2024, a significant jump from 55% the previous year ( AI Index Re

Kong

# How AI Agents Communicate: Managing Context in Multi-Agent Workflows

[Enterprise](/blog/tag)EnterpriseAugust 6, 2026

An AI agent isn't magic. It's a reasoning engine that makes decisions based on what it knows at a given moment. That "what it knows" is its context — the information available to it right now. Context is everything. Give an agent the wrong context,

Hugo Guerrero

# A New Dawn: Enterprise AI's Shadow — Trillions of Tokens, Zero Governance

[Enterprise](/blog/tag)EnterpriseAugust 6, 2026

You Can't Govern What You Can't See AI spending will reach $2.59 trillion in 2026. I regularly like to share what we're seeing in production at Kong. Not projections or analyst forecasts, but actual traffic flowing through Kong AI Gateway from

Augusto Marietti

## Ready to see Kong in action?

Get a personalized walkthrough of Kong's platform tailored to your architecture, use cases, and scale requirements.

[Get a Demo](/contact-sales)Get a Demo
## step-0
    • Company
    • [About Kong ](/company)About Kong
    • [Customers ](/customer-stories)Customers
    • [Careers ](/company/careers)Careers
    • [Press ](/company/press-room)Press
    • [Events ](/events)Events
    • [Contact ](/company/contact-us)Contact
    • [Pricing ](/pricing)Pricing
      •    * [Terms](/legal/terms-of-use)
      •    * [Privacy](/legal/privacy-policy)
      •    * [Trust and Compliance](https://trust.konghq.com/)
    • Platform
    • [Kong AI Gateway ](/products/kong-ai-gateway)Kong AI Gateway
    • [Kong Konnect ](/products/kong-konnect)Kong Konnect
    • [Kong Gateway ](/products/kong-gateway)Kong Gateway
    • [Kong Event Gateway ](/products/event-gateway)Kong Event Gateway
    • [Kong Insomnia ](/products/kong-insomnia)Kong Insomnia
    • [Documentation ](https://developer.konghq.com)Documentation
    • [Book Demo ](/contact-sales)Book Demo
    • Compare
    • [AI Gateway Alternatives ](/performance-comparison/ai-gateway-alternatives)AI Gateway Alternatives
    • [Kong vs Apigee ](/performance-comparison/kong-vs-apigee)Kong vs Apigee
    • [Kong vs AWS ](/performance-comparison/kong-vsaws)Kong vs AWS
    • [Kong vs IBM ](/performance-comparison/ibm-api-connect-vs-kong)Kong vs IBM
    • [Kong vs Mulesoft ](/performance-comparison/kong-vs-mulesoft)Kong vs Mulesoft
    • [Kong vs Postman ](/performance-comparison/kong-vs-postman)Kong vs Postman
    • [Kong vs LiteLLM ](/performance-comparison/kong-vs-litellm)Kong vs LiteLLM
    • Explore More
    • [Kong for Startups ](/solutions/startup-program)Kong for Startups
    • [Open Banking API Solutions ](/solutions/open-banking)Open Banking API Solutions
    • [API Governance Solutions ](/solutions/api-governance)API Governance Solutions
    • [Istio API Gateway Integration ](/solutions/istio-gateway)Istio API Gateway Integration
    • [Kubernetes API Management ](/solutions/build-on-kubernetes)Kubernetes API Management
    • [API Gateway: Build vs Buy ](/campaign/secure-api-scalability)API Gateway: Build vs Buy
    • Open Source
    • [Kong Gateway ](https://developer.konghq.com/gateway/install/)Kong Gateway
    • [Kuma ](https://kuma.io/)Kuma
    • [Insomnia ](https://insomnia.rest/)Insomnia
    • [Kong Community ](/community)Kong Community

Kong enables the connectivity layer for the agentic era – securely connecting, governing, and monetizing APIs and AI tokens across any model or cloud.

  • English
  • Japanese
  • Frenchcoming soon
  • Spanishcoming soon
  • Germancoming soon
[Everything is 200 OK](https://status.konghq.com/)
© Kong Inc. 2026
Interaction mode