agentgateway

Why we included this project

When your agents move past demos and start handling real traffic, the gaps in a naive setup become obvious: API keys scattered across scripts, runaway spend, no idea which tool call caused a spike. Agentgateway solves that by putting a single proxy between your agents and everything they talk to, whether that is an LLM provider, an MCP tool server, or another agent. It handles the unglamorous plumbing, like auth, rate limiting, budget controls, content filtering, and OpenTelemetry-based logging and tracing, and it speaks both MCP and A2A so it fits current agent tooling. You can run it as a plain process or as a Kubernetes controller that plugs into the Gateway API, which makes it a natural fit for teams that already live in a service mesh and want one consistent place for governance.