Skip to main content

Configure and Operate Your AI Platform

Choose a maintained path below, verify each result in the Console, and open the detailed task page when you need exact fields, commands, or troubleshooting.

Configure Admin Settings
Admin Overview

Use Admin to configure tenant access and commercial settings, publish routed provider models, or connect GPU infrastructure and operate self-deployed model services.

Docs 2.0 · Admin Console

What You Can Do

  • Configure tenant, branding, users, permissions, pricing, and billing.
  • Register provider credentials and control which models are available.
  • Define routing behavior for routed model traffic.
  • Register GPU clusters and publish model services.
  • Identify which supported tasks can use AdminClient automation.

Who This Is For

Tenant and system administrators · Teams responsible for model resale and pricing · GPU operators publishing self-deployed services

Choose Your Path

01Recommended

Configure the Platform

Set up tenant identity, access, customers, pricing, and billing.

  1. Settings
  2. Theme
  3. User Control
  4. Customer
  5. Pricing and Billing

Result: The tenant is branded, access is controlled, and commercial settings are ready.

Start configuration
02

Configure Router Monetization

Publish provider-backed models through controlled routing.

  1. Provider API Key
  2. Provider Models
  3. Routing Settings
  4. Validate model access

Result: Provider credentials, model availability, and routing policy are configured.

Configure routing
03

Set Up Self-deployment

Use your GPU infrastructure to publish model services.

  1. Model Serving Platform
  2. How to Monetize Your GPUs

Result: A connected cluster runs a model service ready for customer use.

Connect a cluster

Before You Start

  • An Admin account with the permission named by the target menu.
  • Confirmation that the target feature is enabled in this deployment; some items are unavailable to system tenants.
  • Provider credentials or GPU infrastructure only when the selected path requires them.

Core Journey

1Settings2Theme3User Control4Customer5Pricing and Billing

Expected Result

You know which Admin path owns the task, which permission it requires, how to verify the result, and whether AdminClient can automate a supported part of the workflow.

Recommended Next Step

Configure Admin Settings

Availability and permissions​

  • Every Admin task requires the permission named by its menu entry; having a Tenant Console account is not sufficient.
  • Items guarded by banSystem are intentionally unavailable to system tenants. Their absence is an environment constraint, not a documentation or loading error.
  • AdminClient can automate only the operations present in its fixed-version Reference. Actions outside that Reference must be confirmed by an authorized administrator in Admin Console.