Register & Login
End users complete email registration; Operator, End User, and Provider log in and enter their workspaces.
Scenario guides are organized around outcomes: what you want to accomplish. Choose the closest task or scenario, follow the reading order on its overview page, and open the linked user-manual pages when you need page-level field and button details.
| Role | Typical responsibilities |
|---|---|
| Operator | Configure platform capabilities, onboard resources, assign access, process approvals, and review platform monitoring |
| Provider | Publish and maintain models, configure billing and rate limits, and review customer usage and model revenue |
| End User | Discover and try models, request quota, call APIs, and create development, training, or deployment workloads |
If you are unsure which role applies, start with the Role Comparison, then use the role and subsystem filters below. Use each scenario's completion checklist to confirm that the task is actually finished.
Common Tasks
Choose the task closest to your problem to see an ordered reading path. If no task matches, continue with the scenario filters below.
Showing 29 scenarios. If no task matches, filter by user role and subsystem.
End users complete email registration; Operator, End User, and Provider log in and enter their workspaces.
Operators control who can see and operate features through roles, menus, and button permissions.
Providers publish external endpoints, self-owned models, or platform-hosted models as public or private services with billing and throttling.
Prepare standardized meta-models, model sources, templates, and tags to reduce repeated provider configuration.
Wrap multiple published models behind one entry point and route requests by success rate, cost, balance, random, or round-robin policies.
End users discover, try, integrate, and review calls; providers monitor customer-level calling activity.
Convert tokens, duration, and request counts into end-user usage and provider revenue across billing periods.
Obtain spendable balance, record model and card-hour usage, and generate usage, revenue, and billing-period data.
Connect private IDC, local GPU, NPU, or XPU resources to AGIOne as schedulable, metered, and observable resource pools.
Turn inference parameters into templates so users can quickly deploy online inference services.
Deploy online inference services on local resource pools and confirm they are runnable, accessible, and diagnosable.
Support development, training, and data management while accumulating models, images, datasets, and other assets.
Control quotas and monitor resource pool runtime status, capacity, usage, and billing-period metering.
Connect cloud providers, cloud accounts, regions, and resource pools, then authorize tenants or business types to use them.
Configure runtime environments, frameworks, categories, model information, and output APIs as deployable cloud model assets.
Select models from the cloud model marketplace, deploy them, and obtain API calling capability.
Review provider publishing requests for model information, agreements, billing, and throttling governance.
Locate throughput, latency, status, failure, and resource issues from model, organization, and resource perspectives.
Control who can access what, how much they can call, and which keys, projects, models, and quotas they can use.
Reconcile monthly close, financial accounts, and exceptions before generating and reviewing settlement statements.
Explain provider revenue by customer, model, and cycle and reconcile expected settlement, receipt, and transfer.
Control calling scope, cost, and credential lifecycle with project budgets, model allowlists, and purpose-specific keys.
Request, adjust, and limit member quota while coordinating member, project, key, and model-allowlist boundaries.
Review bound models, calling entries, and customer scope, then validate approval, visibility, and calls.
Connect image services, runtime images, and block, file, or object storage and validate them with a test workload.
Design and release rate-control rules from a traffic baseline and verify node versions, hits, and audit details.
Configure preferred pools, capacity thresholds, and failure fallback and validate actual scheduling with a test deployment.
Review activation state, validity, authorization composition, and managed objects and prepare renewal or expansion.
Complete ModelScope model download, Ascend 910B inference template creation, and validate instance deployment, publishing, and API calls.