Region & Model Scope
Applies to: Organization (top-level user), Subuser Updated: 2026-07-02
This article explains how the "available model scope" is determined in the new console, how it affects which groups you can see in the Call Guide, and how to troubleshoot when you "can't see a certain model".
Key difference from the legacy version: the legacy version let tenant admins switch region on their own in "Tenant Settings" to change the available model groups. In the new version, the organization's available model scope is configured by the platform per organization, and the organization cannot change it itself. For scope adjustments, please contact CloudRouter officially.
1. Core Concepts
1.1 Region (Chinese Mainland / Overseas)
CloudRouter still uses "region" as an important dimension of an organization's model availability scope, with two possible values:
- Chinese Mainland: For compliance scenarios centered on domestic models (e.g. DeepSeek, Tongyi Qianwen, GLM, Kimi, Doubao, Hunyuan, iFlytek Spark, etc.).
- Overseas: In addition to domestic models, may include overseas models such as Claude, GPT, and Gemini.
A simple mnemonic: Overseas is usually a "superset", and Chinese Mainland is a "subset". Which groups are ultimately visible to your organization is determined by the available model scope the platform configures for your organization.
⚠️ Overseas models may involve data being transmitted to third-party model providers outside Chinese Mainland for processing. Whether to enable the overseas scope, and who assesses the compliance responsibility, should be confirmed with the platform officially.
1.2 Who Decides the Available Model Scope
| Concept | Applies to | Set by whom |
|---|---|---|
| The service-region label of a model/group | Each group | Configured uniformly by the platform |
| The organization's available model scope | The entire organization | Configured by the platform per organization (the organization cannot modify it itself) |
Which groups an organization can ultimately use is the result of the platform filtering by "group region label + the available scope the platform sets for the organization". Both the organization and its subusers can only use models within this scope and cannot expand it themselves.
2. How the Available Scope Affects What You See
The available model scope directly determines which groups you can see in the console, most visibly on the "Call Guide" page:
- The Call Guide only lists the call names of currently reachable groups (the bare model name and the fingerprinted call name are shown side by side, in the format
<fingerprint>/<bare model name>). - If a model/group is not within your organization's available scope, it will not appear in the Call Guide, and naturally cannot be called.
Therefore, the most common reason for "not seeing a certain model" is: it is not within your organization's available scope. The call names follow what is actually shown on the Call Guide page; see Developer Guide · Call Guide & Dual Routing.
The available scope also affects the group display on the following pages:
- Available Channels / Channel Status
- The routing groups selectable when creating an API Key
- The per-group display in Dashboard and Usage Records
3. What the Organization Can and Cannot Do
| Operation | Can the organization self-serve | Description |
|---|---|---|
| View the currently available groups/models | ✅ | View on the Call Guide, Available Channels, and other pages |
| Create Keys and bind routing groups within the available scope | ✅ | See API Keys & Routing Groups |
| Switch region / expand the available model scope on their own | ❌ | In the new version, the platform configures this per organization; contact CloudRouter for adjustments |
The legacy operation of "tenant admins modifying the region on their own" has been consolidated into the platform's unified configuration in the new version. To learn whether there is a self-service entry, rely on the actual console interface or confirm with the platform officially.
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 platform to apply:
- Organize your request: organization name, the models or groups you want to add/adjust, and the business background (e.g. needing a certain overseas model).
- Contact CloudRouter through a ticket / your business contact / the official customer service email, etc.
- The platform adjusts the available model scope for your organization.
- Once the adjustment takes effect, the new groups appear on the Call Guide and other pages, and can be bound as routing groups when creating a Key.
If overseas models are involved, also confirm the compliance requirements and responsibility attribution for cross-border data transfer.
5. FAQ
Q: Why can't I see models like Claude / GPT / Gemini? A: Most likely these models are not within your organization's current available scope (e.g. the organization is configured for the Chinese Mainland scope). The available scope is configured by the platform per organization, and the organization cannot change it itself. If you do need to use them, contact CloudRouter to apply for an adjustment.
Q: Can I switch the region myself on a settings page like in the legacy version? A: In the new version, the available model scope is configured by the platform, and the organization cannot switch it itself. For scope adjustments, contact the platform officially.
Q: A model is missing from the Call Guide -- does that mean the platform doesn't have it? A: Not necessarily. It is more likely not within your organization's available scope. The Call Guide only shows the groups currently reachable to you. Please confirm with the platform officially whether it can be included in 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 the balance, orders, historical usage, etc.
Q: Can different subusers have different available model scopes? A: The available scope is an organization-level configuration (set by the platform), and subusers under the organization use it within the same scope. For finer-grained differentiation capabilities, please confirm with the platform officially if needed.
Contact Us
- Email: support_cloudrouter@clouditera.com
- QQ community: 712273971
- Platform URL: cloudrouter.online