[janeza2]

Summary

• Adds kimi-coding-apikey to PROVIDER_LIMITS_APIKEY_PROVIDERS so its usage/quota can be fetched on the dashboard Quota page (parity with the OAuth-only kimi-coding provider).
• Extends getKimiUsage to accept an optional apiKey and switch the auth header accordingly: x-api-key for API-key connections, Authorization: Bearer + device headers for the existing OAuth path.

Why

The kimi-coding-apikey provider (added in #463) currently shows no quota in the dashboard, while its OAuth counterpart kimi-coding does. Kimi's /coding/v1/usages endpoint already accepts the same API key used for /v1/messages — a live request returns authentication.method: METHOD_API_KEY and the standard { usage, limits, user } payload — so the only thing missing was wiring the provider into the API-key quota allowlist and passing the key through to the existing parser.

Verified against api.kimi.com with a real API key:

{
  "user": { "userId": "...", "membership": { "level": "LEVEL_STANDARD" } },
  "usage": { "limit": "100", "used": "6", "remaining": "94", "resetTime": "..." },
  "limits": [{ "window": { "duration": 300, "timeUnit": "TIME_UNIT_MINUTE" }, "detail": { ... } }],
  "authentication": { "method": "METHOD_API_KEY", "scope": "FEATURE_CODING" }
}

The existing parser in getKimiUsage already handles this shape (it reads usage.limit/used/remaining/resetTime and the limits[] array), so no parsing changes were needed.

Changes

File	Change
open-sse/services/usage.ts	getKimiUsage(accessToken, apiKey?) — pick x-api-key when apiKey is present, else fall back to the OAuth Bearer + X-Msh-* device headers. Add case "kimi-coding-apikey" in getUsageForProvider.
src/lib/usage/providerLimits.ts	Add "kimi-coding-apikey" to PROVIDER_LIMITS_APIKEY_PROVIDERS.

Test plan

• Connect a kimi-coding-apikey provider with a real Kimi API key and open the dashboard Quota page — expect Weekly (limit/used/remaining) and Ratelimit cards.
• Confirm kimi-coding (OAuth) still shows quota as before (no regression — same code path, useApiKey=false).
• Confirm a bad/revoked API key falls through to the existing Kimi Coding connected. API Error … message branch instead of crashing.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!