Supported providers and gateways
OpenAI, Anthropic, Mistral
Create an API key in the provider’s console and send it to us. You do not need to send an endpoint: Clarifeye uses the provider’s public API.Google Gemini Enterprise Agent Platform (formerly Vertex AI)
Use this option to keep every call in your own GCP project. We need:- A service-account key in JSON format. The service account must have the
roles/aiplatform.userrole, and theaiplatform.googleapis.comAPI must be enabled in the project. - The GCP project ID.
- The region, for example
euto keep processing in the EU.
Azure OpenAI
We need:- The endpoint of your Azure resource, for example
https://<resource>.openai.azure.com. Send the base endpoint, not the full Target URI of a deployment. - An API key for that resource.
- The deployment names of the models you want us to use.
OpenRouter
Create an API key in your OpenRouter account. You do not need to send an endpoint.LiteLLM gateway
Use this option if you run your own LiteLLM proxy in front of your providers. We need:- The base URL of the gateway, for example
https://llm-gateway.example.com/v1. It must be reachable from the Clarifeye instance. - One way to authenticate:
- a static API key (a LiteLLM virtual key), or
- OAuth client credentials, if your gateway sits behind Microsoft Entra ID or another identity provider: token URL, client ID, client secret and scope. Clarifeye requests and renews the token itself.
- The model names exposed by your gateway (as listed by
GET <base URL>/models).
Route calls through your LLM gateway
Gateway routing is not available on all plans. Contact us to activate it for your organization.
- Every model: Clarifeye routes all LLM calls through the gateway, and infers the provider from the model name. Ask us 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 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 withlite-llm-gateway/ in the model field:
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:
Examples
With a reasoning-effort suffix:
Model overrides
Only organization admins can set model overrides.
- Open your organization and click Settings in the sidebar.
- Under Model overrides, enter a model name next to each tier you want to change. The placeholder shows the platform default for that tier.
- Click Save.
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 in Set the model name.
Good to know
- Choosing models. Clarifeye uses models at several levels (strong, medium, light, embedding). We map each level to a model from your provider. Organization admins can then change the model for each level with model overrides.
- Embeddings. The embedding model must be chosen before the first document is added. Changing it afterwards means processing every document again.