Skip to main content
Open WebUI is often used as a self-hosted team chat entry point. Add Moxus AI as an OpenAI-compatible connection to route requests through your Moxus AI account.

​
Values

FieldValue
OpenAI API Base URLhttps://moxus.ai/v1
OpenAI API Keysk-your-key
ModelCopy the exact model name from Models and pricing

​
Environment variables

For self-hosted deployments, set: 
OPENAI_API_BASE_URL=https://moxus.ai/v1
OPENAI_API_KEY=sk-your-key
If your Open WebUI version supports multiple OpenAI connections, add a connection in the admin UI named Moxus AI and set Base URL to https://moxus.ai/v1.

​
Docker example

docker run -d \
  -p 3000:8080 \
  -e OPENAI_API_BASE_URL="https://moxus.ai/v1" \
  -e OPENAI_API_KEY="sk-your-key" \
  ghcr.io/open-webui/open-webui:main
Exact options may vary by Open WebUI version. For existing deployments, prefer updating the current admin UI or Compose file.

​
Admin guidance

  • Create a separate API key for Open WebUI and set a quota limit.
  • Enable login and user permissions if multiple people share the WebUI.
  • Do not expose keys in frontend pages or public environment files.
  • Review Usage regularly for source and cost.

​
Troubleshooting

Check the Compose file or container environment and restart the container. Some versions may override environment variables with admin UI settings.
Add Moxus AI model names in Open WebUI model management, or confirm whether your version recognizes the model list endpoint.
If everyone shares one API key, Moxus AI sees one key source. For finer audit trails, log users in Open WebUI or split keys by use case.

​
Next steps