# Get an API key: Alibaba Cloud

> An Alibaba Cloud key authenticates only against the endpoint of the region that issued it, and Big-AGI dials the international one by default.

- Canonical: https://big-agi.com/docs/connect-alibaba
- Minimum tier: open  [Open ⊂ Free ⊂ Pro - a tier only ever ADDS to the Open baseline]
- Kind: provider · Last content update generation: 2026-07-27 · Review by: 2026-10-27
- Answers: Where do I create an Alibaba Cloud API key? · Which region should I choose? · Does Direct Connection work with Alibaba Cloud?

An Alibaba Cloud key authenticates against one region's endpoint and no other. Big-AGI dials the international endpoint unless told otherwise. A key from another region is refused, which reads exactly like a bad key.

## Picking the console for your region

1. [bailian.console.alibabacloud.com](https://bailian.console.alibabacloud.com/) covers China (Beijing), Singapore, Tokyo, Hong Kong and Frankfurt. US (Virginia) has its own console at [modelstudio.console.alibabacloud.com/us-east-1](https://modelstudio.console.alibabacloud.com/us-east-1).
2. Inside it, **API Key** -> **Create API Key** ([Alibaba's own steps](https://www.alibabacloud.com/help/en/model-studio/get-api-key)).
3. Copy or download from the dialog straight away - the complete key is shown once.

## The cloud account behind it

Sign-up produces a cloud account with a model-studio workspace, billed on the cloud invoice. Fund it before the first answer. Set the spending limit in that account's billing settings. [Alibaba's own model list](https://www.alibabacloud.com/help/en/model-studio/getting-started/models) describes what the workspace exposes.

## Adding the key and matching the endpoint

Open **Models** (`Ctrl + Shift + M`) and press **More Services** if the **Setup AI Models** wizard appears. Then **Add** -> **Alibaba Cloud**, paste into **Alibaba Cloud API Key**, and press **Models** - the list filling in below is your confirmation ([add and manage your keys](/docs/connect-models)).

Now set **API Endpoint** under **Advanced** to the region whose console issued the key. That field is the fix for the mismatch.

## Direct Connection

Direct Connection can be turned on once the key is in the browser. It starts off.

> **Direct Connection works only with your API key stored in the browser**, and with an AI service that permits direct browser calls (CORS). Where it cannot be used, requests route through the Big-AGI fast edge servers instead - everything still works, within the standard upload size and time limits.

## When this doesn't work

| What you see | What it means | What to do |
|---|---|---|
| `Upstream responded with HTTP 401 Unauthorized` | A valid key against the wrong regional endpoint reads exactly like an invalid one. | Set **API Endpoint** to your region, then [key and access errors](/docs/issue-key-and-access) |

## Related

- [Connect an AI service](/docs/connect-models)
- [Connect any OpenAI-compatible endpoint](/docs/connect-custom-endpoints)
- [What your provider does with your text](/docs/privacy-data-flow)