Skip to main content
OVHcloud AI Endpoints expose hosted open models (Qwen, Mistral, Llama, gpt-oss, and others) through an OpenAI-compatible endpoint, served from OVHcloud’s European infrastructure. Pair them with LightOn search to build RAG pipelines where the retrieval stays on LightOn’s infrastructure and the generation runs on OVHcloud. The flow is:
  1. Search LightOn for the passages most relevant to the user’s question.
  2. Pack those passages into the model’s context window.
  3. Call the OVHcloud model to generate an answer grounded in the retrieved content.

Prerequisites

  • A LIGHTON_API_KEY, available in the Console → API Keys section.
  • An OVHcloud AI Endpoints access token, available in the OVHcloud Control Panel under Public Cloud → AI Endpoints. Store it as OVH_AI_ENDPOINTS_ACCESS_TOKEN.
  • At least one workspace with indexed documents on LightOn.

Installation

The openai package is used here only for its client; OVHcloud’s /chat/completions endpoint is fully compatible with it.

Full example

LightOn search as a tool

Instead of always searching before calling the model, you can expose LightOn search as a tool and let the model decide when to call it. The model issues a lighton_search tool call when it needs context; your code executes the search and feeds the results back; the model then produces a final answer.
The loop handles the case where the model issues multiple search calls in sequence before producing a final answer.

Scoping retrieval to a workspace

Pass workspace_id to limit search to a specific workspace. This is useful in multi-tenant products where each customer’s data lives in a dedicated workspace.

Choosing a model

OVHcloud’s catalog includes several hosted models. Pass the model name to the model parameter: You can list the models available to your token at any time:
Check the OVHcloud AI Endpoints documentation for the current model list and regional availability.

Streaming responses

OVHcloud’s endpoint supports streaming. Enable it by passing stream=True and iterating over the response:

A note on reasoning models

Some OVHcloud models (for example Qwen3-32B and Qwen3.6-27B) are reasoning models. When called through the raw HTTP API they may return their chain of thought under a reasoning field and the final answer under content. The openai client used in the examples above surfaces the final answer in choices[0].message.content as usual, so no special handling is needed; read message.reasoning only if you want to inspect the thinking trace.