Key error diagnosis

Upstage | unauthorized

Upstage returning 401 / unauthorized should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

Upstage

global provider route

Error type

unauthorized

high

Status code

401

unauthorized

Sample models

Solar Pro 3

Error route summary

Error type

unauthorized

high

Provider

Upstage

Status code

401

Read-only check. Detection data burns after 5 minutes.

What this error usually means

Upstage returning 401 / unauthorized should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Upstage
Error type: unauthorized
Status code: 401

How to prove it during checking

Read-only check. Detection data burns after 5 minutes.

Run read-only identity first: confirm whether the key really belongs to Upstage, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Solar Pro 3 are visible and return stable evidence.
Finally record 401, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

unauthorized should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.

Read-only check. Detection data burns after 5 minutes.
global provider route
Solar Pro 3

Open key checker

Read-only check. Detection data burns after 5 minutes.