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

# Agent Integrations Overview

> Coding assistants and agent frameworks that connect to PipeLLM through protocol-compatible gateway routes

This section documents agent-facing tools that can run directly on PipeLLM by
pointing them at the correct protocol route.

## Recommended Routes

| Tool or framework   | Recommended route                                                                         | Why                                                                         |
| ------------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Claude Code         | `https://api.pipellm.ai` for Claude, `https://api.pipellm.ai/anthropic` for GPT or Gemini | Claude Code speaks the Anthropic Messages protocol                          |
| OpenCode            | `https://api.pipellm.ai/openai/v1`                                                        | OpenCode custom providers work well with OpenAI-compatible chat completions |
| OpenClaw            | `https://api.pipellm.ai/openai/v1`                                                        | OpenClaw custom providers support OpenAI-compatible endpoints cleanly       |
| LangChain OpenAI    | `https://api.pipellm.ai/v1`                                                               | `ChatOpenAI` maps directly to OpenAI-compatible native routes               |
| LangChain Anthropic | `https://api.pipellm.ai`                                                                  | `ChatAnthropic` maps directly to Anthropic Messages                         |
| LangChain Gemini    | `https://api.pipellm.ai`                                                                  | `ChatGoogleGenerativeAI` maps directly to Gemini native routes              |

## What a Tool Guide Covers

Each tool guide answers four questions:

* which base URL to use
* which environment variables or config keys to set
* which model families make sense as starting points
* which protocol limitations or workarounds developers should know

## Coding Agents and Assistants

<Columns cols={3}>
  <Card title="Claude Code" icon="terminal" href="/integrations/claude-code">
    Anthropic-native coding assistant
  </Card>

  <Card title="OpenCode" icon="code" href="/integrations/opencode">
    Open source coding agent with JSON config
  </Card>

  <Card title="OpenClaw" icon="terminal" href="/integrations/openclaw">
    Gateway-first assistant with custom provider onboarding
  </Card>
</Columns>

## Agent Framework Integrations

<Columns cols={3}>
  <Card title="LangChain (OpenAI)" icon="link" href="/integrations/langchain-openai">
    Use `ChatOpenAI` with PipeLLM's OpenAI-compatible routes
  </Card>

  <Card title="LangChain (Anthropic)" icon="link" href="/integrations/langchain-anthropic">
    Use `ChatAnthropic` with PipeLLM's Anthropic-compatible routes
  </Card>

  <Card title="LangChain (Gemini)" icon="link" href="/integrations/langchain-gemini">
    Use `ChatGoogleGenerativeAI` with PipeLLM's Gemini routes
  </Card>
</Columns>

## Shared References

<Columns cols={3}>
  <Card title="Routing & Protocols" icon="route" href="/guides/routing-protocols">
    Choose the right route before configuring a tool
  </Card>

  <Card title="Converters" icon="shuffle" href="/converter/overview">
    Keep the tool's native SDK format across providers
  </Card>

  <Card title="List Models" icon="list" href="/api-reference/list-models">
    Confirm the model IDs available to your account
  </Card>
</Columns>