Manage every MiniMax service from one central interface. Create API keys, monitor usage in real time, configure billing, invite team members, and organize work into projects — all from a single dashboard.
The MiniMax platform hub organizes account management into six modules: API keys, usage monitoring, billing, team management, project organization, and account settings.
The hub loads a unified overview page when you sign in. From there, the left sidebar navigates to each module. The overview displays current month spending, active API key count, recent usage chart, team member status, and any active alerts. Each module opens as a full-page view with its own sub-navigation for detailed actions. The hub is responsive — all functions work on desktop, tablet, and mobile browsers. Session timeout is configurable from 15 minutes to 8 hours of inactivity. Two-factor authentication is enforced at login for accounts with the security policy enabled.
API access to hub functions is available through the management API, a separate set of REST endpoints for programmatic account control. Use the management API to automate key rotation, pull usage reports, and manage team members from your internal tools. The management API uses a different authentication scope from the inference API — generate a management key in the hub's API Keys section with the specific admin scope enabled.
The platform hub organizes into six modules: API Keys (create, rotate, revoke), Usage (real-time charts, alerts, CSV export), Billing (invoices, plan management, spending caps), Team (invite members, assign roles, SSO), Projects (group keys and spending, archive), and Settings (security, notifications, account profile). Each module is accessible from the left sidebar after sign-in.
Generate, label, permission-scope, rotate, and revoke API keys from a single interface with full audit logging.
The API Keys module displays all active and revoked keys with their labels, creation dates, last-used timestamps, permission scopes, and associated projects. Create a new key by clicking Generate Key, assigning a descriptive label, and selecting a permission level. Permission levels: Read (usage monitoring only), Standard (API inference access), Admin (full account management including key creation). Each key is shown once at creation — copy and store it immediately. The hub never displays a key's secret again after initial creation. If a key is lost, revoke it and generate a replacement.
Key rotation is built in: generate a new key while the old one is still active, update your application to use the new key, then deactivate the old key from the hub. The key list shows a status indicator (active, rotating, revoked) and the time remaining on keys set to expire. Configure automatic expiration after 30, 90, or 180 days per organizational security policy. Key usage logs show every API call associated with each key, including timestamp, endpoint, model, and token count. Export logs as CSV for external auditing.
Track token consumption, API call volume, video generation minutes, and storage usage with configurable alert thresholds.
The Usage module opens to a real-time dashboard showing current month metrics: total tokens consumed, API call count by endpoint, video generation minutes, and active storage volume. Switch between hourly, daily, and monthly aggregation views. Each graph supports drill-down: click a data point to see the underlying API calls with timestamps and key identifiers. Compare current period usage against the previous period and the same period last month. All usage data is exportable as CSV for integration with internal reporting tools.
Configure usage alerts at thresholds you define. Set alerts at 50%, 80%, and 100% of monthly token limits, spending caps, or per-project budgets. Alert delivery options include email (default), webhook POST to a specified URL, and SMS for enterprise accounts. Each alert includes the current usage percentage, estimated time to reach 100% at current consumption rate, and a direct link to the usage dashboard. Alerts reset at the start of each billing cycle. The alert history log retains all triggered notifications for 12 months.
Invite team members, assign role-based permissions, enforce security policies, and group all work into projects with independent budgets and billing.
Add team members by email, assign roles from Owner to Viewer, and organize into groups with shared access controls.
The Team module lists all members with their roles, last active dates, and API key counts. Invite new members by entering their email address in the invitation field. Invited members receive an email with a link to accept and create their account. Role options: Owner (full account control including plan changes and team management), Admin (key management, billing view, team management without plan changes), Developer (API key generation, usage view for assigned projects), and Viewer (read-only access to usage dashboards). Members can belong to groups that share the same project access and spending limits.
Security policies for teams include: enforce multi-factor authentication for all members or specific roles, require key expiration after a configurable number of days, restrict API access to specific IP ranges via an allowlist, and enable single sign-on through SAML 2.0 or OpenID Connect. SSO configuration accepts Identity Provider metadata URLs and supports just-in-time user provisioning. The security audit log records all team membership changes, role modifications, and permission updates with timestamps and the acting user's identity.
Create projects to isolate API keys, track spending by initiative, and archive completed work while preserving billing records.
Projects serve as organizational containers in the hub. Each project has its own set of API keys, usage tracking, spending caps, and team access controls. Create a project from the Projects module with a name, description, and optional cost center tag. Assign team members or groups to the project with role-specific permissions. The project dashboard shows aggregate usage across all keys in that project with trend charts and cost breakdowns by service (chat API, video generation, model fine-tuning).
Project-level spending caps prevent budget overruns: set a monthly hard cap per project that stops all API activity when reached. Hub administrators receive alerts as projects approach their caps. Archive projects to preserve historical billing data while preventing new API charges and key creation. Archived projects remain viewable in the hub for billing and audit purposes. Delete projects to permanently remove all associated keys, logs, and settings — this action is irreversible and requires owner confirmation. The billing overview consolidates spending across all active projects with a cost allocation table.
Complete reference of platform hub modules with their primary functions and access level requirements.
| Module | Function | Access Level |
|---|---|---|
| Overview | Aggregate dashboard: spending, usage, team status, alerts | Viewer+ |
| API Keys | Generate, label, scope, rotate, revoke keys; view usage logs | Developer+ |
| Usage | Real-time and historical charts; CSV export; threshold alerts | Viewer+ |
| Billing | Invoices, plan management, payment methods, spending caps | Admin+ |
| Team | Invite members, assign roles, create groups, configure SSO | Admin+ |
| Projects | Create, archive, delete projects; assign keys and budgets | Developer+ |
| Settings | Security policies, MFA enforcement, IP allowlist, notifications | Admin+ |
| Audit Log | Security event history, team changes, key activity records | Admin+ |
| Management API | Programmatic access to hub functions; automation integration | Admin (special scope) |
| Notifications | Email, webhook, SMS alert configuration; delivery preferences | Developer+ |
API keys are created in the platform hub under the API Keys section. Generate up to 20 keys per account with configurable permissions: read-only, standard, or admin. Each key displays its creation date, last used timestamp, and associated project. Keys can be revoked instantly. The hub supports key rotation — generate a new key while the old one remains active, then deactivate the old key once your application switches. All key usage is logged and viewable in the security audit page.
The platform hub provides real-time and historical usage monitoring across all MiniMax services. The usage dashboard shows token consumption by model, API call counts by endpoint, video generation minutes, and storage utilization. Graphs support hourly, daily, and monthly aggregation with CSV export. Set usage alerts at configurable thresholds — receive notifications when usage exceeds defined limits. Per-project and per-key breakdowns help teams track spending across initiatives.
Team management lets account owners invite members by email, assign roles (Owner, Admin, Developer, Viewer), and organize members into groups. Developers can generate their own API keys within permitted scopes. Admins can set spending limits per member or group and access audit logs. Teams support SAML 2.0 and OIDC single sign-on for enterprise accounts. MFA can be enforced for all team members. Removing a member automatically revokes their API keys.
Projects in the hub let you group API keys, track spending, and manage configurations for different applications or clients. Each project has its own usage dashboard, spending cap, and team access controls. Tags support cost center tracking. The project overview shows aggregate usage with trend charts. Video batch jobs, fine-tuned models, and stored outputs are scoped to projects. Archive projects to preserve billing history or delete them to clean up inactive work.
The billing section provides real-time spending overview, invoice history, payment method management, and plan comparison. Current month spending updates within 5 minutes of API usage. Switch between plans directly from the hub; changes take effect at the next billing cycle. Invoices are available as PDF downloads with line-item breakdowns. Enterprise accounts get consolidated billing across sub-accounts. Spending caps prevent unexpected charges. Payment methods accepted include credit card and ACH.