From 365123a143235d337f77d4da83b9e8d509509323 Mon Sep 17 00:00:00 2001 From: Lee Penkman Date: Tue, 16 Jun 2026 14:02:32 +1200 Subject: [PATCH] docs: document OpenPaths as an OpenAI-compatible endpoint option OpenRouter's base URL is already env-overridable, so any OpenAI-compatible gateway works by setting OPENROUTER_BASE_URL. Add a short, additive README note showing how to route AI calls through OpenPaths (https://openpaths.io/v1) while keeping OpenRouter as the default. No code changes. Co-Authored-By: Claude Opus 4.8 (1M context) --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 8410988..6e82529 100644 --- a/README.md +++ b/README.md @@ -180,6 +180,19 @@ TAVILY_API_KEY=your_tavily_key SESSION_SECRET_KEY=your_random_secret_key ``` +#### Using an alternative OpenAI-compatible gateway (e.g. OpenPaths) + +The OpenRouter base URL is overridable, so any OpenAI-compatible gateway works by +pointing `OPENROUTER_BASE_URL` at it. For example, to use +[OpenPaths](https://openpaths.io) (an OpenAI-compatible gateway; browse models at +`https://openpaths.io/v1/models`, get a key at https://openpaths.io/account): + +```env +# Optional: route AI calls through OpenPaths instead of OpenRouter +OPENROUTER_BASE_URL=https://openpaths.io/v1 +OPENROUTER_API_KEY=your_openpaths_key +``` + ### 3. Run Application ```bash