A positive account balance and an HTTP 402 budget error can both be true. OpenRouter can enforce several controls separately: an API-key limit, an organization or member guardrail, and a temporary in-flight budget reservation while concurrent requests are still running. The messages `Spend cap exceeded (daily limit)` and `in_flight_budget_exhausted` point to those controls, not necessarily to an empty credit balance.
Do not buy more credits as the first response. Check the limit on the exact API key making the request, then check organization/member guardrails and their reset period. Stop or reduce concurrent requests and wait a few minutes for in-flight reservations to clear. A fresh API key with no custom limit is a useful diagnostic: if it works, the old key's policy is the problem; if it fails too, the restriction is probably at the account or organization level.
If the same 402 persists across a UTC reset, with no key or member limit configured, send OpenRouter support the request ID, exact error code, UTC timestamps, key name (never the secret), organization name, and a screenshot of the positive balance and limit settings. ROZO cannot change OpenRouter account controls, and a crypto top-up will not fix this class of 402 when credits are already present.