Run Kimi inside your workflows on your own key

Kimi (Moonshot AI) in MadMax is a bring-your-own-key model provider. Paste a Moonshot API key, bind it to an AI agent step, and that step runs on a Kimi model billed to your Moonshot account; MadMax routes the call through Moonshot's OpenAI-compatible endpoint at api.moonshot.ai, so there is nothing to configure beyond the key. The agent keeps its full task list (custom prompt with a JSON output schema, extract, classify, summarize) and its tools: calculator, browser, sandboxed code, your sub-workflows and any connected app's operations, plus memory and knowledge-base retrieval. You still describe the workflow in plain English and MadMax builds and verifies it, failing a step whose answer comes back empty or off-schema even when the API call succeeded. Kimi only changes which model answers inside the steps you bind; unbound steps run the platform default, so you can build first and switch models where Kimi fits.

What teams build

• A hosted form collects an RFP's numbered requirements, a Kimi custom-prompt agent bound to a knowledge base of your product docs drafts an answer to each one and says plainly which it cannot support, and the draft lands in a Google Doc with an email to the account owner.
• A webhook delivers each support ticket, a Kimi classify step sorts it into billing, bug, how-to or other, a second agent writes a two-line summary in the team's working language, and a switch routes the ticket to the right queue.
• A GitHub release event arrives through the GitHub connection, a Kimi agent writes a customer-facing changelog entry from the notes, and an approval emails the product manager a one-click approve or reject before the entry posts to a Slack or Discord channel.

How it connects

Paste an API key from platform.moonshot.ai under API Keys (it starts with sk-). Use the international platform, not platform.moonshot.cn: the two run separate endpoints and a key from one is rejected by the other. Add it in Settings → connectors → Kimi (Moonshot AI) or from an agent step's Provider picker. The key routes the agent steps you bind it to through Moonshot on your own account, and MadMax does not meter those calls. The canvas chat that builds and edits workflows stays on the platform model, and the live web-search tool is platform-model only, so a Kimi-bound step ignores that toggle while its other tools keep working. Rotating the key is a reconnect in place. See managing connections.

Related

• AI settings and models
• AI agent step
• Custom prompt task
• Managing connections
• OpenAI on your own key