the provider catalog
Moonshot (Kimi)
Kimi models built for very long context. Cataloged ahead of the runtime: this binary names the vendor, a coming release runs it. The audit below says so honestly. One provider/model line moves a workflow here or away again: the same file runs on every provider the catalog names, and swapping is a one-word diff. Machines read the catalog; the binary answers nika catalog.
- 2pinned modelsaliases pin exact upstream ids
- cloudfamilybring your own key; it rides an env var and stays yours
- MOONSHOT_API_KEYthe key rides herean env var, never a config file
- openai-chatwire dialectthe adapter speaks it
the wire
cloud · bring your own key; it rides an env var and stays yoursA workflow names this provider in the model line (model: moonshot/kimi-k2), and the engine speaks openai-chat on the wire. The key rides MOONSHOT_API_KEY in the environment, never a config file, never the workflow. The provider id also answers to kimi.
- default
kimi-k2- dialect
openai-chat- tags
- frontier · function-calling · long-context · streaming · structured-output
the models
2 pinsAliases are what the file may write; the engine pins each one to an exact upstream id, so a run stays reproducible after a vendor rotates names.
k2kimi-k2ctx 128k · json:schemak2-5kimi-k2.5ctx 256k · json:schema
in the released catalog
2 roomsThe wire models this provider serves in the released binary's catalog · each one is a room with its seats, exact prices and measured energy.
the whole register: /catalog/models · what the released binary knows, vendored at the engine pin.
in a real file
a complete workflow · shown wholenika: v1workflow: id: long-context-brief description: "built for long context — the whole document goes in, one brief comes out"tasks: brief: infer: model: moonshot/kimi-k2 max_tokens: 150 prompt: | Brief a reviewer in three lines: the file declares its blast radius; permits allowlist what runs, reads, writes and calls; absent permits mean the engine floor.outputs: brief: ${{ tasks.brief.output }}conform to the served contract · the vendor is cataloged ahead of the runtime: this binary names it, a coming release runs it · the drift gate re-proves this copy on every test run · open it in the playground →
get set up
keys at platform.kimi.ai- 1Create a key in the Kimi platform console.
- 2The key rides the environment, never the file
export MOONSHOT_API_KEY=…
Pick it for whole-document work, once the runtime lands. Moonshot AI · Beijing, China. Then prove the seat: nika doctor names every provider this binary can reach.
swap it
10 more cloud seatsMoving off Moonshot (Kimi) is editing one line. The rest of the file (tasks, permits, outputs, the trace) does not change. The register orders the catalog local first; beyond it the engine embeds 21 more OpenAI-compatible endpoints.
cross-references
the words that meet it
Try it in the playground, or install and go local first. Read the spec →