kimi-for-coding: inherit indicative costs from base models instead of zeroing - #4071
Open
lorecanc wants to merge 1 commit into
Open
kimi-for-coding: inherit indicative costs from base models instead of zeroing#4071lorecanc wants to merge 1 commit into
lorecanc wants to merge 1 commit into
Conversation
Contributor
Action items
|
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
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.
Summary
The
kimi-for-codingprovider models currently ship with zeroed[cost]tables, with the comment "Cost is zeroed per this provider's subscription convention". This makes usage tracking in opencode (and any models.dev consumer) report $0.00 for all Kimi For Coding traffic, even though the models are billed on the underlying model's token economics.This PR removes the zeroed
[cost]tables so each model inherits the cost of itsbase_model, keeping the pricing in sync automatically when the underlying model or its price changes.What changed
providers/kimi-for-coding/models/kimi-for-coding.toml— no longer zeroes cost; inherits frommoonshotai/kimi-k2.7-code(input $0.95 / output $4.00 / cache read $0.19)providers/kimi-for-coding/models/kimi-for-coding-highspeed.toml— inherits frommoonshotai/kimi-k2.7-code-highspeed(input $1.90 / output $8.00 / cache read $0.38)providers/kimi-for-coding/models/k3.toml— inherits frommoonshotai/kimi-k3(input $3.00 / output $15.00 / cache read $0.30)providers/kimi-for-coding/models/k3-256k.toml— inherits frommoonshotai/kimi-k3Each file now carries a comment clarifying that Kimi For Coding is a fixed-fee subscription plan and the inherited cost is the indicative pay-per-token equivalent, for usage tracking only, not the actual billing rate.
Rationale
The
kimi-for-codingmodel IDs are rolling aliases that point at the current flagship coding model (e.g.kimi-for-coding→moonshotai/kimi-k2.7-codetoday). Because the models usebase_model, dropping the zeroed[cost]tables yields:This follows the existing convention for other subscription-billed endpoints already listed in this repo — e.g.
providers/opencode-go/models/kimi-k2.7-code.tomlships full per-token costs (input $0.95 / output $4.00 / cache read $0.19) without zeroing.Notes
indicativeflag in the schema — happy to discuss.