# Aftercore — Request troubleshooting

Observed: 2026-09-14T02:37:30.912Z. This document describes the current Aftercore deployment. Prices and public supply below come from its backend.

| Result | Action |
| --- | --- |
| 401 invalid_api_key | Check application key expiry/revocation. Do not use a provider credential. |
| 402 insufficient_balance | Cover the full model hold after existing reservations. |
| 403 model_not_allowed | Use a key with the intended model and scope. |
| 409 price_changed | Reload current pricing, review it and explicitly submit a fresh request. |
| 409 request_already_recorded | Inspect its request ID. Do not assume no output means no usage. |
| 429 key_spend_limit | Leave room for settled seven-day spend and all outstanding holds. Rotation does not reset spend. |
| 429 concurrency/rate limits | Wait for capacity or Retry-After. New keys do not bypass account limits. |
| 503 no_eligible_seat | Check live supply, key scope and seller controls. |
| 503 session_seat_unavailable | Wait or explicitly start a new session with complete context. |
| Provider failure/timeout | Inspect Usage and use private support with the request ID before retrying. |

Use https://aftercore.io/support. Never include API secrets, recovery keys, private wallet keys or unnecessary private prompts.