#Kimi 2.5 apikey reache limit
dusk frigateBOT
keen osprey
Mabye wrong api key?
viral basin
Mabye wrong api key?
nope
keen osprey
nope
Maybe try openclaw onboard and put in ur api key again
🤷♂️ I’ve never used Kimi but that might work
@vital lily
vital lilyBOT
Yep, re-running onboarding is a good move — but this specific error is usually rate-limit/quota window, not “no money”.
Try this exact flow:
openclaw --version
openclaw models status
openclaw models status --probe
openclaw logs --follow
Then paste the exact error line here (redact key).
That tells us if it’s auth mismatch vs real provider 429.
Also important for Kimi in OpenClaw:
moonshot/...uses Moonshot keykimi-coding/...uses Kimi Coding key
Those are separate providers/keys and not interchangeable.
If needed, re-onboard with the matching auth choice and restart:
openclaw onboard --auth-choice moonshot-api-key
# or
openclaw onboard --auth-choice kimi-code-api-key
openclaw gateway restart
Docs:
No worries — let’s make this concrete, because “limit reached” can mean different things.
Can you paste these 3 outputs?
openclaw --version
openclaw models status --probe
openclaw logs --follow
(For logs, just paste the exact error line; redact key.)
Most common causes:
- Rate limit window hit (RPM/TPM), even with positive balance
- Wrong provider/key pairing
moonshot/...→MOONSHOT_API_KEYkimi-coding/...→KIMI_API_KEY
- Funds are on one platform, but requests are going through another provider account
Docs:
I got you 🦐
If you want, do this quick reset path first:
openclaw onboard --auth-choice moonshot-api-key
openclaw gateway restart
openclaw models status --probe
If it still says “limit reached”, paste the exact error text from:
openclaw logs --follow
That exact line is the key — it tells us if it’s: