Skip to content

Use a neutral example for the gateway endpoint #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
davidmckayv merged 1 commit into from
Aug 19, 2026
Merged

Use a neutral example for the gateway endpoint #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions .env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,14 +60,11 @@ OPENAI_API_KEY=
#
# Model names travel verbatim, so use whatever the endpoint publishes. An endpoint that namespaces
# its catalogue wants both halves of the name, in `BOT_MODEL` and in the tenant package's
# `default_model` alike. LLMTR, a gateway that fronts several providers and hosts models in Turkey
# for deployments that need the data to stay there, addressed that way:
# `default_model` alike:
#
# OPENAI_BASE_URL=https://llmtr.com/v1
# OPENAI_API_KEY=llmtr-...
# BOT_MODEL=openai/gpt-4o # or llmtr/gemma-4, or anthropic/claude-sonnet-4.5
#
# Its catalogue is public and needs no key: https://llmtr.com/v1/models
# OPENAI_BASE_URL=https://gateway.internal/v1
# OPENAI_API_KEY=...
# BOT_MODEL=openai/gpt-4o
#
# OPENAI_BASE_URL=

Expand Down
14 changes: 5 additions & 9 deletions docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,12 +56,12 @@ The other two providers work the same way under their own names, because they ar

Model names travel verbatim, so use whatever the endpoint publishes. An endpoint that namespaces its catalogue wants both halves of the name, in `BOT_MODEL` and in the tenant package's `default_model` alike.

[LLMTR](https://llmtr.com) is one such gateway. It fronts OpenAI, Anthropic, Google and others behind one key, and hosts models in Turkey for deployments that need the data to stay there, which is the same reason a deployment runs OpenBot on its own infrastructure. Addressed the usual way:
A gateway that fronts several providers behind one key is addressed the usual way:

```sh
OPENAI_BASE_URL=https://llmtr.com/v1
OPENAI_API_KEY=llmtr-...
BOT_MODEL=openai/gpt-4o # or llmtr/gemma-4, or anthropic/claude-sonnet-4.5
OPENAI_BASE_URL=https://gateway.internal/v1
OPENAI_API_KEY=...
BOT_MODEL=openai/gpt-4o
```

and in the tenant package, where the name is namespaced the same way:
Expand All @@ -73,11 +73,7 @@ model:
default_model: openai/gpt-4o
```

Its catalogue is public and needs no key, so the names above can be checked before anything is configured:

```sh
curl -s https://llmtr.com/v1/models
```
Most gateways publish a model list, which is the way to check a name before configuring it.

Two things are worth knowing before pointing a deployment at any gateway. Not every catalogue entry accepts tools, and a Bot without tool calling cannot drive its computer; the model list says which do. And `BOT_RESPONSES_API=true` needs an endpoint that implements the Responses API, not only chat completions.

Expand Down