LowRouterBeta

Integrations

LowRouter speaks the OpenAI Chat Completions API. Anything that talks to OpenAI can talk to LowRouter, usually after you change the base URL and the API key.

Each page in this section is a working snippet plus the few things that tend to surprise people on first use. Pages for tools with a scriptable mode name the release they were verified against, and their config blocks are re-run against that release every week, so a snippet you paste from them worked verbatim within the last seven days. GUI-only tools (Cursor, Cline, the chat apps) are documented the same way but checked by hand.

SDKs and HTTP

Frameworks

  • Frameworks: LangChain, LlamaIndex, CrewAI, the Vercel AI SDK and n8n.

Chat apps

  • Chat apps: Chatbox, Jan, LibreChat, and any other OpenAI-compatible chat client.

Coding agents

  • Claude Code: Anthropic’s terminal coding agent, via the Anthropic-native /v1/messages endpoint.
  • OpenCode: terminal coding assistant.
  • Cursor: AI code editor, through its OpenAI base URL override.
  • Cline: VS Code coding agent.
  • Kilo Code: VS Code agent and terminal CLI; also covers Roo Code.
  • Continue: VS Code and JetBrains assistant with the cn terminal agent.
  • Goose: Block’s open-source agent.
  • Aider: terminal pair-programming agent.

Autonomous agents

These run long, multi-step tasks on their own, often unattended, and resend a large context on every step. Give each one a dedicated key, so its spend is attributed and it can be revoked on its own.

  • OpenHands: open-source software agent, headless from the CLI.
  • Hermes Agent: Nous Research’s agent with memory and skills that persist across sessions.
  • OpenClaw: personal agent that answers from chat apps, a terminal or a schedule.

Other

Base URL and auth

The base URL for every integration is:

Text
https://api.lowrouter.ai/v1

The auth header is:

Text
Authorization: Bearer $LOWROUTER_API_KEY

The rest is per-tool configuration.

The one exception is Claude Code and anything else built on the Anthropic SDK, which talk to /v1/messages instead of /v1/chat/completions and send the key as x-api-key. That endpoint accepts either header; every other endpoint takes Authorization: Bearer.