RUTY / DEVELOPERS
Failures should be actionable.
Read the HTTP status and response body together. Ruty forwards upstream errors and Retry-After without converting failures into successful responses.
| Status | Next step |
|---|---|
400 | Check the model and request parameters. |
401 | Check the Bearer token and whether the key is still active. |
403 | Check account permissions and task ownership. |
404 | Check the route, task ID and originating API key. |
413 | Use media URLs; JSON request bodies are limited to 1 MiB. |
429 | Honor Retry-After, then back off. |
502 | Upstream is unavailable or timed out. Inspect task history before retrying creation. |
Retries
Read-only requests can use bounded retries with backoff. Do not blindly retry chargeable create requests. Image idempotency keys protect supported operations when reused with the same payload; video submissions can produce duplicate jobs.
Insufficient credits and model availability errors come from the backend. The console shows your account balance and generation history.