Vendors Extending API Gateways Into Agent Governance
The short answer
Five vendors now sell an existing API gateway as the control point for AI agents: Google Apigee, Microsoft Azure API Management, Kong, MuleSoft (Salesforce) and AWS with Bedrock AgentCore Gateway. Each turns your existing APIs into Model Context Protocol (MCP) tools and puts authentication, per-tool authorization, quotas and logging in front of agent traffic. The right pick is almost always the gateway that already fronts your APIs, because the policies you have written carry over. Facts below were checked against vendor documentation on October 19, 2026.
The comparison
| Google Apigee | Azure API Management | Kong AI Gateway | MuleSoft Agent Fabric | AWS AgentCore Gateway | |
|---|---|---|---|---|---|
| Turns APIs into MCP tools | Yes — MCP Discovery Proxy from an OpenAPI 3.0.x spec | Yes — expose REST APIs as MCP servers | Yes — map a REST API to MCP tools | Yes — MCP Bridge | Yes — targets from APIs, Lambda and existing MCP servers |
| Traffic it governs | APIs + MCP | LLM APIs, MCP servers, A2A agent APIs | LLM, MCP and A2A from one endpoint | Agents, MCP servers, APIs, LLM calls | Agent tool calls |
| Per-tool authorization | Tools listed in an API product, optional per-tool quota; tools/list filtered per client | Policies per MCP server/tool | ACLs and consumer groups | Open policies on Omni Gateway | Policy checks on each tool call (Cedar) |
| Runs on your infrastructure | Yes — Apigee hybrid 1.17.0 (Sep 14, 2026) | Self-hosted gateway for hybrid | Yes — data planes anywhere, Konnect control plane | Managed instances on Omni Gateway | No — AWS-managed |
| Catalogue | Apigee API hub (MCP as an API style) | Azure API Center | Konnect | Agent registry + scanners | AgentCore registry, semantic tool search |
| Pricing | Apigee plan | Classic tiers; AI Gateway tier pricing “announced later in the preview” | Konnect plan | Anypoint subscription | $5 per million tool calls, no minimum |
| Best for | Regulated, on-prem or multi-cloud API estates | Microsoft and Foundry shops | Vendor-neutral, multi-cloud | Salesforce and Agentforce estates | Agents already on AWS |
What each vendor actually ships
Google Apigee. You describe an API with an OpenAPI 3.0.x spec and create an MCP Discovery Proxy; every operation becomes an MCP tool and Apigee handles the JSON-RPC and transcoding, so you do not write or run MCP servers. Tool-level control comes from the API product: you list the operations a client may call, optionally with a per-tool quota, and when that client calls tools/list it sees only those tools — “an agent cannot call delete_account if it was never allowed to see it,” in Google’s words. Deployed MCP proxies appear in Apigee API hub, and API insights break one /mcp endpoint down by tool. On October 14, 2026 Google announced that Apigee hybrid 1.17.0 (released September 14, 2026) runs the MCP data plane inside your own Kubernetes cluster: MCP requests never leave the cluster, and configuration is pulled from the control plane rather than pushed in. Apigee also forwards W3C trace context from MCP’s _meta field into ordinary traceparent headers so backends join one trace.
Azure API Management. On the Developer, Basic, Standard and Premium tiers (classic and v2), API Management manages remote MCP servers and can expose existing REST APIs as MCP servers, with centralized authentication, authorization and monitoring, and registration in Azure API Center. Separately, the AI Gateway tier is a managed gateway for models and MCP tools in public preview in East US 2 and Sweden Central: one endpoint, provider credentials hidden from apps, token and request rate limits, content safety, IP filters and OpenTelemetry telemetry, with Microsoft Entra ID sign-in. Microsoft says preview pricing “will be announced later in the preview” — budget for change.
Kong AI Gateway. Kong governs three traffic types — LLM, MCP and A2A — from one Konnect control plane with data planes you deploy anywhere. Its AI MCP Server entity exposes existing APIs as discoverable tools and applies the same authentication, rate limiting and observability as your HTTP traffic. AI Gateway 2.1+ accepts the stateless MCP 2026-07-28 revision alongside 2025-03-26, 2025-06-18 and 2025-11-25, and can aggregate tools from several MCP servers. Kong documents that prompt-level AI policies (prompt guards, model routing) do not apply to MCP traffic, which is API-level.
MuleSoft Agent Fabric. Salesforce’s answer is broader than a gateway: an agent registry of agents, MCP servers and APIs from any platform (with scanners that discover them on connected clouds), MCP Bridge to turn existing APIs and SaaS systems into MCP servers, and Omni Gateway as the runtime enforcement point in front of agents, APIs, MCP servers and LLM traffic, plus token cost controls.
AWS Bedrock AgentCore Gateway. The serverless option: no gateway to run, pay per use. AWS lists $5 per million InvokeTool calls, $25 per million semantic search queries, $0.02 per 100 indexed tools a month, and Policy authorization checks at $0.000025 per request — AWS’s own example of 500,000 checks a month costs $12.50. It governs tool calls well; it does not front your non-AWS API estate.
Which one to pick
- You already run one of these for APIs: extend it. Rewriting auth, quotas and audit for a second gateway is the expensive part, not the licence.
- Data must stay in your data centre or a specific jurisdiction: Apigee hybrid or Kong with self-hosted data planes.
- Microsoft estate, agents in Foundry or Copilot Studio: Azure API Management now; evaluate the AI Gateway tier once it has a price.
- Many clouds, many teams, no dominant vendor: Kong.
- Salesforce and Agentforce are the centre of gravity: MuleSoft Agent Fabric.
- Agents built on AWS, few legacy APIs: AgentCore Gateway.
Whatever you choose, keep secrets out of the model — see short-lived credentials for AI agents — and compare with model-traffic gateways in best LLM gateways ranked. For the wider control-plane market see best AI agent control planes; for SaaS tool integrations rather than your own APIs, Composio vs Arcade vs Pipedream Connect.
Last verified: October 19, 2026.