Your own models and keys
Besides the platform catalog, a workspace can bring its own models: an OpenAI-compatible provider connection stores a base URL, a key and the list of models you allow. One key serves models of all three kinds — chat, embeddings and rerank.
Connecting a provider
- Open Settings → Integrations and create an OpenAI-compatible provider connection.
- Fill in the Base URL (for example
https://api.openai.com/v1) and the API key. - Press Load from provider — the platform asks that endpoint for its model list. If the provider does not serve one, use Add manually.
- Turn on the models you want: loaded models arrive disabled.
- Pick the Model purpose on each row — Chat, Embeddings or Rerank.
- Save the connection.
Integrations
OpenAI-compatible provider
Text is always accepted; the modality chips restrict which attachments are sent to the model.
How a model reaches the dropdowns
A connection model gets an id of the form ws:<connection id>:<model id> and sits next to
the catalog models — but only in the dropdown that matches its purpose:
| Purpose | Where it appears | Example label |
|---|---|---|
| Chat | the Model field of the llm node | Acme OpenAI · gpt-4o |
| Embeddings | the embedding node, knowledge-base creation | Acme OpenAI · text-embedding-3-small |
| Rerank | the rerank node | Acme OpenAI · rerank-v3.5 |
The label is “connection name · model label”, so two connections carrying the same model stay distinguishable. In Settings → Models these rows live under the workspace group, and their visibility is toggled there too.
Fallback chains
A separate connection kind is the fallback chain. It is assembled from models you already connected, listed in the order they are tried, and appears in the LLM dropdown as a single entry. Checkboxes decide what makes the chain advance — request timeouts, HTTP 4xx, HTTP 5xx.
Media and web search
Media nodes and the web-search node take a different route: they run through OpenRouter, so your own key is supplied by an OpenRouter connection and picked in the node’s connection field. Leave that field empty and the node uses the platform key.
What this does to billing
Your model runs on your key and the provider bills you, so the platform does not meter its tokens — otherwise the same work would be paid for twice.
| Charge | Catalog model | Your model (BYO) |
|---|---|---|
| Workflow run | 1 credit | 1 credit |
| Each LLM node | 1 credit | 1 credit |
| LLM tokens | the model's tariff | not billed |
| Embedding and rerank tokens | billed | no ledger row at all |
The tokens of a BYO call stay visible under Usage — the node really did run — but their price is zero.