Moonshot AI (beta)
How to connect your own Moonshot AI key as a beta provider, and the opt-in each project needs before it runs on a Kimi model.
With a license for your own key, you can connect your own Moonshot AI key and run stages on Moonshot AI's Kimi models. Moonshot AI bills that key directly.
This is a beta
Moonshot AI is a beta provider in Reqursor Development. Its results and its cost are not yet verified, so treat it as an experiment and keep an eye on the first runs. If you also connected an Anthropic key, it keeps working next to it.
What you need
- A license for your own key. Every such license includes the beta.
- Your own Moonshot AI API key, from the Moonshot AI platform (
platform.kimi.ai). - An opt-in per project. A project uses Moonshot AI only after someone reads its data disclosure and accepts it for that project.
Connect it
Store your key
You can connect it as your provider or next to an Anthropic key:
- As your provider. In the setup wizard's Connect Claude step, or later in Settings → Claude & models, choose Moonshot AI (Kimi, beta) as the provider and paste your API key.
- Next to an Anthropic key. In Settings → Claude & models, under Additional model providers, find Moonshot AI (Kimi, beta). It carries a Beta label. Paste your API key there.
The key is stored encrypted, like every other secret, and is sent to Moonshot AI only: never to another model provider, and never to the agent.
Opt the project in
In the project's settings, under Beta model providers, read the disclosure and accept it with Enable Moonshot AI (Kimi, beta) For This Project. The disclosure says what is sent to Moonshot AI and what Moonshot AI's terms say about it. Read it with whoever is responsible for your data before you accept.
Choose a Kimi model
A stage runs on the provider that serves its model. Set a stage to a Kimi model in Settings → Claude & models, and that stage's requests go to Moonshot AI, only for the projects that opted in.
With only a Moonshot AI key connected, every stage must run on a Kimi model: choose the Fixed model strategy with Kimi K3. Automatic, Prefer economy and Prefer quality pick Claude models and are refused until an Anthropic key is connected too.
What the opt-in means
- It is per project. A project that has not opted in sends nothing to Moonshot AI, even when another project on the same install does.
- It can be withdrawn in the same place, and the project then stops using Moonshot AI.
- It follows the disclosure. If the disclosure text changes, the project is asked again before it keeps using the provider.
Data and billing
For a project that opted in, a model request to Moonshot AI holds what any model request holds: the ticket text and the code the agent reads or writes. It goes straight from your server to Moonshot AI and never through Reqursor. What Moonshot AI does with it is governed by Moonshot AI's own terms, which are an agreement between you and them; the disclosure in the project's settings is the place to start.
Moonshot AI bills your key. The dollar budgets of the project apply to these runs like any other run on your own key.
On Reqursor Credits you do not connect a Moonshot AI key, and Kimi is not offered through credits. This beta is for a self-hosted install with your own key only.