An Alibaba Cloud key authenticates only against the endpoint of the region that issued it, and Big-AGI dials the international one by default.
Alibaba Supported Models ->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.
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 describes what the workspace exposes.
Ctrl + Shift + M opens Models; press More Services when the Setup AI Models wizard is in the way. Then Add -> Alibaba Cloud, paste into Alibaba Cloud API Key, and press Models (add and manage your keys).
Now set API Endpoint under Advanced to the region whose console issued the key. That field is the fix for the mismatch.
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.
| 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 |
BIG-AGI
Resources
© 2026 Token Fabrics·Built with passion in San Diego