Skip to main content
This guide covers Langchain JavaScript/TypeScript. For Python, see Langchain Python.
Langchain provides a unified interface for building LLM applications. Add the AI Gateway to get production-grade features: full observability, automatic fallbacks, semantic caching, and cost controls—all without changing your Langchain code.

Quick Start

Add the AI Gateway to any Langchain app with 3 parameters:
That’s it! You now get:
  • ✅ Full observability (costs, latency, logs)
  • ✅ Dynamic model selection per request
  • ✅ Automatic fallbacks and retries (via configs)
  • ✅ Budget controls per team/project

Why Add the AI Gateway to Langchain?

Langchain handles application orchestration. The AI Gateway adds production features:

Enterprise Observability

Every request logged with costs, latency, tokens. Team-level analytics and debugging.

Dynamic Model Selection

Switch models per request. Route simple queries to cheap models, complex to advanced—automatically tracked.

Production Reliability

Automatic fallbacks, smart retries, load balancing—configured once, works everywhere.

Cost & Access Control

Budget limits per team/project. Rate limiting. Centralized credential management.

Setup

1. Install Packages

2. Add Provider in Model Catalog

  1. Go to Model Catalog → Add Provider
  2. Select your provider (OpenAI, Anthropic, Google, etc.)
  3. Choose existing credentials or create new by entering your API keys
  4. Name your provider (e.g., openai-prod)
Your provider slug will be @openai-prod (or whatever you named it).

Complete Model Catalog Guide →

Set up budgets, rate limits, and manage credentials

3. Get AI Gateway API Key

Create your AI Gateway API key at stratacloudmanager.paloaltonetworks.com

4. Use in Your Code

Replace your existing ChatOpenAI initialization:
That’s the only change needed! All your existing Langchain code (agents, chains, LCEL, etc.) works exactly the same.

Switching Between Providers

Just change the model string—everything else stays the same:
The AI Gateway implements OpenAI-compatible APIs for all providers, so you always use ChatOpenAI regardless of which model you’re calling.

Using with Langchain Agents

Langchain agents are the primary use case. The AI Gateway works seamlessly with agent workflows:
Every agent step is logged in the AI Gateway:
  • Model calls with prompts and responses
  • Tool executions with inputs and outputs
  • Full trace of the agent’s reasoning
  • Costs and latency for each step

Works With All Langchain Features

Agents - Full compatibility with LangGraph agents ✅ LCEL - LangChain Expression Language ✅ Chains - All chain types supported ✅ Streaming - Token-by-token streaming ✅ Tool Calling - Function/tool calling ✅ LangGraph - Complex workflows

Streaming

Chains & Prompts

Tool Calling

Dynamic Model Selection

For dynamic model routing based on query complexity or task type, use AI Gateway Configs with conditional routing:
All routing decisions are tracked in the AI Gateway with full observability—see which models were used, costs per model, and performance comparisons.

Conditional Routing Guide →

Learn more about conditional routing and advanced patterns

Advanced Features via Configs

For production features like fallbacks, caching, and load balancing, use AI Gateway Configs:

Example: Load Balancing

Learn About Configs →

Set up fallbacks, retries, caching, load balancing, and more

Embeddings

Create embeddings via the AI Gateway:
The AI Gateway supports OpenAI embeddings via OpenAIEmbeddings. For other providers (Cohere, Voyage), call the embeddings endpoint directly.

Migration from Direct OpenAI

Already using Langchain with OpenAI? Just update 3 parameters:
Benefits:
  • Zero code changes to your existing Langchain logic
  • Instant observability for all requests
  • Production-grade reliability features
  • Cost controls and budgets

Next Steps

Model Catalog

Set up providers, budgets, and access control

Configs

Configure fallbacks, caching, and routing

Observability

Track costs, performance, and usage

Guardrails

Add PII detection and content filtering
Last modified on September 15, 2026