You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ai-agents/pages/ai-gateway.adoc
+197-7Lines changed: 197 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,13 @@ NOTE: AI Gateway is supported on BYOC clusters running Redpanda version 25.3 and
6
6
7
7
The Redpanda AI Gateway is a production-grade proxy that provides unified access to multiple Large Language Model (LLM) providers and Model Context Protocol (MCP) servers through a single endpoint. It maintains centralized control over routing, rate limiting, cost optimization, security, and observability.
8
8
9
+
Common gateway patterns:
10
+
11
+
* *Team isolation*: Create separate gateways for each team to track usage and enforce budgets independently.
12
+
* *Environment separation*: Use different gateways for staging and production with appropriate rate limits.
13
+
* *Failover*: Configure a primary provider pool with a fallback pool for high availability.
14
+
* *A/B testing*: Distribute traffic across providers to compare performance and cost.
15
+
9
16
== Prerequisites
10
17
11
18
* Access to the AI Gateway UI (provided by your administrator)
@@ -20,7 +27,7 @@ Before a gateway owner can create a gateway, an administrator must enable LLM pr
20
27
21
28
Providers represent upstream services (Anthropic, OpenAI) and associated credentials. Providers are disabled by default. An administrator must enable them explicitly by adding credentials.
22
29
23
-
. Navigate to *Providers*.
30
+
. In AI Gateways, navigate to *Providers*.
24
31
. Select a provider (for example, Anthropic).
25
32
. On the *Configuration* tab, enter your API Key.
26
33
@@ -106,7 +113,7 @@ You can aggregate multiple MCP servers behind a single endpoint. For example:
106
113
* The gateway presents a single aggregated MCP surface to the agent.
107
114
* Agents can list/search tools and call them through the gateway.
108
115
109
-
*MCP orchestrator*
116
+
*MCP orchestrator:*
110
117
111
118
The orchestrator is a built-in MCP server that enables programmatic tool calling. The agent can generate JavaScript to call multiple tools in a single orchestrated step, which reduces the number of round trips. For example, a workflow requiring 47 file reads can be reduced from 49 round trips to just 1.
* *Team isolation*: Create separate gateways for each team to track usage and enforce budgets independently.
183
-
* *Environment separation*: Use different gateways for staging and production with appropriate rate limits.
184
-
* *Failover*: Configure a primary provider pool with a fallback pool for high availability.
185
-
* *A/B testing*: Distribute traffic across providers to compare performance and cost.
189
+
The AI Gateway provides standardized endpoints that work with various AI development tools and agents. This section shows how to configure popular tools to use your AI Gateway endpoints.
190
+
191
+
=== MCP server endpoint
192
+
193
+
If you've configured MCP tools in your gateway, AI agents can connect to the aggregated MCP endpoint:
194
+
195
+
* MCP endpoint URL: `https://gw.ai.panda.com/mcp`
196
+
197
+
* Headers required:
198
+
** `Authorization: Bearer your-api-key`
199
+
** `rp-aigw-id: your-gateway-id`
200
+
201
+
This endpoint aggregates all MCP servers configured in your gateway, providing a unified interface for tool discovery and execution.
202
+
203
+
=== Environment variables
204
+
205
+
For consistent configuration across tools, set these environment variables:
0 commit comments