On the wire
Ships with HTTP status 429, carrying "code": "RU-2001" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.
Common causes
- A client retrying in a tight loop with a bad or missing key.
- A misconfigured deployment where many instances share one broken credential.
How to fix it
- Stop the retry loop first: retrying does not clear the limit.
- Fix the credential (see RU-1001 and RU-1002), wait a minute, then resume.
Related codes
Still stuck?
Ask support and mention RU-2001: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.