How-to guides

Dashboard

The dashboard is the operator console for upstream accounts, model routing, Test API, managed API keys, usage history, and notification settings.

Before you start

Enable dashboard authentication in configuration before exposing the dashboard outside a trusted network.

1
Add provider accounts.
Open the provider account section and add OAuth or API-key credentials for each upstream provider.
2
Test a model route.
Use Test API after adding credentials or changing route rules.
3
Create custom models.
Build ctm: aliases when clients need stable names, weights, account targeting, or fallback chains.
4
Manage API keys.
Scope keys by provider and account, then set per-request input caps or optional input-token budgets.

Look for disabled, cooling-down, failed, and quota-exhausted accounts before blaming client requests.

Use provider and account history to confirm routing behavior after changes.

Confirm an alias appears in the catalog returned to the intended client key before publishing it to clients.

Send a notification test after changing Telegram or Google Chat settings.

After each dashboard change, send one Test API request and inspect usage and quota to confirm which provider account handled it.