What this error usually means
Diagnose Relace rate limited (429) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: Relace
- Error type: rate limited
- Status code: 429
Key error diagnosis
Relace | rate limited
Diagnose Relace rate limited (429) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
Provider
Relace
global provider route
Error type
rate limited
high
Status code
429
rate-limited
Sample models
2
Relace Apply 3 · Relace Search
Error route summary
Error type
rate-limited
high
Provider
Relace
Status code
429
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 Relace, not just a compatible protocol.
- Then list models or run a lightweight probe: check whether models like Relace Apply 3 · Relace Search are visible and return stable evidence.
- Finally record 429, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.
Next action
rate limited 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
- Relace Apply 3 · Relace Search