APIMaster.ai
APIMaster.ai Docs
Quick startAPIMaster.aiMarketplace

Kimi Code CLI — Third-Party API Key Setup (APIMaster Registry)

Configure APIMaster.ai as a custom provider in Kimi Code CLI via Custom Provider Registry. Paste registry.json and your Bearer token to use coding models like gpt-5.6-sol.

Kimi Code CLI setup

Complete the environment check and Get API Key first.

Kimi Code CLI can import a third-party provider through Custom provider registry (api.json). APIMaster.ai exposes a dynamic Registry: the model list is generated from your API Key permissions. When models are added or removed on the platform, later launches refresh automatically—you usually do not need to reconfigure.

Item Value
Registry URL https://apimaster.ai/kimi/registry.json
Bearer token Your APIMaster API Key from the console (sk-...)
Protocol OpenAI-compatible Chat Completions (streaming / tool calling)

The Registry only returns models suitable for coding agents (chat, streaming, tools, text reasoning). Image, video, embedding, and rerank models do not appear. Your key’s group and model allowlist directly affect the visible list.

Prerequisites

  1. Kimi Code CLI installed (screenshots use 0.31.1; command is kimi).
  2. An APIMaster API Key from the console.
  3. A working terminal (Windows PowerShell / macOS Terminal / Linux).

Install per the official Kimi Code docs, then run:

kimi

If the model shows not set, follow the steps below and import APIMaster with /provider.

Step 1 — Launch and run /provider

  1. Run kimi.
  2. Type /provider and press Enter.

Launch Kimi Code and enter /provider

Step 2 — Choose Custom registry (api.json)

In the Add provider menu:

  1. Use ↑↓ to highlight Custom registry (api.json) (not Known third-party provider).
  2. Press Enter.

Add provider: select Custom registry (api.json)

Step 3 — Paste Registry URL and Bearer token

In Import custom provider registry, fill in:

Field Value
Registry URL https://apimaster.ai/kimi/registry.json
Bearer token Your APIMaster API Key

Use Tab / ↑↓ to switch fields, Enter to continue. Do not share the key in chat groups or public screenshots.

Paste apimaster.ai/kimi/registry.json and Bearer token

You can also import from the shell (same result):

kimi provider add https://apimaster.ai/kimi/registry.json --api-key sk-your-apimaster-key

Step 4 — Select a model under apimaster

After a successful import you should see something like:

  • Imported 1 provider from registry.

Then in Select a model:

  1. Press Tab to switch to the apimaster tab.
  2. Pick a model such as gpt-5.6-sol, gpt-5.6-terra, gpt-5.5, or glm-5.2 (depends on your key permissions and current marketplace listings).
  3. Optionally set Thinking to On.
  4. Press Enter.

Select a model under the apimaster tab (e.g. gpt-5.6-sol)

The status bar should show something like: gpt-5.6-sol thinking.

Step 5 — Send a test message

You may see a default similar to:

  • Default model set to apimaster/gpt-5.6-sol with thinking on.

Send a short message (e.g. hello). A normal reply means traffic is going through APIMaster.

Successful import and chat verification

Use /model anytime to switch models.

Changing keys / missing models

Situation What to do
Switched to a key with different permissions Run /provider again (or kimi provider add ...)
A model is missing from the list Confirm it on the marketplace and check the token group / allowlist
Non-coding models missing Expected — the Registry filters non-agent models

Related docs