Connect your tools
If your tool takes a base URL and a key, it already works. These are the exact settings for the ones people ask about most. Each page has the config, where the key belongs, and what that tool gets wrong.
Guides
Pick your tool
Everything below uses the same base URL, https://api.tium.ai/v1, and the same key.
- AiderAI pair programming in your terminal, pointed at Tium with two environment variables.
- OpenCodeA terminal coding agent that takes a custom provider block in opencode.json.
- PiPoint Pi at the gateway with a models.json entry and an environment variable.
- ClineThe VS Code agent, configured through its settings panel rather than a file.
- Open WebUIThe self-hosted chat UI, pointed at Tium through an admin connection.
- JanThe local-first desktop chat app, with Tium added as a custom provider.
- MstyA desktop chat client that can fetch the whole catalog once it has the endpoint.
- ZedThe editor's agent panel, configured through an openai_compatible provider block.
- ContinueThe VS Code and JetBrains assistant, with Tium as an openai-provider model block.
- Codex CLIOpenAI's terminal agent, pointed at Tium with a custom provider in config.toml.
- GooseBlock's open-source agent, which splits the endpoint across two variables.
- Zoo CodeThe community continuation of Roo Code, set up through its OpenAI Compatible provider.
- llmSimon Willison's CLI, which takes an OpenAI-compatible model with no plugin at all.
- LibreChatA self-hosted multi-model chat UI that takes Tium as a custom endpoint.
- Vercel AI SDKFour lines of createOpenAICompatible. There is no package to wait for.
Everything else
Tools without a page here
There is nothing special about the ones listed above; they are just the ones people ask about.
Anything that accepts an OpenAI-compatible endpoint works without a page of its own. Give it https://api.tium.ai/v1, your key, and a model slug from /models. If you are writing code rather than configuring a tool, the request samples are in the API reference.