Repository navigation
[Feat] Add Kimi K3.1 Pro and Highspeed models - #3596
Conversation
|
No new code issues found. The prior Requesty issue is addressed by removing both new routes and their metadata fallback. See session
Reviewed 5e5b6e5 |
|
Completed in 5e5b6e58: removed both new Requesty Kimi K3.1 routes, the metadata compatibility fallback, related tests, and docs/changeset references. Existing Requesty configuration and metadata implementation match the PR base. The other five providers’ Kimi additions remain; the PR description now reflects eight supported routes. The associated Requesty review thread is resolved by removing the unsupported additions. Validation: 176 targeted types tests and 31 metadata tests passed; docs build/link validation and pre-push oxlint, residual ESLint, typechecks, and knip passed. No new Requesty additions remain in the net diff. Optional pre-commit Judgement evaluation is still incomplete due to evidence collection/evaluation failure; authenticated inference was not exercised. |
What changed
Why this change was made
The upstream release is named Kimi K3.1 Pro, with a separate Highspeed variant. Exact IDs were verified against Moonshot's API documentation, Kimi for Coding's model documentation, and the live OpenRouter, Vercel, and OpenCode Go catalogs.
Impact
Users can select the new models through five providers (eight task-model routes). Kimi for Coding uses
k3.1-pro/k3.1-pro-highspeedon its membership endpoint and resolves metadata throughkimi-code-plan-cn.Validation on the updated branch:
Authenticated inference was not exercised. Kimi membership tier controls model and full-context access. The optional pre-commit Judgement evaluation reported incomplete evidence collection/evaluation; that check remains to be completed before merge.