Regions and Model Scope
Applicable roles: Organization (top-level user), sub-users Last updated: 2026-07-14
This document explains how the "available model scope" is determined in the new console, how it affects which groups you can see in the invocation guide, and how to troubleshoot when you "can't see a certain model."
Key difference from the old version: The old version allowed tenant administrators to switch regions on their own in "Tenant Settings" to change the available model groups. In the new version, an organization's available model scope is configured by the platform per organization, and organizations cannot change it themselves. For any scope adjustments, please contact the platform officially.
1. Core Concepts
1.1 Region (Chinese Mainland / Overseas)
The platform still uses "region" as an important dimension for an organization's available model scope, with two possible values:
- Chinese Mainland: For compliance scenarios centered on domestic models (such as DeepSeek, Tongyi Qianwen, GLM, Kimi, Doubao, Hunyuan, iFlytek Spark, etc.).
- Overseas: In addition to domestic models, this may include overseas models such as Claude, GPT, and Gemini.
Simple way to remember: Overseas is usually the "superset," and Chinese Mainland is the "subset." Which groups are actually visible to your organization is ultimately determined by the available model scope the platform configured for your organization.
⚠️ Overseas models may involve data being transmitted to third-party model service providers outside Chinese Mainland for processing. Whether to enable the overseas scope, and who evaluates the compliance responsibility, should be confirmed with the official team.
1.2 Who Determines the Available Model Scope
| Concept | Applies to | Set by |
|---|---|---|
| Service region label of a model/group | Each group | Configured uniformly by the platform |
| Organization's available model scope | Entire organization | Configured by the platform per organization (organizations cannot modify it themselves) |
Which groups an organization can ultimately use is the result of the platform filtering by "group region label + available scope set by the platform for the organization." Both organizations and sub-users can only use models within this scope and cannot expand it on their own.
2. How the Available Scope Affects What You See
The available model scope directly determines which groups you can see in the console. There are two ways to view them: the "Model Marketplace" page (no login required, lists all public models) and the "Invocation Guide" page (login required, lists the models you can actually reach):
- The invocation guide lists the invocation names of currently reachable groups. After group-identifier routing is enabled, the model name is displayed side by side with the invocation name that includes the group identifier (format:
<group-identifier>/<model-name>). - If a model/group is not within your organization's available scope, it will not appear in the invocation guide or the model marketplace, and naturally cannot be invoked.
Therefore, the most common reason for "not being able to see a certain model" is: it is not within your organization's available scope. Invocation names are determined by what is actually displayed on the model marketplace or invocation guide pages; see Developer Guide · Invocation Guide and Routing for details.
The available scope also affects the group display on the following pages:
- Channel status (this page shows available channels and their health status)
- Routing groups selectable when creating an API key
- Group-based display in the dashboard and usage records
3. What Organizations Can and Cannot Do
| Action | Can the organization do it on its own | Notes |
|---|---|---|
| View currently available groups/models | ✅ | View on pages such as the Model Marketplace, Invocation Guide, and Channel Status |
| Create keys and bind routing groups within the available scope | ✅ | See API Keys and Routing Groups |
| Switch regions / expand the available model scope on your own | ❌ | In the new version, this is configured by the platform per organization; contact the platform for adjustments |
The old version's "tenant administrator switching regions on their own" operation is now centralized under platform configuration in the new version. To find out whether there is a self-service entry point, refer to the actual console interface or confirm with the official team.
4. How to Adjust the Available Model Scope
The available scope is configured uniformly by the platform, and the adjustment process is to contact the official team to apply:
- Prepare your requirements: organization name, the models or groups you want to add/adjust, and the business context (e.g., needing to use a certain overseas model).
- Contact the platform through channels such as a support ticket, your business contact, or the official customer service email.
- The platform adjusts the available model scope for your organization.
- Once the adjustment takes effect, the new groups will appear on pages such as the Model Marketplace and Invocation Guide, and can then be bound as routing groups when creating a key.
If overseas models are involved, please also confirm the compliance requirements and responsibility for cross-border data transfer.
5. FAQ
Q: Why can't I see models such as Claude / GPT / Gemini? A: Most likely these models are not within your organization's current available scope (for example, the organization is configured for the Chinese Mainland scope). The available scope is configured by the platform per organization, and organizations cannot change it themselves. If you do need to use them, please contact the platform to apply for an adjustment.
Q: Can I switch regions myself on the settings page like in the old version? A: In the new version, the available model scope is configured by the platform, and organizations cannot switch it themselves. To adjust the scope, please contact the official team.
Q: If a certain model isn't in the invocation guide, does that mean the platform doesn't have it? A: Not necessarily. The invocation guide only shows the models your organization can currently reach; models outside the available scope will not be shown. You can also check the "Model Marketplace" for the list of models the platform publicly offers. If it appears in neither place, it is more likely that it is not within your organization's available scope. Please contact the official team to confirm whether it can be added to your available scope.
Q: Will adjusting the available scope affect my balance or historical data? A: The available scope only determines "which models/groups are visible and usable"; it does not change your balance, orders, historical usage, etc.
Q: Can different sub-users have different available model scopes? A: The available scope is an organization-level configuration (set by the platform), and sub-users under the organization use models within the same scope. If you need more fine-grained differentiation, please contact the official team to confirm.