Error Resolver

rout.my returns normalized JSON errors to clients. Internally, the admin panel can maintain approved Error Templates: regex patterns that map noisy upstream provider messages to safe user-facing responses.

Use this resolver when a user sends you an HTTP status and error body. It does not call the admin API; it mirrors common public error categories so you can decide whether to fix the request, retry, or add an Error Template in admin.

HTTP status Error body or raw message {"error":{"message":"Daily quota exceeded","type":"rate_limit_error","code":"quota_exceeded"}}

Likely category

Rate or quota limit

Cause

The request exceeded daily tokens, per-minute request limits, or a provider-side throttle.

Action

Wait for reset, reduce concurrency, or move the key to a plan with a larger pool.

Retry

Retry with backoff. For daily quota, retry after the reset window.

When to Add an Error Template

Add or approve a template when the same upstream message repeats and exposes provider-specific implementation details, raw stack traces, credentials, or confusing internal wording.

Do not add a template for normal client mistakes such as missing model, invalid JSON, or an API key typo. Those should stay explicit and actionable.