Admin Console
The Admin Console manages a tenant's upstream keys, routing, pricing, and notifications. It is a purely static site: account, key, routing, and pricing management call the XSI API directly and map to the public endpoints in these docs; with payment integration enabled, product, order, and revenue management call XPAY_API directly.
Signing in
- Sign in with an XSI API key (51 characters, starting with
sk-Xvs). The console verifies it withGET /dashboard/status; the account must be the tenant owner or have manager permissions. - The key is stored locally in the browser, so reopening the page signs you in automatically. Click Exit in the top-right corner to clear it.
- The sign-in page offers email signup (
POST /x-sign). When referrals are enabled, a referral code can be entered; a?ref=parameter in the URL fills it in automatically. - Switch languages with
EN/δΈin the top-right corner. The English UI lives under/en/. - The bottom of the sign-in page shows the
XSI by XABC Labsattribution and the project link. - The broadcast bar in the navigation and the promotional card on the right are XSI reserved placements. Free use requires keeping them as they are; see section 5 of the LICENSE.
The navigation bar also includes the license badge (LICENSE_ID), a link to the Manage Console, the current account card (R indicates root), and the balance.
AI API
Integration notes and examples: how the system works, OpenAI and Anthropic SDK examples, and cURL examples for Responses, Chat Completions, image generation and editing, and Messages. The base URL in the examples is filled in with the API address of the current deployment and can be copied with one click.
Model Providers
Manages the tenant's upstream provider keys. Corresponds to the Provider Key API.
Stat cards: Total Levels, Total Keys, Active Keys, and Sleeping Keys.
Add New Provider
| Field | Description |
|---|---|
| Name | Optional label, such as OpenAI |
| Level | Required. The key pool group number; the system suggests one based on existing providers of the same kind |
| Common Providers | 32 presets (OpenAI, Claude, Gemini, xAI, DeepSeek, Azure OpenAI, Vertex AI, Alibaba Cloud, Volcano Engine Ark, Zhipu, Moonshot, and more). Selecting one fills in the URL and configuration type |
| Provider | Required. The upstream URL |
| SecretKey | Required. At least 20 characters; stored encrypted |
| Configuration Type | Standard Configuration, Azure OpenAI Configuration (model-to-deployment mapping and API version mapping), or Google Vertex AI Configuration (Base URL, Project ID, Client Email, Private Key) |
| Sleep Policy | No Sleep: the key stays in the rotation pool even when it meets the auto-sleep conditions |
After a key is added, if the backend adjusted the Level mapping automatically, the notification lists the mappings that were added and removed.
Provider List: Grouped by Level and refreshed automatically every 30 seconds. Levels with sticky scheduling enabled carry a "Sticky" tag. Each key shows its status (enabled, disabled, sleeping, auto-sleeping, or long sleep) and the following actions:
| Action | Description |
|---|---|
| Sleep / Wake | Put the key to sleep manually for 32 hours, or wake it immediately |
| Clone | Copy the key with the same Level, Provider, SecretKey, and configuration, to increase its weight in the rotation |
| Edit | Change Name, Level, Provider, SecretKey (leave blank to keep it), configuration, enabled status, and sleep policy |
| Delete | Delete the key. This cannot be undone |
System Config
System Config corresponds to the Tenant Configuration API. Saving submits only the fields that changed, and cleared fields revert to their defaults. Before saving, the console checks for Level mapping conflicts, self-references and cycles in Level failover, and duplicates and cycles in model failover.
Model Pricing (Owner Overrides)
Overrides model prices for this tenant (PRICING). Changes take effect as soon as they are saved:
- Single Model Override: Choose a billing type and model ID, then edit that model's price JSON (it must include
Rates). You can load the current override, view the effective price, fill in a template, and save or delete the override. - Full pricing JSON: Edit all overrides at once, with a template you can fill in with one click.
- Client-side validation: total size β€ 128 KB, at most 1024 entries, and all values finite and non-negative.
Basic Configuration
| Field | Configuration key |
|---|---|
| System Notification Email | XAI_MAIL |
| Allowed Resource Paths | RESOURCES (currently only stored and displayed; to actually restrict access, set the account's Resources) |
| System Model Limits (JSON) | MODEL_LIMITS, with a template; * clears all, -model removes one |
Email Configuration
SMTP Server, SMTP Port, Auth Account, Sender, and Email Password, corresponding to EMAIL_SMTP, EMAIL_PORT, EMAIL_AUTH, EMAIL_SENDER, and EMAIL_PASS. If not configured, the deployment's default mail service is used.
Mapping Configuration
| UI label | Configuration key | Format |
|---|---|---|
| System Model Mapping | MODEL_MAPPER | source-model=target-model |
| System Model Group | LEVEL_MAPPER | model=level |
| Model Group Failover | SWITCH_OVER | primary-level=backup-level |
| Sticky Scheduling Levels | STICKY_LEVELS | A list of Levels; hidden when global sticky scheduling is enabled |
| Model Mapping Failover | MODEL_FAILOVER | primary-model=backup-model |
Signup Security (root only)
The email domain allowlist and denylist (SIGNUP_ALLOW_DOMAINS, SIGNUP_DENY_DOMAINS). Entries can be separated by newlines, commas, or spaces, and *.example.com is supported.
Payments and products (root only, requires XPAY_API)
Once a valid payment gateway URL (including /t/<tenant>) is configured, root can manage the product catalog scope, subscription plans, pay-as-you-go cards, extra usage cards, and services and digital goods here, and handle digital goods order delivery, invoice requests, group-buy launches, and refunds to the original payment method. These actions call the payment gateway API directly.
Revenue (root only, requires XPAY_API)
View data for yesterday, 7 days, this month, last month, 90 days, 1 year, 3 years, or a custom range: payments, refunds, and net revenue for the range; order count and average order value; revenue trend; product type and payment method distribution; plus today's orders, payment ranking, and a daily breakdown.
Broadcast
- Fields: Title (optional), Target ID (optional), and Content (required).
- With a target ID, the notification goes to that account; without one, it goes to the current account's direct sub-accounts (
POST /x-news/{DNA}). Notifications remain valid for 32 days. - "Recent Broadcasts" only keeps the 3 most recent notifications sent from this browser. To delete a sent notification, use
DELETE /x-news/...; see Account Management API.
Operation Logs
Shows the current account's recent management actions (time, action, target, details, and IP; hover to see the User-Agent). Loaded the first time the tab is opened. Corresponds to GET /dashboard/logs.
Deployment configuration
The console reads its runtime parameters from config.js, which is rendered from the container's environment variables. See Configuration Reference.
| Variable | Effect on this console |
|---|---|
XAI_API | API address |
XAI_MANAGE | Link to the Manage Console |
XPAY_API | Enables Revenue and management of products, orders, invoices, group buys, and refunds |
LICENSE_ID | License badge |
BRAND_NAME | Brand name |
XAI_REFERRAL_REWARD_RATE | Signup referral codes and the displayed reward rate |