Use Relixr with other tools

Aider, Codex CLI, Zed, Neovim, and automation platforms like n8n — anything that accepts an OpenAI-compatible base URL.

Any tool that lets you set an OpenAI-compatible base URL and API key can run through Relixr. The pattern is always the same: base URL is https://gateway.relixr.com/v1, API key is a scoped Relixr key.

Aider

zsh

$ export OPENAI_API_BASE="https://gateway.relixr.com/v1"
export OPENAI_API_KEY="nf_live_your_key_here"
aider --model gpt-4o-mini

Codex CLI

zsh

$ export OPENAI_BASE_URL="https://gateway.relixr.com/v1"
export OPENAI_API_KEY="nf_live_your_key_here"
codex

Zed

Zed's Assistant panel accepts a custom OpenAI-compatible provider under Settings → Assistant → Add Provider. Set the base URL to https://gateway.relixr.com/v1 and paste your key.

Neovim (avante.nvim / CodeCompanion)

-- lua/plugins/avante.lua
{
"yetone/avante.nvim",
opts = {
  provider = "openai",
  openai = {
    endpoint = "https://gateway.relixr.com/v1",
    api_key_name = "RELIXR_API_KEY",
    model = "claude-sonnet-4-5",
  },
},
}

Automation: n8n, LangChain, LlamaIndex

Any node or client that takes an OPENAI_API_BASE / baseURL config works the same way — set it to https://gateway.relixr.com/v1 and use a Relixr key as the bearer token. For workflow tools like n8n, create one key per workflow so cost attribution matches your automation, not just "n8n" as a single line item.

Tip:

Automations are the highest-leverage place to set a spend cap — nobody is watching a workflow run in real time, so the cap is what stops a misconfigured loop instead of a person noticing.

Next steps

Use Relixr with Cursor

The same pattern for Cursor.

Agents

Give each automated workflow its own budget and identity.

← Use Relixr with VS Code