> ## Documentation Index
> Fetch the complete documentation index at: https://docs.modelstudio.console.alibabacloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Obtain an API key

> Before you use models or applications in Alibaba Cloud Model Studio, you must obtain an API key for authentication.

This topic describes the pay-as-you-go API key for Model Studio. If you are using a Token Plan or Coding Plan, use the corresponding dedicated API key (starts with `sk-sp-`). For more information, see [Token Plan API Key](/en/model-studio/token-plan-team-quickstart) and [Coding Plan API Key](/en/model-studio/coding-plan#2531c37fd64f9).

## Create an API key <span id="c38fb45bc6sje" /> <span id="ca06817d4cqro" />

This procedure must be performed by an [Alibaba Cloud account](/en/model-studio/permission-management-overview) or a [RAM user](/en/model-studio/permission-management-overview) with `administrator` or `API-Key` [page permissions](/en/model-studio/permission-management-overview).

<Tabs>
  <Tab title="China (Beijing), Singapore, and other regions">
    1. Go to the Alibaba Cloud Model Studio [API Key](https://modelstudio.console.alibabacloud.com/ap-southeast-1/settings/api-key) page, select a region in the upper-right corner, and then click <strong>Create API Key</strong>. Each region has its own endpoint, API keys, and model list. They cannot be used across regions. For the API key page and endpoint of each region, see [Regional access information](/en/model-studio/regions#h2_cc92e61c).
    2. In the dialog box, configure the following settings, and then click <strong>OK</strong>.

       - <strong>Workspace</strong>: We recommend that you select the default workspace.
       - <strong>Description</strong> (optional, up to 200 characters): Enter a description to help you identify the purpose of the API key.
       - <strong>Permissions</strong>: We recommend that you select <strong>All</strong>. For more granular control, select <strong>Custom</strong> to configure accessible IP addresses and models. Model Studio provides two types: <strong>All</strong> grants permission to call any model or application; <strong>Custom</strong> allows you to configure an <strong>IP address whitelist</strong> and an <strong>accessible model scope</strong>. By default, all IPv4 (`0.0.0.0/0`) traffic is allowed; support for IPv6 is available only in the China (Beijing) region. You can add up to <strong>20</strong> IPv4 or IPv6 addresses or CIDR blocks to the IP address whitelist. When the <strong>Access Scope</strong> toggle is enabled, you can select the models that the API key is allowed to call from the model list (for example, Qwen3.7-Plus and Qwen3.7-Max). After configuration, click <strong>OK</strong>.
    3. After the key is created, the complete API key and API Host (service endpoint address) are displayed in a dialog box. You must copy or download and save them immediately. Keep them confidential. Anyone with your API key can make service requests on your behalf, which may incur charges. After you close the dialog box, you <strong>cannot view or copy</strong> the plaintext API key again. If the key is lost, reset it or create a new one. An Alibaba Cloud account can view the API keys in all workspaces. A RAM user can view only the API keys in the workspaces that they have joined.
  </Tab>

  <Tab title="US (Virginia) region">
    1. Go to the [Alibaba Cloud Model Studio console](https://modelstudio.console.alibabacloud.com/us-east-1). In the upper-right corner, switch the region to <strong>US (Virginia)</strong>. Choose <strong>API Key</strong> from the left-side navigation pane. On the API key management page, click <strong>Create API Key</strong>.
    2. In the dialog box, configure the following information, and then click <strong>OK</strong>.

       - <strong>Workspace</strong>: We recommend that you select the default workspace.
       - <strong>Description</strong>: Enter a description to help you identify the purpose of the API key.
       - <strong>Permissions</strong>: We recommend that you select <strong>All</strong>. For more granular control, select <strong>Custom</strong> to configure accessible IP addresses and models. By default, all IPv4 (`0.0.0.0/0`) traffic is allowed. IPv6 is not supported in the US (Virginia) region. You can add up to <strong>20</strong> IPv4 addresses or CIDR blocks to the IP address whitelist. Separate multiple entries with commas.
    3. After the key is created, the complete API key is displayed in a dialog box. Copy it immediately and store it securely. You cannot view the complete API key again after you close the dialog box.
    4. In the API key list, click the <Image src="https://help-static-aliyun-doc.aliyuncs.com/assets/img/en-US/2182544571/p994217.png" alt="image" className="inline" noZoom /> icon next to an API key to copy the masked key. An Alibaba Cloud account can view the API keys in all workspaces. A RAM user can view only the API keys in the workspaces that they have joined. Click the <strong>+ Create API key</strong> button in the upper-right corner to create a new API key.
  </Tab>
</Tabs>

<Accordion title="API key management operations" defaultOpen>
  In the API key list, you can perform the following operations on existing API keys:

  - <strong>Edit</strong>: Modify the description and permission settings of the API key.
  - <strong>Delete</strong>: Permanently delete the API key. This operation cannot be undone.
  - <strong>Disable</strong> (not supported in the US (Virginia) region): Suspend the API key without deleting it. You can re-enable it at any time.
  - <strong>Reset</strong> (not supported in the US (Virginia) region): Generate a new key value. The old key becomes invalid immediately.
</Accordion>

<Accordion title="When to use other owner accounts or workspaces">
  If you require team collaboration or cost allocation, consider the following:

  - <strong>Workspace</strong>: A workspace is used to isolate resources and permissions for different projects or teams. To control which models a user group can call or to allocate costs for model calls, create or select a sub-workspace from the list.

  For more information, see [API key permissions](/en/model-studio/permission-management-overview#f2704153a055r) and [Query bills and manage costs](/en/model-studio/bill-query-and-cost-management).
</Accordion>

## Configure API key as an environment variable <span id="h2_env_var_config" /> <span id="section_env_var_config" />

We recommend setting your API key as an environment variable. This helps you avoid hard-coding the key in your source code, reducing the risk of accidental exposure.

<Tabs>
  <Tab title="Linux">
    <Tabs>
      <Tab title="Permanent">
        To make the API key available in all new sessions for the current user, set it as a permanent environment variable.

        1. Run the following command to append the environment variable setting to the `~/.bashrc` file.

        ```bash
        # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
        echo "export DASHSCOPE_API_KEY='YOUR_DASHSCOPE_API_KEY'" >> ~/.bashrc
        ```

        Alternatively, you can manually edit the `~/.bashrc` file.

        <Accordion title="Manual modification">
          Run the following command to open the `~/.bashrc` file.

          ```zsh
          nano ~/.bashrc
          ```

          Add the following content to the configuration file.

          ```bash
          # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
          export DASHSCOPE_API_KEY="YOUR_DASHSCOPE_API_KEY"
          ```

          In the nano editor, press Ctrl+X, then Y, and then Enter to save and close the file.
        </Accordion>

        2. Run the following command to apply the changes.

        ```bash
        source ~/.bashrc
        ```

        3. Open a new terminal window and run the following command to verify that the environment variable is set.

        ```bash
        echo $DASHSCOPE_API_KEY
        ```
      </Tab>

      <Tab title="Temporary">
        To use the environment variable only for the current session, set it as a temporary environment variable.

        1. Run the following command.

        ```bash
        # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
        export DASHSCOPE_API_KEY="YOUR_DASHSCOPE_API_KEY"
        ```

        2. Run the following command to verify that the environment variable is set.

        ```bash
        echo $DASHSCOPE_API_KEY
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="macOS">
    <Tabs>
      <Tab title="Permanent">
        To make the API key available in all new sessions for the current user, set it as a permanent environment variable.

        1. Run the following command in your terminal to check your default shell type.

        ```bash
        echo $SHELL
        ```

        2. Proceed based on your default shell type.

           <Tabs>
             <Tab title="Zsh">
               1. Run the following command to append the environment variable setting to the `~/.zshrc` file.

               ```zsh
               # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
               echo "export DASHSCOPE_API_KEY='YOUR_DASHSCOPE_API_KEY'" >> ~/.zshrc
               ```

               Alternatively, you can manually edit the `~/.zshrc` file.

               <Accordion title="Manual modification">
                 Run the following command to open the shell configuration file.

                 ```zsh
                 nano ~/.zshrc
                 ```

                 Add the following content to the configuration file.

                 ```bash
                 # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
                 export DASHSCOPE_API_KEY="YOUR_DASHSCOPE_API_KEY"
                 ```

                 In the nano editor, press Ctrl+X, then Y, and then Enter to save and close the file.
               </Accordion>

               2. Run the following command to apply the changes.

               ```zsh
               source ~/.zshrc
               ```

               3. Open a new terminal window and run the following command to verify that the environment variable is set.

               ```zsh
               echo $DASHSCOPE_API_KEY
               ```
             </Tab>

             <Tab title="Bash">
               1. Run the following command to append the environment variable setting to the `~/.bash_profile` file.

               ```zsh
               # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
               echo "export DASHSCOPE_API_KEY='YOUR_DASHSCOPE_API_KEY'" >> ~/.bash_profile
               ```

               Alternatively, you can manually edit the `~/.bash_profile` file.

               <Accordion title="Manual modification">
                 Run the following command to open the shell configuration file.

                 ```bash
                 nano ~/.bash_profile
                 ```

                 Add the following content to the configuration file.

                 ```bash
                 # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
                 export DASHSCOPE_API_KEY="YOUR_DASHSCOPE_API_KEY"
                 ```

                 In the nano editor, press Ctrl+X, then Y, and then Enter to save and close the file.
               </Accordion>

               2. Run the following command to apply the changes.

               ```zsh
               source ~/.bash_profile
               ```

               3. Open a new terminal window and run the following command to verify that the environment variable is set.

               ```zsh
               echo $DASHSCOPE_API_KEY
               ```
             </Tab>
           </Tabs>
      </Tab>

      <Tab title="Temporary">
        To use the environment variable only for the current session, set it as a temporary environment variable. The following command applies to both Zsh and Bash.

        1. Run the following command.

        ```bash
        # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
        export DASHSCOPE_API_KEY="YOUR_DASHSCOPE_API_KEY"
        ```

        2. Run the following command to verify that the environment variable is set.

        ```bash
        echo $DASHSCOPE_API_KEY
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Windows">
    In Windows, you can configure an environment variable by using System Properties, Command Prompt, or Windows PowerShell.

    <Tabs>
      <Tab title="System Properties">
        - Environment variables configured this way are permanent.
        - You need administrator permissions to modify system environment variables.
        - Changes to environment variables do not affect running applications, including Command Prompt windows and IDEs. You must restart these applications or open a new command-line session to apply the changes.

        1. On the Windows desktop, press `Win+Q`, search for <strong>Edit the system environment variables</strong> in the search box, and click the search result to open the <strong>System Properties</strong> window.
        2. In the <strong>System Properties</strong> window, click <strong>Environment Variable</strong>, and then in the <strong>System variables</strong> section, click <strong>Create</strong>. For <strong>Variable Name</strong>, enter `DASHSCOPE_API_KEY`, and for <strong>Variable value</strong>, enter your DashScope API Key.
        3. Click <strong>OK</strong> on all three open windows to save the changes and close them.
        4. Open a new Command Prompt or Windows PowerShell window and run the appropriate command to verify that the environment variable is set.

           - In Command Prompt:

        ```powershell
        echo %DASHSCOPE_API_KEY%
        ```

        ```cmd
        Microsoft Windows [Version 10.0.19045.5371]
        (c) Microsoft Corporation. All rights reserved.
        C:\Windows\system32>echo %DASHSCOPE_API_KEY%
        sk-ee16697?fe4
        C:\Windows\system32>
        ```

        - In Windows PowerShell:

        ```powershell
        echo $env:DASHSCOPE_API_KEY
        ```

        ```powershell
        Windows PowerShell
        Copyright (C) Microsoft Corporation. All rights reserved.
        Try the new cross-platform PowerShell https://aka.ms/pscore6
        PS C:\Windows\system32> echo $env:DASHSCOPE_API_KEY
        sk-ee166797fe40xxx
        PS C:\Windows\system32>
        ```
      </Tab>

      <Tab title="Command Prompt">
        <Tabs>
          <Tab title="Permanent">
            To make the API key environment variable available in all new sessions for the current user, follow these steps.

            1. Run the following command in Command Prompt.

            ```bash
            REM Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
            setx DASHSCOPE_API_KEY "YOUR_DASHSCOPE_API_KEY"
            ```

            2. Open a new Command Prompt window for the change to take effect.
            3. In the new Command Prompt window, run the following command to verify that the environment variable is set.

            ```bash
            echo %DASHSCOPE_API_KEY%
            ```
          </Tab>

          <Tab title="Temporary">
            To use the environment variable only in the current session, run the following command in Command Prompt.

            ```cmd
            REM Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
            set DASHSCOPE_API_KEY=YOUR_DASHSCOPE_API_KEY
            ```

            You can run the following command in the same session to verify that the environment variable is set.

            ```bash
            echo %DASHSCOPE_API_KEY%
            ```
          </Tab>
        </Tabs>
      </Tab>

      <Tab title="Windows PowerShell">
        <Tabs>
          <Tab title="Permanent">
            To make the API key environment variable available in all new sessions for the current user, follow these steps.

            1. Run the following command in Windows PowerShell.

            ```powershell height="62"
            # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
            [Environment]::SetEnvironmentVariable("DASHSCOPE_API_KEY", "YOUR_DASHSCOPE_API_KEY", [EnvironmentVariableTarget]::User)
            ```

            2. Open a new Windows PowerShell window for the change to take effect.
            3. In the new Windows PowerShell window, run the following command to verify that the environment variable is set.

            ```powershell
            echo $env:DASHSCOPE_API_KEY
            ```
          </Tab>

          <Tab title="Temporary">
            If you want to use the environment variable only in the current session, you can run the following command in PowerShell.

            ```powershell
            # Replace YOUR_DASHSCOPE_API_KEY with your DashScope API key
            $env:DASHSCOPE_API_KEY = "YOUR_DASHSCOPE_API_KEY"
            ```

            You can run the following command in the same session to verify that the environment variable is set.

            ```powershell
            echo $env:DASHSCOPE_API_KEY
            ```
          </Tab>
        </Tabs>
      </Tab>
    </Tabs>
  </Tab>
</Tabs>

## Use an API key <span id="20b17d4430qvt" /> <span id="6a82f1a968bhf" />

- <strong>Method 1: Call models from</strong>[<strong>third-party tools</strong>](/en/model-studio/use-chat-client-or-development-tool)

  Configuration guides for common tools: [Chatbox](https://www.alibabacloud.com/help/model-studio/cline-tool), [Cline](/en/model-studio/cline), [Claude Code](/en/model-studio/claude-code), [Dify](/en/model-studio/dify), [OpenClaw](/en/model-studio/openclaw), [Postman](/en/model-studio/first-call-to-image-and-video-api), and [Qwen Code](/en/model-studio/qwen-code).

- <strong>Method 2: Call models by using code</strong>

  When you [call the Qwen API](/en/model-studio/first-api-call-to-qwen) for the first time by using code, we recommend that you [configure the API key as an environment variable](/en/model-studio/get-api-key#section_env_var_config) to avoid hard-coding it in your code, which reduces the risk of leaks.

When you call a model from code or a third-party tool, in addition to the API key you must specify a <strong>service endpoint</strong> (the <strong>API Host</strong> shown in the creation success dialog, which corresponds to the `base_url` in your SDK or HTTP request). Model Studio provides both <strong>OpenAI-compatible</strong> and <strong>Anthropic-compatible</strong> protocol interfaces. The `base_url` differs between the two protocols and varies by region. Refer to the documentation for the protocol you use:

- OpenAI-compatible protocol: [OpenAI compatible - Chat](/en/model-studio/compatibility-of-openai-with-dashscope)
- Anthropic-compatible protocol: [Anthropic-compatible Messages](/en/model-studio/anthropic-api-messages)

Do not expose your API key.

## API key security upgrade <span id="h2_apikey_security_upgrade" /> <span id="sec_apikey_security_upgrade" />

Model Studio has upgraded the pay-as-you-go API key generation and storage mechanism for enhanced security (except for the US (Virginia) region). API keys created before the upgrade that start with `sk-` remain fully functional and are not affected. All API keys created after the upgrade start with `sk-ws`.

The following table describes the main differences between API keys created before and after the upgrade.

<table style={{ display: "table", tableLayout: "fixed", width: "100%" }}><colgroup><col style={{ width: "16.93%" }} /><col style={{ width: "41.61%" }} /><col style={{ width: "41.46%" }} /></colgroup><thead><tr><th><p><strong>Comparison item</strong></p></th><th><p><strong>Pre-upgrade keys</strong></p></th><th><p><strong>Post-upgrade keys</strong></p></th></tr></thead><tbody><tr><td><p><strong>Key format</strong></p></td><td><p>Starts with <code>sk-</code> and is about 32 characters long.</p></td><td><p>Starts with <code>sk-ws</code> and is longer than the previous format.</p></td></tr><tr><td><p><strong>Plaintext viewing</strong></p></td><td><p>You can copy the complete plaintext key from the console at any time.</p></td><td><p>The plaintext key is displayed only once upon creation. It cannot be viewed again after the dialog box is closed. If lost, reset or create a new key.</p></td></tr><tr><td><p><strong>Calling capability</strong></p></td><td><p>Can be used to call models normally; functionality is unaffected.</p></td><td><p>Can be used to call models normally; functionality is identical to pre-upgrade keys.</p></td></tr><tr><td><p><strong>Recommended action</strong></p></td><td><p>We recommend that you create a new key to replace the old one for improved security.</p></td><td><p>Copy and save the key immediately after creation, and store it securely.</p></td></tr></tbody></table>

## Manage API keys through the API <span id="apikey-openapi-h2" /> <span id="apikey-openapi-sec" />

In addition to console operations, Alibaba Cloud Model Studio provides OpenAPI operations that let you create, query, edit, delete, enable, disable, and reset API keys programmatically, so that you can integrate API key management into automated workflows. Calling the following operations requires signature authentication with your Alibaba Cloud account AccessKey (not the API key itself) and the corresponding RAM permissions. You can debug each operation online in the OpenAPI developer portal, or call it through an Alibaba Cloud SDK.

<table style={{ display: "table", tableLayout: "fixed", width: "100%" }}><colgroup><col style={{ width: "33.33%" }} /><col style={{ width: "66.67%" }} /></colgroup><thead><tr><th><p><strong>Operation</strong></p></th><th><p><strong>Description</strong></p></th></tr></thead><tbody><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/CreateApiKey">CreateApiKey</a></p></td><td><p>Creates an API key.</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/GetApiKey">GetApiKey</a></p></td><td><p>Queries the information of a specified API key.</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/ListApiKeys">ListApiKeys</a></p></td><td><p>Queries the list of API keys.</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/UpdateApiKey">UpdateApiKey</a></p></td><td><p>Edits an API key, such as its description and permission configuration.</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/DeleteApiKey">DeleteApiKey</a></p></td><td><p>Deletes an API key. This operation cannot be undone.</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/EnableApiKey">EnableApiKey</a></p></td><td><p>Enables an API key (not supported in the US (Virginia) region).</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/DisableApiKey">DisableApiKey</a></p></td><td><p>Disables an API key. The key is retained and can be re-enabled at any time (not supported in the US (Virginia) region).</p></td></tr><tr><td><p><a href="https://api.alibabacloud.com/api/ModelStudio/2026-02-10/ResetApiKey">ResetApiKey</a></p></td><td><p>Resets an API key. A new key value is generated and the old key immediately becomes invalid (not supported in the US (Virginia) region).</p></td></tr></tbody></table>

## API key permissions <span id="095678aa28rn4" /> <span id="69fb488ea27xi" />

An API key's permissions are determined entirely by its <strong>workspace</strong>. <strong>All API keys within the same workspace have identical permissions.</strong> You do not need to create different API keys for different models, such as text-to-text, text-to-image, or speech synthesis models.

- <strong>API key in the default workspace:</strong> Can call all standard models and any [application](/en/model-studio/application-introduction) within the default workspace.
- <strong>API key in a sub-workspace:</strong> Can call standard models [authorized](/en/model-studio/use-workspace#f2e68d7ba7ubk) for the sub-workspace and any application within that sub-workspace.

<strong>Calling a</strong>[<strong>fine-tuned model</strong>](/en/model-studio/model-training-overview)<strong>:</strong> After a model is fine-tuned and deployed in Alibaba Cloud Model Studio, only an API key from the model's workspace can call it. No separate [authorization](/en/model-studio/use-workspace#f2e68d7ba7ubk) is required.

When you <strong>Create API Key</strong> or click <strong>Edit</strong> for an existing API key, you can switch the <strong>Permissions</strong> to <strong>Custom</strong> and configure the following:

- <strong>IP address whitelist</strong>: Allows only IP addresses on the whitelist to use the API key to make calls (supports IPv4 addresses and CIDR blocks; IPv6 is supported only in the China (Beijing) region, and the US (Virginia) region supports IPv4 only).
- <strong>Access Scope</strong>: Select the specific models or applications that this API key can access. The key cannot call unselected resources. You can select up to 30 models.

## API key validity <span id="7d2ee55621wns" /> <span id="fd72c5c1besqv" />

API keys do not expire. They remain valid until you manually delete them.

To grant temporary access to third-party applications or users, or to strictly control high-risk operations such as accessing or deleting sensitive data, you can [generate a temporary API key](/en/model-studio/generate-temporary-api-key) (valid for up to 1800 seconds). This avoids exposing a long-term API key and reduces the risk of leaks.

## Error codes <span id="apikey-errcode-h2" /> <span id="apikey-errcode-sec" />

If a model call fails and returns an error message, see [Error codes](/en/model-studio/error-code) for troubleshooting.

## FAQ <span id="4a33090ffaa7g" /> <span id="bba416986e453" />

<strong>Q: How many API keys can I create under a single Alibaba Cloud account?</strong>

A: Each Alibaba Cloud account can create up to 10 workspaces (including the default workspace), and each workspace can have up to 20 API keys.

<strong>Q: Are API keys created by a RAM user still valid after the user is deleted?</strong>

A: No. After you [disable or delete a RAM user](https://www.alibabacloud.com/help/en/doc-detail/116116.htm) in the RAM console, all API keys created by that user become invalid and can no longer be used for model calls.

<strong>Q: I used the</strong>`echo`<strong>command and confirmed the environment variable was set correctly. Why does my code still report that the API key cannot be found?</strong>

A: This can occur for the following reasons:

- Scenario 1: <strong>A temporary environment variable was set</strong>. A temporary variable is valid only within the current terminal session and does not affect running IDEs or other applications. Refer to the instructions in this topic to set a permanent environment variable.
- Scenario 2: <strong>The IDE, command-line tool, or application was not restarted</strong>.

  - You must restart your IDE (such as VS Code) or terminal to load the new environment variables.
  - If you set the environment variable after deploying an application, you must restart the application service to reload the environment variables.
- Scenario 3: <strong>The variable is missing from a service configuration file</strong>. If your application is started by a service manager, such as systemd or supervisord, you may need to add the environment variable to the service manager's configuration file.
- Scenario 4: <strong>Using the</strong>`sudo`<strong>command</strong>. If you use `sudo python xx.py` to run the script, the environment variables of the current user may not be inherited. This is because `sudo` does not inherit all environment variables by default. You can use the `sudo -E python xx.py` command, where the `-E` parameter ensures that the environment variables are passed. If you have permission to run the script, you can run `python xx.py` directly.