router.clavue.com
Clavue Router
Clavue Router at https://router.clavue.com/ is the operator config cloud for TUI and CLI. It stores how a machine mixes a local model with Clavue's official API. Membership never receives the raw keys. The account view only sees a redacted summary.
Overview
Router is not a second model vendor. Chat completions still go to https://api.clavue.com/v1 when the recipe says to use a Clavue product id. Router only holds the operator's routing document and serves the signed-in member a redacted pack.
- Editor: https://router.clavue.com/
- Redacted pack: GET https://www.clavue.com/api/membership/router/pack
- Official models stay on api.clavue.com
- TUI applies the pack locally. It does not upload API keys into the membership file
Operator config
The public summary schema is clavue_operator_config_v1. GET /api/membership/router/pack returns that object plus openUrl. Fields tell you which hops exist and whether a credential is present. They do not contain the credential.
{
"schema": "clavue_operator_config_v1",
"name": "default",
"hasHybrid": true,
"hybridName": "local-plus-clavue",
"localUrl": "http://127.0.0.1:11434/v1",
"localModel": "qwen",
"remoteUrl": "https://api.clavue.com/v1",
"planModel": "clavue-2.1",
"reviewModel": "clavue-2.1-pro",
"reviewUrl": "https://api.clavue.com/v1",
"hasLocalKey": false,
"hasRemoteKey": true,
"hasReviewKey": true,
"effortLevel": "medium",
"fastMode": false,
"mcpServerCount": 2
}Hybrid recipe
The document Router edits is clavue_hybrid_recipe_v1. It is the operator-side recipe: a name, a local hop (base URL and model), a remote hop (base URL and plan model), and an optional review hop. The membership redactor reads hybrid.local, hybrid.remote, and review, then replaces secrets with booleans. local.credential, remote.credential, and review.apikey stay on the operator host.
- schema clavue_hybrid_recipe_v1 on the operator cloud
- hybrid.local.baseUrl / hybrid.local.model — the machine next to the TUI
- hybrid.remote.baseUrl / hybrid.remote.planModel — usually https://api.clavue.com/v1 and a product id such as clavue-2.1
- review.model / review.apiUrl — optional second pass, often clavue-2.1-pro
- What /api/membership/router/pack returns is the redacted clavue_operator_config_v1 summary, not the raw recipe
TUI and CLI sync
On a machine that already ran clavue login, pull the redacted pack and apply it in the TUI provider flow. Headless scripts that only need official models can skip Router and set OPENAI_BASE_URL to https://api.clavue.com/v1.
# Inside Clavue TUI
/provider router pull --apply
# Scripts that only need the official API
export OPENAI_BASE_URL=https://api.clavue.com/v1
export OPENAI_API_KEY="$CLAVUE_TOKEN"SSO cookie
Router is an allowlisted SSO return host. The exact-hostname allowlist includes www.clavue.com, chat.clavue.com, api.clavue.com, router.clavue.com, agent.clavue.com, mail.clavue.com, relay.clavue.com, nas.clavue.com, track.clavue.com, and explorer.clavue.com, and also clavue.com, www.iccjk.com, iccjk.com, localhost, and 127.0.0.1. agent.clavue.com and mail.clavue.com are on that list. Visit the hop while signed in on www. The response re-issues imux_membership_session with Domain=.clavue.com (HttpOnly, SameSite=Lax) and redirects to router.clavue.com. If you are not signed in, the hop sends you to /account?next= that same URL. The pack route then accepts the cookie or a Bearer session token. Unsigned callers get 401.
https://www.clavue.com/api/membership/auth/sso?return=https://router.clavue.com/
curl -s https://www.clavue.com/api/membership/router/pack \
-H "Authorization: Bearer $CLAVUE_TOKEN"Security
Do not paste provider keys into a membership note or a chat transcript and expect Router to store them. The redactor drops credential strings. If a pack shows hasRemoteKey: true, the key exists on the operator side. The JSON you fetched is safe to leave in a log. The recipe on the operator host is not.