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

# LLM Providers: Route Agents to Any Model

> Route AI agent traffic to Anthropic, OpenAI, Vertex AI, or any LLM provider. The gateway injects API keys so agents never see them.

## Overview

Store your LLM API keys in OneCLI and the gateway injects them into requests automatically. Agents call model APIs without ever seeing the raw key.

<Frame>
  <img src="https://mintcdn.com/chartdbinc/WHxYCiD2RgHrla4w/images/connections-llms.png?fit=max&auto=format&n=WHxYCiD2RgHrla4w&q=85&s=dda750e88731d17616635ad27d6d55ad" alt="LLMs tab in the OneCLI Connections dashboard" width="2000" height="1208" data-path="images/connections-llms.png" />
</Frame>

| Provider                             | Target host         | Auth method            |
| ------------------------------------ | ------------------- | ---------------------- |
| [Anthropic](/integrations/anthropic) | `api.anthropic.com` | API key or OAuth token |
| [OpenAI](/integrations/openai)       | `api.openai.com`    | API key                |

## How it works

1. You add an API key in the OneCLI dashboard under **Connections** > **LLMs**
2. OneCLI encrypts and stores the key (AES-256-GCM at rest)
3. When an agent sends a request to a matching host (e.g. `api.anthropic.com`), the gateway injects the key into the appropriate header
4. The request is forwarded to the provider

If you rotate a key, update it in the dashboard and all agents pick up the new key automatically.

## Controlling access with rules

Use OneCLI's [rules engine](/guides/rules) to control how agents use your LLM keys. For example, you can rate-limit requests, restrict agents to specific models by blocking certain paths, or flag high-cost operations for manual approval. Rules are evaluated before credential injection, so a blocked request never reaches the provider.