Zed on AI models run in Europe

Add Evanesca as an OpenAI-compatible provider in Zed's settings.json and drive its agent panel with open models run in Europe. language_models.openai_compatible in ~/.config/zed/settings.json; the key in the keychain or in an environment variable.

Tool documentation read on 12 Oct 2026

SoonOpening soon: what follows describes the service as it will work.

Tool: Zed · Code editor
API format: OpenAI-compatible (Chat Completions)
Base URL: https://evanesca.app/api/v1
Your prompts: From your machine or server, straight to Evanesca

Setup

1. Declare the provider

Each model needs max_tokens, which Zed reads as the context window. A key never goes in settings.json: enter it under Settings → AI → LLM Providers, or start Zed with EVANESCA_API_KEY set — Zed derives the variable's name from the provider ID (evanesca).

~/.config/zed/settings.json

{
  "language_models": {
    "openai_compatible": {
      "evanesca": {
        "api_url": "https://evanesca.app/api/v1",
        "available_models": [
          {
            "name": "deepseek-v4.1-flash",
            "display_name": "DeepSeek V4.1 Flash (Evanesca)",
            "max_tokens": 1000000,
            "capabilities": { "tools": true, "images": true }
          }
        ]
      }
    }
  }
}

Where these settings come from

These settings come from Zed's official documentation, read on 12 Oct 2026. This guide has not been run against Evanesca yet: it will be checked when the API opens.

Which model to pick

Evanesca's models from which a real tool call came back at their operator. This guide uses DeepSeek V4.1 Flash and Gemma 4 26B, picked from the catalogue for their properties. Prices per million tokens, input / output, margin and VAT included.

Model ID	Operator and place	Context	Reasoning	Price
`mistral-large-4`	EU region of Mistral AI	512k	—	€2.5133 / €7.7246
`deepseek-v4.1-flash`	Germany (AKI.IO)	1M	Yes	€1.008 / €3.024
`glm-5.3`	Germany (AKI.IO)	512k	Yes	€3.024 / €9.24
`qwen3.8-27b`	Scaleway — Paris, France	256k	Yes	€1.008 / €5.544
`deepseek-v4-flash`	Scaleway — Paris, France	256k	Yes	€0.672 / €1.344
`apertus-v1.5-70b`	Switzerland (Infomaniak)	100k	—	€1.2936 / €4.62
`glm-5.2`	Scaleway — Paris, France	256k	Yes	€3.024 / €9.24
`qwen3.6-35b`	Scaleway — Paris, France	256k	Yes	€0.42 / €2.52
`gemma-4-26b`	Germany (AKI.IO)	256k	—	€0.168 / €0.84
`mistral-small-4-119b`	EU region of Mistral AI	256k	—	€0.2772 / €1.1088
`qwen3.5-397b`	Scaleway — Paris, France	250k	Yes	€1.008 / €6.048
`gpt-oss-120b`	Scaleway — Paris, France	—	Yes	€0.252 / €1.008
`qwen3-coder-30b`	Scaleway — Paris, France	256k	—	€0.336 / €1.344
`qwen3-235b`	Scaleway — Paris, France	250k	—	€1.26 / €3.78
`mistral-small-3.2`	Scaleway — Paris, France	—	—	€0.252 / €0.588
`llama-3.3-70b`	Scaleway — Paris, France	—	—	€1.512 / €1.512
`pixtral-12b`	Scaleway — Paris, France	128k	—	€0.336 / €0.336

Reasoning tokens are billed as output. Where each model runs and what its operator keeps: Models and Europe.

Good to know

Edit predictions (Tab) call a completions endpoint, not chat completions: they do not work with Evanesca.
External agents launched inside Zed, such as Claude Code, ignore these settings: configure the agent itself.
With a reasoning model Zed sends max_completion_tokens by default; capabilities.max_tokens_parameter changes that if needed.

Where your prompts go

Zed's privacy page says that with your own key the provider you configured handles the requests, from the local app; only Zed-hosted models go through Zed.

On Evanesca's side, the model runs at a European operator, named with its place in the x-evanesca-operator and x-evanesca-location headers of every response, and Evanesca keeps no copy of prompts or answers — only the billing data of each call. What each operator keeps is set out in Models and Europe; the host of Evanesca's servers is named in the legal notice.

Sources

Official documentation, read on 12 Oct 2026:

Frequently asked questions

Does Zed work with Evanesca?

Yes, through its base URL setting: language_models.openai_compatible in ~/.config/zed/settings.json; the key in the keychain or in an environment variable. These settings come from Zed's official documentation, read on 12 Oct 2026. This guide has not been run against Evanesca yet: it will be checked when the API opens.

Which Evanesca model should I use with Zed?

One whose tool calling is measured. This guide uses DeepSeek V4.1 Flash and Gemma 4 26B; the 17 candidates are in this page's table, with their context window and price.

Do my prompts stay in Europe with Zed?

Zed's privacy page says that with your own key the provider you configured handles the requests, from the local app; only Zed-hosted models go through Zed. On Evanesca's side, the model runs at a European operator, named with its place in the x-evanesca-operator and x-evanesca-location headers of every response, and Evanesca keeps no copy of prompts or answers — only the billing data of each call. What each operator keeps is set out in Models and Europe; the host of Evanesca's servers is named in the legal notice.

One key, and the tool runs on models in Europe.

Prepaid credit, no subscription: the same key works with every guide.

Get an API key All integrations