For the complete documentation index, see llms.txt. This page is also available as Markdown.

LangGraph

Connect Akto with LangGraph

Overview

LangGraph is a framework for building stateful, multi-actor AI agent applications using graph-based workflows. This integration lets you capture tool calls, agent interactions, and execution traces from your LangGraph applications and send them into Akto for security monitoring and policy enforcement.

Akto supports three integration methods for LangGraph depending on your deployment requirements.

Integration Methods

1. Via LangSmith (Telemetry)

LangGraph natively integrates with LangSmith for observability and tracing. If your LangGraph application already reports traces to LangSmith, you can use Akto's existing LangChain connector to pull that data into Akto — no additional instrumentation required.

Follow the steps in the LangChain connector guide to configure the integration. The same connector works for LangGraph applications traced through LangSmith.

When to use this

Use this method if you want passive observability; collecting execution traces and API traffic after the fact without intercepting live requests.

2. Via Gateway

Route your LangGraph agent's outbound LLM and tool calls through Akto's AI Agent Gateway. This gives you real-time inspection, guardrails enforcement, and response filtering on every request your agent makes, without modifying your application logic.

1. Set Up the AI Agent Gateway

Configure an AI Agent Gateway in your environment so LangGraph agent requests can pass through the gateway before reaching the upstream LLM or tool APIs.

Akto Argus inspects prompts, evaluates guardrail policies, and filters responses before forwarding traffic to the upstream services.

Refer to the AI Agent Gateway guide for setup instructions.

An enterprise platform team can deploy and manage the gateway within internal infrastructure. The deployed gateway endpoint becomes the {PROXY_URL} used in model routing configuration.

2. Route Model Requests Through the Gateway

Update the model endpoint used by the LangGraph agent so requests pass through the gateway before reaching the model provider.

General model endpoint format:

Gateway endpoint format:

Configuration Element
Value

Model URL

https://{MODEL_HOST}/{MODEL_PATH}

Gateway URL Format

https://{PROXY_URL}/{MODEL_PATH}?openai_url=https://{MODEL_HOST}

Akto Argus evaluates prompts, applies guardrail policies, and forwards the request to the upstream model provider.

Example: Azure AI Foundry endpoint

Azure AI Foundry model endpoint:

Gateway endpoint format:

When to use this

Use this method if you want active enforcement — intercepting and inspecting requests in real time before they reach the LLM or tool.

Akto provides AktoGuardrailsMiddleware — a class-based AgentMiddleware that hooks directly into the LangGraph agent lifecycle to enforce Akto guardrails on every model call. This requires no gateway and no external telemetry pipeline.

The middleware intercepts two points in the agent lifecycle:

  • before_model — Validates the prompt against Akto guardrails before the LLM is called. In sync mode, a policy violation blocks the request immediately.

  • after_model — Ingests the completed interaction (prompt + response) into Akto for audit and dashboard visibility.

Both synchronous and asynchronous agent execution modes are supported.

Request Flow (AKTO_SYNC_MODE=true)

Request Flow (AKTO_SYNC_MODE=false)

Steps to Connect

1

Install Dependencies

Ensure the required packages are installed:

2

Download the Middleware

Download the akto_middleware.py file into your project:

3

Configure Environment Variables

Set the following environment variables in your shell or .env file:

4

Integrate the Middleware into Your LangGraph Agent

Import AktoGuardrailsMiddleware and pass it to your LangGraph agent's middleware list:

The middleware automatically handles both sync and async execution paths — no additional configuration is needed.

5

Verify Integration

Run your agent and check the logs for middleware initialization:

Then verify in the Akto dashboard:

  • Log into your Akto dashboard

  • Navigate to the Collections section

  • Verify you see requests from your LangGraph application appearing

Configuration Reference

Variable
Required
Default
Description

AKTO_DATA_INGESTION_URL

Yes

Akto service base URL

PROJECT_NAME

Yes

Unique identifier for this LangGraph application in Akto

AKTO_SYNC_MODE

No

true

true to block on violation, false for log-only

AKTO_TIMEOUT

No

5

HTTP timeout in seconds

LOG_LEVEL

No

INFO

Logging level

LOG_PAYLOADS

No

false

Log full request/response payloads (privacy-sensitive)

LANGCHAIN_API_HOST

No

api.langchain.com

Host header used in the proxy payload

LANGCHAIN_API_PATH

No

/langchain/chat

Path used in the proxy payload

Handling Blocked Requests

When AKTO_SYNC_MODE=true and a request is blocked by guardrails, the middleware raises a ValueError:

You can catch this in your application to handle blocked requests gracefully:

When to use this

Use this method if you want guardrails enforcement directly inside your LangGraph agent without deploying a separate gateway. It provides the same validation and blocking capabilities as the gateway approach, with a simpler setup.

Get Support

Last updated