> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fiddler.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Gateway Integrations

> How Fiddler plugs into a third-party AI gateway (Kong, AgentGateway, LiteLLM) for observability and guardrail enforcement — and how that differs from the Fiddler LLM Gateway.

## What This Is

A **third-party AI gateway** is an inline proxy your application already routes LLM traffic
through. Fiddler plugs in at that layer, so you get observability, guardrail enforcement, or both —
with **no application code changes**. Fiddler documents three: [Kong AI Gateway](/integrations/agentic-ai/kong-integration),
[AgentGateway](/integrations/agentic-ai/agentgateway-integration), and [LiteLLM](/integrations/agentic-ai/litellm-integration).

<Note>
  **Not to be confused with the Fiddler LLM Gateway.** The [Fiddler LLM Gateway](/reference/administration/llm-gateway)
  manages *Fiddler's own* provider credentials for evaluators and enrichments — Fiddler calling out to
  model providers. A third-party AI gateway proxies *your* traffic to *your* models. This page is about
  the latter.
</Note>

## Two Capabilities, Independent

Each integration offers up to two capabilities, and either can be deployed without the other:

| Capability                  | What it does                                              | How it runs                                                                     |
| --------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------- |
| **Observability (tracing)** | Captures prompts, responses, tokens, and latency as spans | Out-of-band — the gateway exports OTel spans to Fiddler                         |
| **Guardrail enforcement**   | Blocks or redacts PII and secrets                         | Inline — the gateway calls Fiddler's guardrail adapter on each request/response |

```mermaid theme={null}
flowchart LR
    App["Your app"] --> GW["AI gateway"]
    GW -->|inline guardrail check| FA["Fiddler guardrail adapter"]
    GW --> LLM["LLM provider"]
    GW -.->|out-of-band OTel spans| FO["Fiddler observability"]
```

## Which Gateways

<Columns cols={3}>
  <Card title="Kong AI Gateway" href="/integrations/agentic-ai/kong-integration">
    Tracing on Kong 3.13+. Guardrails need Kong 3.14+ with an **AI Gateway Enterprise** license. Live today. · [Guardrails](/protection/kong-guardrails)
  </Card>

  <Card title="AgentGateway" href="/integrations/agentic-ai/agentgateway-integration">
    Apache 2.0. Tracing on v1.1.0+. Guardrails need v1.4.0+ and **Fiddler 26.17+**. · [Guardrails](/protection/agentgateway-guardrails)
  </Card>

  <Card title="LiteLLM" href="/integrations/agentic-ai/litellm-integration">
    Open source. SDK or proxy. Live today. · [Guardrails](/protection/litellm-guardrails)
  </Card>
</Columns>

## Capability Comparison

Each page is authoritative for its own exact behavior and version floors; this table is a starting
point, not a substitute.

|                                    | Kong                               | AgentGateway                             | LiteLLM                |
| ---------------------------------- | ---------------------------------- | ---------------------------------------- | ---------------------- |
| Enforcement outcome                | Blocked                            | Redacted or blocked                      | Redacted or blocked    |
| Failure control                    | None (fail-open)                   | Per-route header + gateway `failureMode` | Per-request            |
| Streaming redaction                | N/A (blocks only)                  | No-op on streamed responses              | Not on streamed output |
| Session grouping                   | `pre-function` plugin              | CEL from a header                        | Not supported          |
| MCP tool tracing                   | —                                  | Yes (via downstream classification)      | Yes                    |
| Configurability                    | None (2 wire fields)               | Per-route static headers                 | Per-request body       |
| Edition / license                  | AI Gateway Enterprise (guardrails) | Apache 2.0                               | MIT (open source)      |
| Product-visible guardrail decision | Customer-emitted span              | None                                     | Mapper-emitted         |
| Guardrails availability            | Live                               | Fiddler 26.17+                           | Live                   |

## Which Checks Run

Across all three gateways, Fiddler's guardrail adapters run two checks: **PII** and **secrets**.
Faithfulness — offered elsewhere in [Fiddler Protect](/protection/index) — is **not** available on
the gateway path. See each guardrails page for per-check thresholds, actions, and what can be tuned.

## Choosing a Path

Use the gateway you already run. If you only need visibility, start with tracing; add guardrails when
you need enforcement. Kong blocks on a detection; AgentGateway and LiteLLM can redact in place. If
you need to redact streamed responses, review the streaming limits on the owning guardrails page
first.

## What Every Integration Guarantees

* **No application code changes** — you point at the gateway you already run.
* **The guardrail adapter is stateless** — Fiddler evaluates text in-request and returns a decision; no prompt, response, or detection result is retained (the only durable artifact is content-free operational counters).
* **Each page is the source of truth** for its gateway's exact version floors, wire contract, and configuration surface.

## Next Steps

* [Kong AI Gateway Integration](/integrations/agentic-ai/kong-integration) — tracing setup for Kong.
* [Kong AI Gateway Guardrails](/protection/kong-guardrails) — enforcement on Kong.
* [AgentGateway Integration](/integrations/agentic-ai/agentgateway-integration) — tracing setup for AgentGateway.
* [AgentGateway Guardrails](/protection/agentgateway-guardrails) — enforcement on AgentGateway.
* [LiteLLM Integration](/integrations/agentic-ai/litellm-integration) — tracing setup for LiteLLM.
* [LiteLLM Guardrails](/protection/litellm-guardrails) — enforcement on LiteLLM.