What TKEN base URL should Open WebUI use?

Use https://www.tken.shop/v1 as the OpenAI-compatible API base URL.

Should I expose the TKEN API key to browser users?

No. Keep the API key on the Open WebUI server or deployment environment and avoid exposing it in client-side code.

Open WebUI provider setup

Use TKEN as an OpenAI-compatible Open WebUI provider

Connect Open WebUI to the TKEN gateway when you want a chat UI for GPT, Claude, DeepSeek, Qwen, Kimi, MiniMax and other model families through one OpenAI-compatible endpoint.

Get API key Gateway overview

Docker environment OpenAI-compatible

OPENAI_API_BASE_URLS=https://www.tken.shop/v1
OPENAI_API_KEYS=$TKEN_API_KEY

Use Open WebUI with a custom base URL

Keep the API key server-side

Compare multiple model families from one UI

Minimal docker run pattern

The exact Open WebUI deployment command can vary by version and hosting environment. Keep the TKEN values as environment variables and restart Open WebUI after changing provider configuration.

Example replace your key

docker run -d -p 3000:8080 \
  -e OPENAI_API_BASE_URLS="https://www.tken.shop/v1" \
  -e OPENAI_API_KEYS="$TKEN_API_KEY" \
  -v open-webui:/app/backend/data \
  --name open-webui \
  ghcr.io/open-webui/open-webui:main

Setup checks

1. Create a TKEN API key

Create or copy the key from the TKEN console, then store it as a deployment secret or server environment variable.

2. Set the OpenAI-compatible base URL

Use https://www.tken.shop/v1. If your Open WebUI version exposes an admin UI for OpenAI connections, set the same base URL there.

3. Test with one low-risk prompt

Confirm the model list and one chat response before sharing the workspace with additional users.

TKEN is an independent third-party API gateway. It is not affiliated with Open WebUI or with the upstream model providers referenced on this page.

Connect Open WebUI to TKEN

Use the same gateway base URL in Open WebUI and your SDK smoke tests so your team has one repeatable configuration.

Create account Quickstart