Skip to content
Zed editor logo

Zed via Tokonomix

Add Tokonomix as an OpenAI-compatible provider in Zed’s Agent panel — 130+ models and consensus on one key, configured in settings.json.

openai_compatible providerHigh-performance editorGPL/AGPL · open sourcemacOS · Linux · Windows
Zed — a high-performance editor, via Tokonomix

What is Zed?

Zed is a high-performance, multiplayer code editor written in Rust. Its built-in Agent panel lets you chat with a model, edit code, and run agentic tasks — and it supports OpenAI API-compatible providers, so the model behind the panel is your choice.

  • A native, GPU-accelerated editor with an integrated AI Agent panel.
  • Configure any OpenAI-compatible endpoint under language_models.openai_compatible in settings.json.
  • List exactly the models you want available, each with its context window.
  • Open source, with a strong focus on speed and low latency.

Why route Zed through Tokonomix?

Zed’s Agent panel is only as good as the model behind it. Tokonomix lets you pick from every major family — and reach for consensus on the high-stakes edits — without leaving your settings.json.

  • Expose tokonomix-consensus and any direct slug side by side in the model picker.
  • One key, 130+ models — no separate provider accounts.
  • Per-call spend caps and hosting_region / origin_country routing for regulated codebases.
  • Switch the model on a task from the Agent panel; cost is metered in your dashboard.

Connect Tokonomix in settings.json

Add an openai_compatible provider named tokonomix with the Tokonomix api_url and the models you want. Then pick a Tokonomix model in the Agent panel.

{
  "language_models": {
    "openai_compatible": {
      "tokonomix": {
        "api_url": "https://tokonomix.ai/api/v1",
        "available_models": [
          { "name": "tokonomix-consensus", "display_name": "Tokonomix Consensus", "max_tokens": 200000 },
          { "name": "anthropic/claude-sonnet-4-6", "display_name": "Claude Sonnet (fast)", "max_tokens": 200000 }
        ]
      }
    }
  }
}
Where the API key goes

Per Zed’s docs, do not put the API key in settings.json. Enter it in the provider settings UI, or set the generated environment variable TOKONOMIX_API_KEY (provider id, upper-snake-case, + _API_KEY).

Verify it works

  • Save settings.json and open the Agent panel — the Tokonomix models appear in the picker.
  • Enter your key in the provider settings (or via TOKONOMIX_API_KEY) and select Tokonomix Consensus.
  • Ask a question and confirm the metered call 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