What this error usually means
Diagnose NVIDIA insufficient balance (402) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: NVIDIA
- Error type: insufficient balance
- Status code: 402
Key error diagnosis
NVIDIA | insufficient balance
Diagnose NVIDIA insufficient balance (402) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
Provider
NVIDIA
global provider route
Error type
insufficient balance
high
Status code
402
insufficient-balance
Sample models
11
Llama 3.1 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5
Error route summary
Error type
insufficient-balance
high
Provider
NVIDIA
Status code
402
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.
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 NVIDIA, not just a compatible protocol.
- Then list models or run a lightweight probe: check whether models like Llama 3.1 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5 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 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5