How it works
The decoder reads what you paste and matches the HTTP status, the v2 problem type, any v1.1 error code and Weir's own API errors against a built-in list, then says what the error means, the usual fix, and whether retrying will help.
It runs in your browser: nothing is sent, you don't need to sign in, and it uses no credits. It can't see your account, so for usage caps and billing errors check your developer console too.
Retry or fix
As a rule, a 429 or a 503 is worth retrying after a wait, while a 401, 402 or 403 comes back the same until you change something. Our guides to X API error codes, 402 Payment Required, rate limit errors, Tweepy 403 Forbidden and X API rate limits go deeper, and X API status helps when the problem is on X's side.