I use a tested Kimi API Key starting with sk- and 51 characters long. It works via web API tests. When i try using it from Cursor using overridden “https://api.moonshot.ai/v1” URL and my Kimi API Key, it gives “Unauthorized User API Key” but it doesn’t even try to reach moonshot URL.
I tried adding “kimi-k2.6” since it was not already in the list like “Kimi K2.7 Code” or “Kimi K3” but it fails with all of them.
Steps to Reproduce
Generate a Kimi API Key
Use this key to “Cursor Settings > Models > API Keys > OpenAI API Key” section by pressing enter.
i just tried “kimi-k2.7-code-highspeed” and it worked. so, please let me know which Kimi models are usable with Cursor and how can we use already listed models like “Kimi K3” or “Kimi K2.7 Code”?
Hey, thanks for the detailed report and for figuring out to try a different name. That’s the key part.
What’s happening: the custom model name kimi-k2.6 (same for kimi-k2.7-code, kimi-k3, kimi-latest, kimi-k2.5) matches a reserved identifier for a built-in model in Cursor. Because of that, Cursor treats it as a managed model and doesn’t send the request to your Override OpenAI Base URL. So Moonshot never gets called, and your key gets rejected. We’re tracking this issue, but I can’t share an ETA yet.
Workaround (you’re already on the right track with kimi-k2.7-code-highspeed): name your custom model using a real Moonshot model ID that does NOT collide with reserved names. These work:
About the built-in picker options Kimi K3 and Kimi K2.7 Code: right now those are Cursor-managed models, so they don’t route through your personal Moonshot key and Override URL. You can’t select them with a personal key yet. For BYOK via Moonshot, use a custom model with a non-colliding name like above.
