Key error diagnosis

Sao10k | insufficient balance

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

Provider

Sao10k

global provider route

Error type

insufficient balance

high

Status code

402

insufficient-balance

Sample models

Llama 3.1 70B Hanami x1 · Llama 3.1 Euryale 70B v2.2 · Llama 3.3 Euryale 70B

Error route summary

Error type

insufficient-balance

high

Provider

Sao10k

Status code

402

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

What this error usually means

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

Provider: Sao10k
Error type: insufficient balance
Status code: 402

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 Sao10k, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Llama 3.1 70B Hanami x1 · Llama 3.1 Euryale 70B v2.2 · Llama 3.3 Euryale 70B are visible and return stable evidence.
Finally record 402, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

insufficient balance 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
Llama 3.1 70B Hanami x1 · Llama 3.1 Euryale 70B v2.2 · Llama 3.3 Euryale 70B

Open key checker

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

Open providers

Sao10k

Open models

Llama 3.1 70B Hanami x1 · Llama 3.1 Euryale 70B v2.2 · Llama 3.3 Euryale 70B