Skip to content
Kilo Code logo

Kilo Code via Tokonomix

Set Kilo Code’s OpenAI Compatible provider to Tokonomix — 130+ models and consensus on one key, straight from the settings panel.

OpenAI Compatible providerMCP-capableVS Code coding agentApache-2.0 · open sourceVS Code · all platforms
Kilo Code — open-source AI agent for VS Code, via Tokonomix

What is Kilo Code?

Kilo Code is an open-source AI coding agent for VS Code that plans, writes and refactors code across your project. It supports multiple providers — including a generic OpenAI Compatible option — and MCP tools, so it slots straight onto Tokonomix.

  • Plans and applies multi-file changes, runs commands, and iterates with your approval.
  • Ships an OpenAI Compatible provider — just a Base URL, key and model.
  • Supports MCP, so it can call external tools including consensus.
  • Open source and model-agnostic by design.

Why route Kilo Code through Tokonomix?

Kilo Code is model-agnostic, which is exactly where Tokonomix shines: one key replaces a drawer of provider accounts, and consensus is available for the changes you don’t want a single model to decide alone.

  • Reach 130+ models from one OpenAI Compatible endpoint — no per-provider keys.
  • Select tokonomix-consensus for risky refactors, a fast slug for routine edits.
  • Add the Tokonomix MCP server so the agent can call tokonomix_consensus_ask mid-task.
  • Per-call spend caps and region / origin routing keep cost and compliance in check.

Connect Tokonomix to Kilo Code

Open the Kilo Code settings panel, choose the OpenAI Compatible provider, and fill in three fields. The Base URL must include /v1.

# Kilo Code → Settings → API Provider: OpenAI Compatible
Base URL : https://tokonomix.ai/api/v1
API Key  : tok_live_your-key
Model    : tokonomix-consensus      # or any slug from GET /api/v1/models
Add consensus as a tool too

Beyond the chat model, add the Tokonomix MCP server (npx -y tokonomix-mcp with TOKONOMIX_API_KEY) so Kilo Code’s agent can call tokonomix_consensus_ask on the steps that matter.

Verify it works

  • Select the OpenAI Compatible provider, paste the Base URL, key and a model slug.
  • Ask Kilo Code to make a small edit and approve it.
  • Confirm the call and token usage in your Tokonomix dashboard.

Model selection

Which model and endpoint should my agent use?

Pick by what your agent does, then swap the model id any time — every model in the catalog works through the same key.

What your agent doesUse this
Edits files / calls tools and streams responses (most coding agents)An Anthropic model via the Anthropic endpoint (tools + streaming both work)
Calls tools but does not need streaming (any model)The OpenAI-compatible endpoint with a single model id
Wants tools and streaming on a non-Anthropic modelRun non-streaming for now — streaming tool-calls on other providers is not enabled yet
Plain chat, no toolsEither endpoint; streaming is fine
Wants a cross-model verdict (consensus) on a high-stakes answerSet model to tokonomix-consensus on the OpenAI-compatible endpoint — note: consensus rejects tool requests (no tool-calling)
Endpoint & API reference (technical)

anthropic-messages → https://tokonomix.ai/api/anthropic — tools ✓, streaming ✓ (use an Anthropic model). openai-completions → https://tokonomix.ai/api/v1 — tools ✓ (single-model passthrough), streaming with tools not yet enabled. Plain chat: streaming works on both. Consensus: openai-completions, model tokonomix-consensus, no tools. Swap the model id to any slug returned by GET /api/v1/models.

Browse all models →

Related agents