Solo.io Blog

In previous posts, I’ve covered the reasons why an AI agent needs an identity. I recommend reading that first. In this post I want to nail down “what is agent identity” because I’ve seen a lot of different interpretations from smart people such as “use OAuth” to “it’s just workload identity”, and new protocols cropping up, etc. But what “is” an agent identity in concrete terms?

Learn how to configure and test agentgateway Code Mode to expose APIs as MCP tools, enabling secure agent access without an MCP server.

What’s the difference between agent-sandbox and agent-substrate? Learn how these complementary projects help teams build AI agent platforms that are both secure and scalable on Kubernetes.

Learn why James Quigley's team adopted Istio Ambient for mTLS, security, and operational simplicity, and how the journey unfolded.

Learn how to run AI agents on Kubernetes with Agent Substrate and kagent. This step-by-step guide covers architecture, installation, configuration, and deploying agent workloads using the Substrate runtime.

Kubernetes transformed how we run services. Agent Substrate and kagent are transforming how we run AI agents with fast startup, efficient resource utilization, and secure execution.

Discover how to build a dollar-denominated AI cost-governance layer on top of agentgateway's native External Processing support. The reference implementation adds hierarchical budgets, pre-request reservations, actual-cost settlement, forecasting, approvals, rate limits, and a management UI.

Learn about the infrastructure challenges emerging around AI systems, why existing gateway patterns are being stretched in new ways, and why agentgateway was built as a unified, high-performance operational layer for AI and API traffic.

The Agentic AI Foundation welcomes agentgateway - an open source gateway purpose-built for MCP, Agent-to-Agent, LLM, and API traffic - as its newest hosted project.

This release brings agentgateway into the ambient mesh as a waypoint, ingress, and egress proxy, adds egress controls directly in ztunnel, ships a revamped Solo UI with a new advanced Service Graph, and introduces workload identity that goes beyond the service account.