OpenAI-compatible endpoints
The generic path, which covers most providers.
LensHub speaks the OpenAI API format. Anything that implements it works, whether or not it is OpenAI.
Settings
| Setting | What it is |
|---|---|
| Provider | openai for anything OpenAI-compatible |
| Base URL | The API root, ending in /v1. Leave empty for OpenAI itself |
| API key | Your key. Some local servers accept any value |
| Chat model | The model name, exactly as the provider spells it |
| Embed model | Optional. Leave empty to use the bundled local embedding model |
Example: a hosted provider
Provider: openai
Base URL: https://api.example-provider.com/v1
API key: your-key
Chat model: their-model-nameKeeping the local embedding model
Setting a chat provider does not move embeddings off your instance. Unless you deliberately set an embed model and endpoint, embedding stays local — so your content is not sent anywhere to be indexed.
That is usually what you want. Embedding touches every chunk of every document; chat touches only what a person asks about.
Checking it works
Open the chat interface and ask anything. A configuration error shows up immediately there, rather than silently failing later during a sync.
The API key is stored encrypted, and the interface only ever shows it masked. Even so, use a key scoped to this purpose so you can rotate it independently.