What is the AgentAnywhere Universal Gateway?

The AgentAnywhere Universal Gateway is a multi-protocol API gateway for AI agents. It routes, secures, observes, and governs traffic across nine protocols (MCP, A2A, HTTP/REST, AG-UI, ACP, GraphQL, WebSocket, MQTT and gRPC) from a single control plane, so every agent, model, and tool interoperates under one policy layer.

Which protocols does the Universal Gateway support?

It supports nine: MCP (Model Context Protocol), A2A (Agent-to-Agent), HTTP/REST, AG-UI, ACP, GraphQL, WebSocket, MQTT and gRPC. All nine are terminated at one edge, with the same policy, key check and audit record on every one of the nine.

How do I install and run the Universal Gateway?

Install from PyPI with 'pip install agentanywhere-gateway', or run the full stack — gateway, admin console, and health checks — with Docker Compose. The CLI command is 'agentanywhere-gateway'. The gateway exposes a health endpoint on port 8000 and the admin console on port 3001.

How is a gateway different from a routing library?

A gateway centralizes routing, authentication, policy enforcement, and logging at one inspectable layer instead of scattering them across application code. That single chokepoint is what a regulator or CISO can audit to know exactly what every agent is allowed to do.

Is the Universal Gateway secure and compliant?

Yes. API keys, OAuth2, declarative policies and IP allow/deny rules are enforced at the edge, and administrative changes are kept in a hash-chained log. It is mapped to RBI FREE-AI and to SOC 2, ISO 27001, HIPAA, and GDPR.

Can I deploy the Universal Gateway on my own infrastructure?

Yes. It runs as a container inside your environment, so request traffic and the gateway's logs stay inside your perimeter. Configuration is set through environment variables.

PLATFORM · UNIVERSAL GATEWAY

AgentAnywhere Universal Gateway.

One gateway for agent protocols — route, secure, observe, and govern multi-protocol traffic from a single control plane. MCP, A2A, HTTP/REST, AG-UI, ACP, GraphQL, WebSocket, MQTT and gRPC, on your infrastructure.

Three jobs, one chokepoint.

Universal routing

One gateway across protocols. Connect any agent, model, or tool — MCP, A2A, and more — without bespoke integrations, and swap any of them without rewiring the others. Circuit breakers keep a failing upstream from cascading.

Policy enforcement

Guardrails applied at the point of call, not bolted on after. Every request is authenticated, scoped, and checked against your policies before it reaches a model or tool.

Full observability

Every call is logged, attributable to a human accountability chain, and audit-ready — with RED metrics, SLOs, and OTLP tracing out of the box. Nothing the agents do is invisible.

Speaks nine protocols.

Agent ecosystems are fragmenting across protocols. The Universal Gateway terminates nine of them at one edge, so a policy you write once applies to every one of the nine.

MCP

Model Context Protocol — tool and context calls from AI assistants and agent frameworks.

A2A

Agent-to-Agent — coordination and delegation between autonomous agents.

HTTP / REST

The universal default — any service, SDK, or webhook that speaks HTTP.

GraphQL

Typed, client-shaped queries for data-rich agent front-ends.

AG-UI

Agent-UI protocol for rendering interactive agent surfaces.

ACP

Agent Communication Protocol for interoperable agent messaging.

WebSocket

A proxy that applies policy to long-lived connections; one opened without a key is closed.

MQTT

A stream endpoint over server-sent events, behind the same key check.

gRPC

Served with reflection, behind the same key check.

Why a gateway, not a library.

Most agent stacks scatter routing, policy, and logging across application code. That works in a demo and fails an audit — there is no single place a regulator or CISO can inspect to know what every agent is allowed to do.

The Universal Gateway is that single place. It sits between your agents and everything they touch, so control and evidence live at one layer instead of a hundred.

Get started in minutes.

Install from PyPI or run the full stack — gateway, admin console, and health checks — with Docker Compose.

bash

pip install agentanywhere-gateway
cp env.example .env
docker compose up -d
# Health:   http://localhost:8000/health
# Admin UI: http://localhost:3001

CLI: agentanywhere-gateway · see the docs for env vars and deployment.

Part of one platform.

The Universal Gateway is how AgentAnywhere stays one system. Teams build agents in Flow Studio and Agent Lab; internally, the Orchestrator runs them and the agent Registry governs their lifecycle; and the Universal Gateway controls every call they make. The Orchestrator and the agent Registry are integral platform services — not separately sold — that hold this together as one governed system. They are distinct from Model Hub, the model registry, which is part of our open-source programme.

Compliance from the control plane.

Aligned with all twenty-six recommendations of RBI FREE-AI. SOC 2 and ISO 27001 certified; independently assessed for HIPAA and GDPR.

FAQ

Frequently asked questions.

What is the AgentAnywhere Universal Gateway?: The AgentAnywhere Universal Gateway is a multi-protocol API gateway for AI agents. It routes, secures, observes, and governs traffic across nine protocols (MCP, A2A, HTTP/REST, AG-UI, ACP, GraphQL, WebSocket, MQTT and gRPC) from a single control plane, so every agent, model, and tool interoperates under one policy layer.
Which protocols does the Universal Gateway support?: It supports nine: MCP (Model Context Protocol), A2A (Agent-to-Agent), HTTP/REST, AG-UI, ACP, GraphQL, WebSocket, MQTT and gRPC. All nine are terminated at one edge, with the same policy, key check and audit record on every one of the nine.
How do I install and run the Universal Gateway?: Install from PyPI with 'pip install agentanywhere-gateway', or run the full stack — gateway, admin console, and health checks — with Docker Compose. The CLI command is 'agentanywhere-gateway'. The gateway exposes a health endpoint on port 8000 and the admin console on port 3001.
How is a gateway different from a routing library?: A gateway centralizes routing, authentication, policy enforcement, and logging at one inspectable layer instead of scattering them across application code. That single chokepoint is what a regulator or CISO can audit to know exactly what every agent is allowed to do.
Is the Universal Gateway secure and compliant?: Yes. API keys, OAuth2, declarative policies and IP allow/deny rules are enforced at the edge, and administrative changes are kept in a hash-chained log. It is mapped to RBI FREE-AI and to SOC 2, ISO 27001, HIPAA, and GDPR.
Can I deploy the Universal Gateway on my own infrastructure?: Yes. It runs as a container inside your environment, so request traffic and the gateway's logs stay inside your perimeter. Configuration is set through environment variables.

Put every agent call under one control point.

Pilots start with an audit of your current agent communication surface — who calls what, with what policy, and where the evidence lives today. We replace scattered ad-hoc wiring with a single governed Universal Gateway. Six to ten weeks, sovereign environment.

Request a pilot Read the docs