Repository navigation
Conversation
PROVIDER_USAGE_IDS gains kimi-coding with an adapter for GET https://api.kimi.com/coding/v1/usages, on the same origin as the provider's base URL. The overall quota and each rate-limit window become count buckets with their reset time; the parallel-request limit and membership level become metrics. Both an API key and a Kimi Code OAuth credential reach the endpoint as a Bearer token through the existing query path. The mapping follows the response sample in the issue; it was not checked against the live endpoint. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
kimi-codingto the provider usage list with an adapter forGET https://api.kimi.com/coding/v1/usages(same origin as the provider's base URL), following the existing pattern; no route change.usage→ a count bucket "Overall"; eachlimits[]entry → a count bucket labelled from its window (e.g. 300 min → "5h") with its reset timeparallel.limitanduser.membership.level→ metricsKIMI_API_KEY) and a Kimi Code OAuth sign-in both reach the endpoint asAuthorization: Bearer …(checked withfetchfaked and a scratch auth.json); no credential →auth-unavailableNot verified against the live endpoint: the mapping follows the response sample in #848 only. As with MiniMax, the UI shows count buckets as remaining / limit without their reset time.
Files:
lib/provider-usage.ts,lib/provider-usage-ids.ts(+ identicaldemo/copy); test inlib/provider-usage.test.mjs.tsc, eslint,npm testpass.Closes #848
🤖 Generated with Claude Code