Skip to main content
Configure Kilo Code, the open-source AI coding agent for VS Code and the terminal, to use Eden AI for 500+ models behind one API key.

Overview

Eden AI is a built-in provider in Kilo Code, in both the VS Code extension and the CLI. Kilo uses the provider ID edenai and reads your key from EDENAI_API_KEY.
  • 500+ models: reach OpenAI, Anthropic, Google, Mistral, Z.ai and more through one key
  • One key, one invoice: no per-vendor accounts to manage
  • EU endpoint: route through api.eu.edenai.run when you have data-residency requirements
  • Shared credential store: the extension and the CLI read the same auth.json

Prerequisites

  • Kilo Code installed, either the VS Code extension or the CLI. See kilocode.ai
  • An Eden AI API key from app.edenai.runAPI Keys

Setup in VS Code

  1. Open Settings in the Kilo Code extension.
  2. Go to the Providers tab and add Eden AI. If it is not listed, click Show more providers.
  3. Paste your Eden AI API key.
  4. Select a model.
Credentials are stored in Kilo’s auth.json, the same store the CLI uses.

Setup in the CLI

Connecting interactively is the recommended path, so the key lands in auth.json rather than in a project file. In the TUI run /connect, choose Eden AI, then paste your key. From the shell:
Then pick a model from the picker, or set a default:
To keep the secret in the environment instead, declare the provider in ~/.config/kilo/kilo.json or ./kilo.json:

Model naming

Eden AI model IDs are already vendor/model, so a full reference in Kilo has three segments, edenai/<vendor>/<model>:
Copy the identifier exactly as the models endpoint returns it. It is public and needs no key:

Using a model that is not in the picker

The picker lists the Eden AI models in the catalogue Kilo refreshes, which is smaller than the full Eden AI catalogue. Any other model can be declared yourself:
Set cost when you declare a model, and limit too if you want the context gauge to be right. Kilo defaults both to zero for a model it does not already know, which would leave spend reporting at zero. Costs are per million tokens, so multiply the endpoint’s input_cost_per_token and output_cost_per_token by one million. A limit block needs both context, from context_length, and output.

EU data residency

Point the provider at the EU gateway with a custom base URL:
That base URL governs where Eden AI processes the request. The EU endpoint serves the subset of the catalogue available in the EU, so a model that works on the global endpoint is not guaranteed to be reachable through it. Independently, some models are published as a region-pinned variant that also pins the underlying vendor’s region, marked with an @eu suffix:
Only a few of these appear in the picker. Declare the others as shown in the previous section.

Cost tracking

The spend Kilo Code displays for Eden AI is derived from token counts and the per-model rates in its catalogue, so treat it as an estimate. Eden AI returns the actual billed cost of each request in its own response body, and that figure, with your Eden AI dashboard, is the authoritative one.

Troubleshooting

Invalid API key

Create a new key in your Eden AI account, then reconnect with /connect or kilo auth login --provider edenai. If you use manual configuration, update EDENAI_API_KEY in the environment Kilo runs from.

Model not found

Copy the identifier exactly as the models endpoint returns it, vendor prefix included. Do not rely on a static list.

Eden AI is not visible in the provider list

Refresh Kilo Code’s provider catalogue, then check Show more providers.

A key or model you just added has no effect

Kilo caches the resolved catalogue for a few minutes. Wait, then restart your client.

Next Steps