Use Augure with Open WebUI
Add Augure's Canadian, OpenAI-compatible API as an OpenAI connection in Open WebUI, via the admin panel or Docker environment variables.
Updated 2026-10-26 · Configuration shown as documented by the tool; not yet verified end to end by Augure. · Markdown version
You get Augure models in Open WebUI's model picker for every user of your instance, with inference on Canadian infrastructure.
Prerequisites
- A running Open WebUI instance (Docker or pip) with an admin account.
- An Augure API key (
aug_sk_live_…) from the developer dashboard. Plans and pricing: augureai.ca/developers.
Configure
In the admin panel
- Open Admin Panel > Settings > Connections.
- Under OpenAI API, add a connection (the
+button). - Enter the URL and key:
URL: https://api.augureai.ca/v1
Key: aug_sk_live_...
- Save. Open WebUI calls
/v1/modelson the connection and listsossington-5,rosedale-1,tofino-3,autoand the others in the model picker.
With environment variables
For a fresh Docker deployment, the same connection can be set at start:
docker run -d -p 3000:8080 \
-e OPENAI_API_BASE_URL=https://api.augureai.ca/v1 \
-e OPENAI_API_KEY=aug_sk_live_... \
-v open-webui:/app/backend/data \
--name open-webui ghcr.io/open-webui/open-webui:main
To run Augure alongside another OpenAI-compatible provider, use the plural forms OPENAI_API_BASE_URLS and OPENAI_API_KEYS with ; between values. Settings saved in the admin panel take precedence over environment variables after first start.
Pick a model
| Model | When to use |
|---|---|
ossington-5 |
Flagship reasoning. 256K context, 32,768 max output. Default for hard questions and documents. |
rosedale-1 |
Premium reasoning, up to 1M context on paid plans, Canadian inference. Very long documents. |
tofino-3 |
Fast everyday model, 256K context, 16,384 max output, no thinking. Everyday chat. |
auto appears in the picker and lets the gateway pick. On ossington-5, reasoning_effort none turns thinking off; Open WebUI exposes a Reasoning Effort field in a model's advanced parameters (Workspace > Models > edit) in recent versions, though its allowed values may not include none. Full list: /docs/models.
You can hide models you do not want users to see under Admin Panel > Settings > Models, and set a default model per instance.
Verify it works
Start a new chat, pick tofino-3 and send "Reply with the single word OK." For the residency check, call the API once from the host:
curl -s https://api.augureai.ca/v1/chat/completions \
-H "Authorization: Bearer $AUGURE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"tofino-3","max_tokens":64,"messages":[{"role":"user","content":"Reply with the single word OK."}]}'
The JSON ends with an _augure block, for example "_augure": {"gateway_region": "ca-montreal-1", "inference_region": "ca-on-toronto", "request_id": "..."}. inference_region tells you where the model ran. Inference is on Canadian infrastructure first, with disclosed failover to vetted EU partners under zero data retention, never the US.
Notes
- Open WebUI streams by default; Augure returns usage in the final chunk when
stream_options.include_usageis set, which Open WebUI does in recent versions. - Reasoning models return their thinking in
reasoning_content; recent Open WebUI versions render it as a collapsible block above the answer. - Images pasted into a chat are sent as
image_urlcontent parts, whichossington-5androsedale-1accept. Augure Open models (open-glm-5-3,open-qwen-3.8-flash-next) are text only. - Open WebUI's title and tag generation uses the selected model by default; point it at
tofino-3under Admin Panel > Settings > Interface to keep those calls fast.