The whole history, kept in mind.
Kimi models hold long inputs and keep track across many steps. A coworker can read years of a customer's orders, claims and emails before it answers. The code variants help draft automation scripts for your team to review.
Kimi and Dika Ops, kept in step.
Moonshot AI's long-context Kimi models for long histories and multi-step work.
What teams use it for.
A one-page summary of a key account, built from every order and email.
Chase overdue confirmations across many suppliers, one draft at a time.
Describe a routine and get a script for your team to check and switch on.
Connected in four steps.
- 01
Choose Kimi models included with your plan, or add your own Moonshot AI API key.
- 02
Assign Kimi to account and automation coworkers, and the code variant to script drafting.
- 03
Set spending and step limits per task.
- 04
Run it on a few real accounts and tasks, review the log, then go live.
Kimi, answered.
Is Dika Ops an official Kimi partner?
No. The Kimi integration is in early access. It uses Moonshot AI's API through a key managed by Dika Ops or your own key.
Which Kimi models are available?
The Kimi K2 and K3 families, including code variants. The list follows what Moonshot AI releases.
What data is sent?
Only what the coworker's scope allows for the task. A long history is sent only if the coworker may see all of it.
Do scripts it writes run straight away?
No. Draft scripts wait for a person to review and switch them on.
Kimi is a trademark of its owner. Dika Ops is not affiliated with or endorsed by its owner.
Run the whole company from one place.
Dika Ops is in closed beta. We onboard a few companies at a time and set everything up with you.