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

# LLM gateway and model overrides

> Choose which models your organization uses, and route Clarifeye's LLM calls through your own LiteLLM gateway.

You control which models Clarifeye uses for your organization, and how its LLM calls reach them:

* **Model overrides** replace the platform's default model for a tier with a model of your choice, for every store in the organization.
* **Gateway routing** sends LLM and agentic calls through an OpenAI-compatible **LiteLLM gateway** that you or your operator control, instead of calling providers (OpenAI, Anthropic, Gemini, Mistral) directly. This lets you centralize provider keys, spend, logging and access policy in one place, while Clarifeye keeps working exactly as before.

## Model overrides

<Note>
  Only organization admins can set model overrides.
</Note>

Clarifeye groups the models it uses into tiers, and you can point any tier at a different model:

1. Open your organization and click **Settings** in the sidebar.
2. Under **Model overrides**, enter a model name next to each tier you want to change. The placeholder shows the platform default for that tier.
3. Click **Save**.

The tiers are `STRONG_MODEL`, `STRONG_HIGH_REASONING`, `STRONG_LOW_REASONING`, `MEDIUM_MODEL`, `LIGHT_MODEL`, and `EMBEDDING_MODEL`. Leave a tier blank to keep the platform default.

To send a tier through your gateway, enter its gateway model name, as described below.

## Route calls through your LLM gateway

<Note>
  Gateway routing is not available on all plans. Contact us at `support@clarifeye.ai` to activate the feature and plug in your LiteLLM gateway endpoint for your organization.
</Note>

When the gateway is set up, Clarifeye authenticates to it with a static token or with an OAuth 2.0 client-credentials flow, for example against Microsoft Entra ID.

There are two ways to use it:

* **Every model**: Clarifeye routes all LLM calls through the gateway, and infers the provider from the model name. Ask Clarifeye support to enable this.
* **Per model**: you opt in one model at a time with the `lite-llm-gateway/` prefix. Models you leave unprefixed keep their default route, so you can move one tier, one extractor or one Playground agent onto the gateway without touching the rest.

### What can be routed

Any model that Clarifeye lets you name can go through the gateway, including:

* The [model overrides](#model-overrides) of your organization.
* The **Playground** assistant (chat, agentic tool use, and playbook execution).
* **Extractors**: object extraction, tag extraction, and document-tag extraction.

### Set the model name

To route a model through the gateway, prefix its name with `lite-llm-gateway/` in the model field:

```text theme={null}
lite-llm-gateway/<provider>/<model>
```

Clarifeye strips the `lite-llm-gateway/` prefix and passes the remainder (`<provider>/<model>`) to the gateway verbatim, so it must match a model your gateway is configured to serve. A prefixed model always goes through the gateway, whatever the default route.

For reasoning models, add a reasoning-effort suffix after a colon (`:low`, `:medium`, `:high`), exactly as you would without the gateway:

```text theme={null}
lite-llm-gateway/<provider>/<model>:<effort>
```

### Examples

| Provider | Direct model name | Through the gateway |
| - | - | - |
| OpenAI | `gpt-5.4` | `lite-llm-gateway/openai/gpt-5.4` |
| Anthropic | `anthropic/claude-opus-4-8` | `lite-llm-gateway/anthropic/claude-opus-4-8` |
| Gemini | `gemini/gemini-2.5-pro` | `lite-llm-gateway/gemini/gemini-2.5-pro` |
| Mistral | `mistral/mistral-large-latest` | `lite-llm-gateway/mistral/mistral-large-latest` |

With a reasoning-effort suffix:

```text theme={null}
lite-llm-gateway/openai/gpt-5:medium
lite-llm-gateway/openai/gpt-5:high
```

<Tip>
  Whitespace around the value is ignored, so a stray leading or trailing space won't accidentally bypass gateway routing.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.