Kimi Code

Route Moonshot AI’s Kimi Code through Edgee to cut token costs and gain full observability, with one command.

Kimi Code is Moonshot AI’s terminal coding agent. Route it through Edgee to reduce token costs with lossless compression and gain full observability over every session.

Edgee CLI setup (recommended)

The fastest way to connect Kimi Code to Edgee is the CLI. It authenticates, points Kimi Code at the gateway for the duration of the session, and starts it, no config file to edit by hand.

1. Install the Edgee CLI

   macOS / Linux

   curl -fsSL https://edgee.ai/install.sh | bash
   

   Homebrew (macOS)

   brew install edgee-ai/tap/edgee
   

   Windows (PowerShell)

   irm https://edgee.ai/install.ps1 | iex
   
2. Launch Kimi Code through Edgee

   edgee launch kimi
   

   The CLI authenticates, configures routing, and starts Kimi Code, all in one command. Token compression is enabled automatically.

   Kimi Code must already be installed. See the Kimi Code documentation for install instructions, or run curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash.

You can pass any Kimi Code arguments after the command:

edgee launch kimi "How do I implement a binary search?"

After the session ends, the CLI prints a link to view token usage, compression savings, and cost breakdown in the Edgee Console.

What the session runs on

Kimi Code launched through Edgee runs on Edgee credentials and the Edgee model catalog, not on a Moonshot subscription. The CLI provisions a Kimi Code key against your Edgee organization on first launch; a Moonshot plan is not required and is not used.

The provider Edgee configures lives in memory for the length of the session. Nothing is written to ~/.kimi-code/config.toml, and running kimi on its own afterwards is unaffected.

Model selection

The session is pinned to moonshotai/kimi-k2.7-code. That is a starting point, not a restriction: Edgee’s routing engine decides which provider and model actually serve each request, so routing strategies and retry and fallback apply as they do for any other agent.

To pin a different catalog model instead, set EDGEE_KIMI_MODEL before launching:

EDGEE_KIMI_MODEL="anthropic/claude-sonnet-4-5" edgee launch kimi

Compression settings

Compression, fallback, and rerouting for the Kimi Code key are managed like any other agent:

edgee settings kimi

See token compression for what each setting does.

Manual setup (advanced)

Prefer to configure Kimi Code yourself? Kimi Code does not read provider credentials from the usual environment variables — api_key and base_url come from config.toml. The one channel that does read the shell is the KIMI_MODEL_* family, which synthesizes a provider and a model alias in memory:

export KIMI_MODEL_NAME="moonshotai/kimi-k2.7-code"
export KIMI_MODEL_API_KEY="<YOUR_EDGEE_API_KEY>"
export KIMI_MODEL_BASE_URL="https://edgee.io"
export KIMI_MODEL_PROVIDER_TYPE="anthropic"
export KIMI_CODE_CUSTOM_HEADERS="x-edgee-api-key: <YOUR_EDGEE_API_KEY>
x-edgee-session-id: <A_UUID>"

Replace <YOUR_EDGEE_API_KEY> with your actual Edgee API key from the Edgee Console.

Three details worth knowing:

• KIMI_MODEL_NAME is both the model id and the switch. Unset, none of the other variables are read. Set with a required one missing, Kimi Code fails at startup rather than quietly calling Moonshot.
• KIMI_MODEL_BASE_URL carries no /v1 suffix. With KIMI_MODEL_PROVIDER_TYPE=anthropic, the SDK appends /v1/messages itself, the same way ANTHROPIC_BASE_URL works for Claude Code.
• KIMI_CODE_CUSTOM_HEADERS takes one Name: Value per line and is what groups requests into a session in the Console. Without x-edgee-session-id, requests are still routed and metered, but they do not group into one session.

edgee launch kimi sets all of these for you, including a fresh session id and your repository origin, and adds nothing to your shell configuration.

Benefits

Cost reduction

Edgee’s token compression reduces the tokens sent to and from the model, with no change to output quality.

Observability

Every request is logged in the Edgee Console with token counts, latency, and cost breakdowns.

Reliability

Automatic retry and fallback across providers keeps your sessions running even when a provider has issues.

One command

No config to edit, the CLI wires everything up.

Next Steps

• Learn more about the Edgee CLI and its launch commands
• Set up observability to monitor usage and costs
• Explore retry and fallback for resilient routing