Key error diagnosis

Meta | quota exceeded

Meta returning 429 / quota exceeded should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

What this error usually means

Meta returning 429 / quota exceeded should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Meta
Error type: quota exceeded
Status code: 429

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 Meta, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Llama 3.1 70B Instruct · Llama 3.1 8B Instruct · Llama 3.2 11B Vision Instruct 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

quota exceeded 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 Instruct · Llama 3.1 8B Instruct · Llama 3.2 11B Vision Instruct

Open key checker

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

Open providers