Overview & Telemetry
Sovereign AI Routing Console
Active Engine
—
LAN Direct
Verified Models (200 OK)
0
Fast & Ready in SQLite
Combo Profiles
0
Load Balance / Failover
Client API Keys
0
SHA-256 Authenticated
Server RAM Free
—
Loading...
Tokens Saved
0
Compressor OFF
System Vault & Storage
Loading...
Recent Requests
| Time | Client | Route / Model | Status |
|---|
AI Agent Chat Studio
—
Client API Mode
Create / Edit Combo Profile
Saved Combo Profiles
| Combo Name | Policy | Sticky | Routing Chain | Action |
|---|
AI Providers, Encrypted Keys & Model Registry
Client API Keys (Gateway Access Control)
| Client Name | Key Prefix | SHA-256 Hash | Requests | Last Used | Status | Action |
|---|
Cloudflare Edge Tunnel (Remote HTTPS Access)
Checking...
Tailscale Permanent HTTPS (Serve / Funnel)
Checking...
Telegram Bot Binding & Online Alerts
Not ConfiguredBind a Telegram Bot to automatically send the Cloudflare Tunnel URL and Client API Keys (sk-9r-...) to the admin whenever the gateway comes online or reboots.
How to Create & Bind a Telegram Bot (Step-by-Step)
- Create a Bot via @BotFather: Open Telegram, search for @BotFather (verified badge) → tap Start → send /newbot → set a display name (e.g. 9Router S805 Alert) and a username ending in bot (e.g. my_9router_s805_bot).
- Copy Your Bot Token: Paste the HTTP API Token from @BotFather (e.g. 123456789:AAH...) into field 1. Telegram Bot Token above.
- Send /start to Your Bot (Required): Open the t.me/<bot_username> link provided by @BotFather and tap Start (or send /start once) so the bot can register your chat.
- Detect Chat ID & Save: Click Auto-Detect Chat ID above → check Enable Telegram Notifications → click Save Telegram Config.
- Test Delivery: Click Send Test Notification to confirm you receive the Cloudflare Tunnel URL and Client API Keys in Telegram.
Group Alerts Tip: Add your bot to a Telegram group → send any message in the group → click Auto-Detect Chat ID (group IDs start with -100...) and Save.
Agent Playground (/v1/chat/completions)
Live Request Telemetry
| Time | Client | Route / Model | Status | Key # |
|---|
Request & Model Error Logs (Last 150 Entries)
| Time | Client | Route / Model | Status | Latency | Key # | Error / Detail |
|---|
Change Admin Login Credentials
Gateway Routing Thresholds & Legacy Token
Google Authenticator (2FA PIN Pairing)
Not PairedPair Google Authenticator to require a 6-digit TOTP PIN after password login (sessions remain valid for 24 hours).