Integration guide
apifare for Kimi CLI
Give Kimi CLI one prepaid key for every API it needs. There is no separate provider account or provider API key for eligible capabilities, and it all runs under hard caps and a kill switch.
1 · Get a key
Create an account at /start: email in, token out (shown once). Save the token somewhere safe.
2 · Add apifare to Kimi CLI
Add this to ~/.kimi/mcp.json. Kimi CLI uses the same format as other MCP clients.
{
"mcpServers": {
"apifare": {
"command": "npx",
"args": ["-y", "apifare-mcp"],
"env": { "APIPAY_TOKEN": "<your-token>" }
}
}
}Replace <your-token> with your token. Run kimi mcp list, or type /mcp inside Kimi CLI, to see apifare connected.
3 · Try it
Ask Kimi CLI to search the web for X, then to fetch a URL, then what's the weather in London. Every call is debited from your balance and lands on your signed, exportable audit chain.
4 · Stay in control
Set daily or monthly caps per agent, and keep the kill switch ready. Both are checked before a call is dispatched. When the balance runs out, your agent gets an HTTP 402 with a top-up link it can hand you; the error catalog lists every stop and what unblocks it.
What Kimi CLI can call
Everything on the key: search, filings, registries, weather, and ready-to-run tools, plus any provider key you vault yourself. Exact per-call prices are on /capabilities.
Config checked against Kimi CLI's MCP docs on 2026-09-12. Markdown version: /integrations/kimi-cli.md.
More integrations
Claude Code · Claude Desktop · Cursor · Windsurf · Zed · Cline · GitHub Copilot (VS Code) · OpenAI Codex CLI · Gemini CLI · Hermes Agent · Qwen Code · LibreChat
Model guides
Calling a model's API directly instead? Give it apifare tools with a plain tool loop: DeepSeek · Kimi · Qwen · OpenAI GPT · Gemini.