>>106389364
Oh, I see it now. Looks like the rate limit value is broken on the /api/v1/key endpoint and always returns -1.